Provider · FastlyWarning
CDN latency rising while your site stays up
Edge delivery slows for a region. Your uptime check passes; your customers wait.
Oh Dear monitors your application health. Crowswatch monitors the operational ecosystem around it.
Uptime, SSL, cron and DNS checks tell you your own systems are healthy. Crowswatch tells you what is happening across the providers and dependencies those systems rely on, in one operational stream.
Uptime & SSLCronProvider eventsInfra layer
Two layers of operational health
Website health is one layer. Operational health is two.
Your application can be perfectly healthy while the layer beneath it is not.
Website layer
What Oh Dear watches
UptimeSSL validCron on timeNo broken links
Infrastructure layer
What Crowswatch watches
Fastly edge latencyDNS propagation driftProvider incidentRegional checkout impact
Oh Dear keeps the top layer green. Crowswatch watches the layer underneath, where this incident actually started.
Application health vs operational ecosystem
Oh Dear watches your application. Crowswatch watches the ecosystem it depends on.
Application health tells you your own systems are sound. Operational ecosystem awareness tells you when something you depend on is not.
Application health
- Uptime and response checks
- SSL and certificate health
- Cron and scheduled job monitoring
- Broken links and sitemap checks
- DNS and domain hygiene
Operational ecosystem
- Provider incidents across 150+ services
- CDN and regional degradation
- SaaS and API dependency health
- Dependency propagation, attributed
- Provider events on one operational timeline
Beyond application health
When your application is fine but the experience is not.
Each of these sits outside your application's own health. Oh Dear would correctly report your site as up. The experience still degrades, because the cause is a dependency. Crowswatch surfaces it.
Provider · StripeWarning
Payment API degraded, checkout page healthy
Your checkout loads fine. Confirmations slow because a dependency is struggling.
DNS · embercheckout.comWarning
DNS propagation issue after a provider change
A registrar or provider change is propagating. Resolution is intermittent before any check fails.
Cron · nightly-billingWarning
Cron ran on time, the API it calls did not
The job fired and reported healthy. The downstream provider API it depends on was degraded.
Region · EU-WestCritical
Customers impacted regionally, globally fine
Your global checks pass. A regional provider incident is degrading one market.
SSL · api.partner.comWarning
A partner's certificate expired, not yours
Your own SSL is valid. An upstream partner lapse breaks an integration you rely on.
Coverage comparison
Oh Dear monitors your application. Crowswatch monitors what it depends on.
Coverage areaOh DearCrowswatch
Uptime monitoringMulti-region uptime and response checksChecks plus the provider state behind them
SSL and certificate monitoringCertificate health and expiry alertsSSL, DNS drift, DMARC, SPF, MX changes, registrar expiry
Cron and scheduled jobsCron heartbeat and schedule checksSurfaces the provider APIs those jobs depend on
Broken links and sitemapBroken link, mixed content and sitemap checksApplication hygiene stays with Oh Dear
DNS and domain checksDNS and domain configuration checksDNS drift plus the provider changes behind it
Provider incident awarenessNot coveredLive incidents from 150+ providers, attributed in-stream
Dependency propagation and attributionNot coveredProvider → API → journey → customer, as one chain
Unified operational timelineNot coveredEvery signal in one attributed, severity-coded stream
The same incident, two timelines
Oh Dear confirms your application is healthy. Crowswatch explains the degradation anyway.
Same window. Your application checks stay healthy throughout, correctly. Crowswatch surfaces the provider incident degrading the experience in parallel, attributed.
Oh Dear timeline
- 14:30Uptime healthy
- 14:31SSL valid, cron on time
- 14:33Pages responding, slightly slower
- 14:36Customer reports begin
- 14:39Application still healthy
- 14:42Cause not in your own checks
Crowswatch timeline
- 14:30
All providers operational
baseline
- 14:31
Fastly edge latency rising in EU-West
Provider
- 14:33
Fastly confirms degraded edge performance
Provider incident
- 14:35
Checkout API latency rising regionally
API check
- 14:37
EU checkout completion dropping, attributed
Customer journey
- 14:39
Provider cause and regional impact grouped into one incident
Operational chain
Your application was healthy throughout. Crowswatch explained why the experience was not.
Keep monitoring your application. Add awareness of what it depends on.
Oh Dear keeps your website and application healthy. Crowswatch adds visibility into the providers and dependencies around them, so a healthy app and a degraded experience never look the same again.
Free plan available. No credit card. 150+ providers tracked out of the box.