All services / KARTE / Nov 20, 2026 / Evidence

Evidence

Evidence: KARTE, Nov 20, 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: Confirmed outage: at least 2 independent sources agreed. How we verify outages

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

16 of 16Checks failed in the window
4 of 4Regions failing
http_503_edgeMost common error code
1Peak 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_503_edge14
http_5032

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.
  • : Failing from Asia-Pacific, US East, Europe, US West.
Regional probe results in the window
RegionData centerTime (UTC)ResultHTTPLatencyError code
Asia-PacificKIXFail50378 mshttp_503_edge
US EastORDFail503144 mshttp_503_edge
EuropeAMSFail50360 mshttp_503_edge
US WestSJCFail50368 mshttp_503_edge

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

6:45 AM ET: 07:00 AM ET: 07:15 AM ET: 07:30 AM ET: 07:45 AM ET: 08:00 AM ET: 08:15 AM ET: 18:30 AM ET: 08:45 AM ET: 09:00 AM ET: 09:15 AM ET: 09:30 AM ET: 09:45 AM ET: 010:00 AM ET: 010:15 AM ET: 010:30 AM ET: 010:45 AM ET: 011:00 AM ET: 011:15 AM ET: 011:30 AM ET: 011:45 AM ET: 012:00 PM ET: 012:15 PM ET: 012:30 PM ET: 012:45 PM ET: 01:00 PM ET: 01:15 PM ET: 01:30 PM ET: 01:45 PM ET: 02:00 PM ET: 02:15 PM ET: 02:30 PM ET: 02:45 PM ET: 03:00 PM ET: 03:15 PM ET: 03:30 PM ET: 03:45 PM ET: 04:00 PM ET: 04:15 PM ET: 04:30 PM ET: 04:45 PM ET: 05:00 PM ET: 05:15 PM ET: 05:30 PM ET: 05:45 PM ET: 06:00 PM ET: 06:15 PM ET: 06:30 PM ET: 06:45 PM ET: 07:00 PM ET: 07:15 PM ET: 07:30 PM ET: 07:45 PM ET: 06:45 AM ET7:45 PM ET
User reports per 15 minutes (peak 1). Times are ET.
Report counts per 15 minutes (1 non-zero buckets)
15 minutes from (UTC)Reports
1

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

16 checks, 16 failed (first , last ).

Failed checks

Failed checks
Check time (UTC)Probe ran (UTC)ResultHTTPLatencyError codeTrigger
Fail50353 mshttp_503_edgescheduled
Fail50333 mshttp_503_edgeon demand
Fail503141 mshttp_503_edgeon demand
Fail503116 mshttp_503_edgeon demand
Fail50399 mshttp_503_edgescheduled
Fail50396 mshttp_503_edgeon demand
Fail5031068 mshttp_503scheduled
Fail50352 mshttp_503_edgescheduled
Fail50387 mshttp_503_edgeon demand
Fail50389 mshttp_503_edgeon demand
Fail5031038 mshttp_503scheduled
Fail50394 mshttp_503_edgeon demand
Fail50373 mshttp_503_edgescheduled
Fail50392 mshttp_503_edgescheduled
Fail503231 mshttp_503_edgescheduled
Fail50353 mshttp_503_edgescheduled
All 16 checks, passes included
All checks in the window
Check time (UTC)Probe ran (UTC)ResultHTTPLatencyError codeTrigger
Fail50353 mshttp_503_edgescheduled
Fail50333 mshttp_503_edgeon demand
Fail503141 mshttp_503_edgeon demand
Fail503116 mshttp_503_edgeon demand
Fail50399 mshttp_503_edgescheduled
Fail50396 mshttp_503_edgeon demand
Fail5031068 mshttp_503scheduled
Fail50352 mshttp_503_edgescheduled
Fail50387 mshttp_503_edgeon demand
Fail50389 mshttp_503_edgeon demand
Fail5031038 mshttp_503scheduled
Fail50394 mshttp_503_edgeon demand
Fail50373 mshttp_503_edgescheduled
Fail50392 mshttp_503_edgescheduled
Fail503231 mshttp_503_edgescheduled
Fail50353 mshttp_503_edgescheduled

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=1418

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