Monthly leaderboard
Slowest to admit it: November 2026
How long each company took to post an incident on its own status page after our checks and user reports already showed the problem. Confirmed outages only, measured with our own timestamps. Companies are ranked by their median delay.
November 2026 so far. Updated 2026-11-13 04:43 UTC; the month is still in progress, so this can change.
The ranking
| Rank | Company | Median delay | Longest delay | Posted after us |
|---|---|---|---|---|
| 1 | BitGo | 3 min | 3 min | 1 of 1 |
Small sample: 2 timed confirmed outages this month. Treat these as early numbers, not a trend.
Posted first or within a minute
These companies had confirmed outages we could time, and their median delay was under a minute: they posted before our evidence or about as fast. They are not ranked.
- Ada · Confirmed outages timed: 1
Every incident behind these numbers
| Date | Company | Our evidence | Vendor posted | Difference | Dispute |
|---|---|---|---|---|---|
| Nov 7, 2026 | BitGo | 2026-11-07 00:16 UTC | 2026-11-07 00:20 UTC | 3 min after our evidence | Dispute |
| Nov 4, 2026 | Ada | 2026-11-04 19:44 UTC | 2026-11-04 19:17 UTC | 26 min before our evidence | Dispute |
Not ranked this month
- Confirmed outages with our own evidence where we have no time from the vendor status page: 0. Many services we track do not publish a machine-readable status page or post updates elsewhere, so this does not mean the vendor stayed silent. These are never ranked.
- Confirmed outages where the vendor incident started more than 6 hours from our evidence (treated as a different event): 1.
- Timed incidents left out because only one independent source carried them (not a confirmed outage): 1.
How this is measured
- Confirmed outages only: at least two independent sources agreed (our checks failed at least twice, at least 5 people reported a problem within 15 minutes, or the vendor posted a major or critical incident). Retracted incidents, scheduled maintenance, incidents under review and incidents that rested only on the vendor status page are left out.
- Our evidence time is the moment our own evidence first carried the incident: our checks failing repeatedly or a spike in user reports. The vendor time is the earliest time the vendor gives for its status-page incident (its posted start or creation time), so a vendor that backdates its start is credited with it.
- A vendor incident counts as the same event only if it started within 6 hours of our evidence, the same rule as our accuracy scorecard. An outage the vendor has not posted yet is not counted until it does.
- Each delay is floored to whole minutes. A vendor that posted first, or within a minute, counts as 0 minutes. A company is ranked by the median of its delays that month, and only when that median is at least 1 minute; ties are broken by more confirmed outages, then the longest delay.
- Months are calendar months in UTC, by our evidence time. Times on this page are in UTC.
- A delay is a timing measurement, not a judgment of intent: companies often confirm an issue internally before posting. If a number here is wrong, use the Dispute link; we review disputes within 24 hours.
Accuracy scorecard → · How we detect, verify and correct outages · JSON
Disclaimer
Outage information on this site is provided as is, without warranty, for information only. It may be inaccurate, incomplete or late. Damn Is It Down is not affiliated with, sponsored by or endorsed by the companies listed. Company names and trademarks belong to their owners and are used only to identify the services.