Detection lead time vs. vendor status pages
Each row below is a service with at least 2 recorded lead-time samples from vendor-confirmed incidents, compared on when an independent signal — user reports, synthetic probes, DNS, BGP, social — detected the incident against when the vendor confirmed it on their official status page. Beat rate is the share of those incidents where the independent signal came first. Leads that merely read the vendor's own status surface faster are tracked separately below — we don't count those as knowing first.
How we measure: for every incident where the vendor eventually confirmed an outage on their official status page, we record when our earliest independent signal (user reports, synthetic probes, BGP, DNS, certificate transparency, social) first detected the issue, and compare it to the vendor's confirmation timestamp. Leads whose earliest signal was our reader of the vendor's own status page (LLM or native API) are excluded from rankings and reported separately as relay speed. Services need at least 2 recorded lead-time samples from confirmed incidents to rank. Read the full methodology →
Watch the services your stack depends on.
Build a watchlist of your vendors and get notified when PulseWatch detects a problem.
Start free