Damn, is it down?

All services / O2 UK / Nov 5, 2026 / Evidence

Evidence

Evidence: O2 UK, Nov 5, 2026

The raw data behind this incident page: every check we ran, the regions that failed, the error codes and the user report curve. Check our work.

Our verdict: Possible problem, not a confirmed outage: it did not meet our evidence bar. How we verify outages

Download JSON Download CSV Also at /api/v1/outages/889/evidence. Free to reuse with attribution.

25 of 41Checks failed in the window
4 of 4Regions failing
http_530Most common error code
0Peak user reports in 15 min

Window: to . Checks from 15 minutes before the start to 15 minutes after recovery (or now). Report curve: one hour either side. Tables are in UTC.

Error codes

Error codeFailed checks
http_53025

Passing checks with a note (counted as up, not as failures): bot_blocked_timeout ×2.

http_5xx = the site answered with that server error; timeout = no answer in time; network = the connection failed; origin_reset = the connection to the site's server was reset (HTTP 520–527) and a second fetch path got no answer either; no_status = no usable answer. Bot walls (bot_*), certificate problems on a server that answers (cert_*) and maintenance pages count as up.

Regions

  • We check from: US East, US West, Europe, Asia-Pacific.
  • Failing during this incident: Asia-Pacific, US East, Europe, US West.
  • : Now failing from Asia-Pacific, US East, Europe, US West.

Regional probes run from Cloudflare data centers in each region. We keep the latest regional result per region, plus a timestamped timeline entry when a region starts failing during an incident, so older incidents show the failing regions and when each was first seen, not every regional probe.

Report curve

No user reports for O2 UK in this window.

User reports per 15-minute bucket. Counts only: no reporter identity, IP address, location or text is published. We call reports a spike at 5 or more in 15 minutes.

Raw checks

41 checks, 25 failed (first , last ).

Failed checks

Failed checks
Check time (UTC)Probe ran (UTC)ResultHTTPLatencyError codeTrigger
Fail5306312 mshttp_530scheduled
Fail5306958 mshttp_530scheduled
Fail5306226 mshttp_530scheduled
Fail5306015 mshttp_530scheduled
Fail5306789 mshttp_530scheduled
Fail5307906 mshttp_530scheduled
Fail5306134 mshttp_530scheduled
Fail5306160 mshttp_530scheduled
Fail5306934 mshttp_530scheduled
Fail5306223 mshttp_530scheduled
Fail5306029 mshttp_530scheduled
Fail5307282 mshttp_530scheduled
Fail5306759 mshttp_530scheduled
Fail5306093 mshttp_530scheduled
Fail5306647 mshttp_530scheduled
Fail5306306 mshttp_530scheduled
Fail5305995 mshttp_530scheduled
Fail5307109 mshttp_530scheduled
Fail5306675 mshttp_530scheduled
Fail5306181 mshttp_530scheduled
Fail5306864 mshttp_530scheduled
Fail5306017 mshttp_530scheduled
Fail5307585 mshttp_530scheduled
Fail5307126 mshttp_530scheduled
Fail5306723 mshttp_530scheduled
All 41 checks, passes included
All checks in the window
Check time (UTC)Probe ran (UTC)ResultHTTPLatencyError codeTrigger
Fail5306312 mshttp_530scheduled
Fail5306958 mshttp_530scheduled
Fail5306226 mshttp_530scheduled
Fail5306015 mshttp_530scheduled
Fail5306789 mshttp_530scheduled
Fail5307906 mshttp_530scheduled
Fail5306134 mshttp_530scheduled
Fail5306160 mshttp_530scheduled
Fail5306934 mshttp_530scheduled
Fail5306223 mshttp_530scheduled
Fail5306029 mshttp_530scheduled
Fail5307282 mshttp_530scheduled
Fail5306759 mshttp_530scheduled
Fail5306093 mshttp_530scheduled
Pass200251 ms—scheduled
Fail5306647 mshttp_530scheduled
Fail5306306 mshttp_530scheduled
Fail5305995 mshttp_530scheduled
Pass200145 ms—scheduled
Fail5307109 mshttp_530scheduled
Fail5306675 mshttp_530scheduled
Pass200158 ms—scheduled
Fail5306181 mshttp_530scheduled
Pass200435 ms—scheduled
Fail5306864 mshttp_530scheduled
Pass200763 ms—scheduled
Pass200435 ms—scheduled
Fail5306017 mshttp_530scheduled
Fail5307585 mshttp_530scheduled
Pass301—bot_blocked_timeoutscheduled
Pass301—bot_blocked_timeoutscheduled
Pass200568 ms—scheduled
Fail5307126 mshttp_530scheduled
Fail5306723 mshttp_530scheduled
Pass2001611 ms—scheduled
Pass2001250 ms—scheduled
Pass2001868 ms—scheduled
Pass200247 ms—scheduled
Pass2002027 ms—scheduled
Pass200746 ms—scheduled
Pass2001592 ms—scheduled

Every main HTTP check of this service in the window, oldest first: the scheduled check time, when the probe actually ran, the result, HTTP status, latency and the stored error code. A failed check is a 5xx or 408 answer, a timeout or a failed connection; bot walls and maintenance pages count as passing and are noted in passing_notes.

How to check this

  • Compare checks.rows with the outage page: the first and last failed checks bound the incident times we published.
  • error_codes counts every failed check by its stored code; recount it from checks.rows.
  • report_curve.points sum to summary.reports_in_curve; the peak is summary.peak_reports_15m.
  • Disagree? Dispute it at https://damnisitdown.com/support?dispute=889

No personal data: no reporter identities, IP addresses, emails, report text or reporter locations. User reports are aggregate 15-minute counts.

← Back to the incident · Methodology · Dispute this report