All services / Samanage / Nov 11, 2026 / Evidence

Evidence

Evidence: Samanage, Nov 11, 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/1207/evidence. Free to reuse with attribution.

97 of 99Checks failed in the window
4 of 4Regions failing
http_502Most 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_50296
http_5041

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-PacificKIXFail5021184 mshttp_502
US EastORDFail502251 mshttp_502
EuropeAMSFail502635 mshttp_502
US WestSJCFail502351 mshttp_502

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 Samanage 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

99 checks, 97 failed (first , last ).

Failed checks

Failed checks
Check time (UTC)Probe ran (UTC)ResultHTTPLatencyError codeTrigger
Fail502361 mshttp_502scheduled
Fail502609 mshttp_502scheduled
Fail502549 mshttp_502scheduled
Fail502578 mshttp_502scheduled
Fail502450 mshttp_502scheduled
Fail5044523 mshttp_504scheduled
Fail502468 mshttp_502scheduled
Fail502882 mshttp_502scheduled
Fail502626 mshttp_502scheduled
Fail5021374 mshttp_502scheduled
Fail502511 mshttp_502scheduled
Fail502379 mshttp_502scheduled
Fail502398 mshttp_502scheduled
Fail502463 mshttp_502scheduled
Fail502659 mshttp_502scheduled
Fail502556 mshttp_502scheduled
Fail502631 mshttp_502scheduled
Fail502435 mshttp_502scheduled
Fail502641 mshttp_502scheduled
Fail502305 mshttp_502scheduled
Fail502444 mshttp_502scheduled
Fail502668 mshttp_502scheduled
Fail502453 mshttp_502scheduled
Fail502655 mshttp_502scheduled
Fail502819 mshttp_502scheduled
Fail502551 mshttp_502scheduled
Fail502626 mshttp_502scheduled
Fail502608 mshttp_502scheduled
Fail502381 mshttp_502scheduled
Fail502634 mshttp_502scheduled
Fail502499 mshttp_502scheduled
Fail502489 mshttp_502scheduled
Fail502422 mshttp_502scheduled
Fail502671 mshttp_502scheduled
Fail502815 mshttp_502scheduled
Fail502511 mshttp_502scheduled
Fail502615 mshttp_502scheduled
Fail502610 mshttp_502scheduled
Fail502408 mshttp_502scheduled
Fail502886 mshttp_502scheduled
Fail502469 mshttp_502scheduled
Fail502769 mshttp_502scheduled
Fail502501 mshttp_502scheduled
Fail502407 mshttp_502scheduled
Fail502492 mshttp_502scheduled
Fail502542 mshttp_502scheduled
Fail502621 mshttp_502scheduled
Fail502684 mshttp_502scheduled
Fail502528 mshttp_502scheduled
Fail502502 mshttp_502scheduled
Fail502468 mshttp_502scheduled
Fail502406 mshttp_502scheduled
Fail502446 mshttp_502scheduled
Fail502447 mshttp_502scheduled
Fail5021224 mshttp_502scheduled
Fail502304 mshttp_502scheduled
Fail502713 mshttp_502scheduled
Fail502485 mshttp_502scheduled
Fail502363 mshttp_502scheduled
Fail502632 mshttp_502scheduled
Fail502703 mshttp_502scheduled
Fail502461 mshttp_502scheduled
Fail502651 mshttp_502scheduled
Fail502595 mshttp_502scheduled
Fail502431 mshttp_502scheduled
Fail502607 mshttp_502scheduled
Fail502502 mshttp_502scheduled
Fail502436 mshttp_502scheduled
Fail502634 mshttp_502scheduled
Fail502534 mshttp_502scheduled
Fail502588 mshttp_502scheduled
Fail502314 mshttp_502scheduled
Fail502291 mshttp_502scheduled
Fail502313 mshttp_502scheduled
Fail502574 mshttp_502scheduled
Fail502527 mshttp_502scheduled
Fail502688 mshttp_502scheduled
Fail502454 mshttp_502scheduled
Fail502443 mshttp_502scheduled
Fail502452 mshttp_502scheduled
Fail502605 mshttp_502scheduled
Fail502622 mshttp_502scheduled
Fail502344 mshttp_502scheduled
Fail502445 mshttp_502scheduled
Fail502632 mshttp_502scheduled
Fail502440 mshttp_502scheduled
Fail502593 mshttp_502scheduled
Fail502737 mshttp_502scheduled
Fail502588 mshttp_502scheduled
Fail502585 mshttp_502scheduled
Fail502554 mshttp_502scheduled
Fail502273 mshttp_502scheduled
Fail502248 mshttp_502scheduled
Fail502502 mshttp_502scheduled
Fail502512 mshttp_502scheduled
Fail502597 mshttp_502scheduled
Fail502346 mshttp_502scheduled
All 99 checks, passes included
All checks in the window
Check time (UTC)Probe ran (UTC)ResultHTTPLatencyError codeTrigger
Fail502361 mshttp_502scheduled
Fail502609 mshttp_502scheduled
Fail502549 mshttp_502scheduled
Fail502578 mshttp_502scheduled
Fail502450 mshttp_502scheduled
Fail5044523 mshttp_504scheduled
Fail502468 mshttp_502scheduled
Fail502882 mshttp_502scheduled
Fail502626 mshttp_502scheduled
Fail5021374 mshttp_502scheduled
Fail502511 mshttp_502scheduled
Fail502379 mshttp_502scheduled
Fail502398 mshttp_502scheduled
Fail502463 mshttp_502scheduled
Fail502659 mshttp_502scheduled
Fail502556 mshttp_502scheduled
Fail502631 mshttp_502scheduled
Fail502435 mshttp_502scheduled
Fail502641 mshttp_502scheduled
Fail502305 mshttp_502scheduled
Fail502444 mshttp_502scheduled
Fail502668 mshttp_502scheduled
Fail502453 mshttp_502scheduled
Fail502655 mshttp_502scheduled
Fail502819 mshttp_502scheduled
Fail502551 mshttp_502scheduled
Fail502626 mshttp_502scheduled
Fail502608 mshttp_502scheduled
Fail502381 mshttp_502scheduled
Fail502634 mshttp_502scheduled
Fail502499 mshttp_502scheduled
Fail502489 mshttp_502scheduled
Fail502422 mshttp_502scheduled
Fail502671 mshttp_502scheduled
Fail502815 mshttp_502scheduled
Fail502511 mshttp_502scheduled
Fail502615 mshttp_502scheduled
Fail502610 mshttp_502scheduled
Fail502408 mshttp_502scheduled
Fail502886 mshttp_502scheduled
Fail502469 mshttp_502scheduled
Fail502769 mshttp_502scheduled
Fail502501 mshttp_502scheduled
Fail502407 mshttp_502scheduled
Fail502492 mshttp_502scheduled
Fail502542 mshttp_502scheduled
Fail502621 mshttp_502scheduled
Fail502684 mshttp_502scheduled
Fail502528 mshttp_502scheduled
Fail502502 mshttp_502scheduled
Fail502468 mshttp_502scheduled
Fail502406 mshttp_502scheduled
Fail502446 mshttp_502scheduled
Fail502447 mshttp_502scheduled
Fail5021224 mshttp_502scheduled
Fail502304 mshttp_502scheduled
Fail502713 mshttp_502scheduled
Fail502485 mshttp_502scheduled
Fail502363 mshttp_502scheduled
Fail502632 mshttp_502scheduled
Fail502703 mshttp_502scheduled
Fail502461 mshttp_502scheduled
Fail502651 mshttp_502scheduled
Fail502595 mshttp_502scheduled
Fail502431 mshttp_502scheduled
Fail502607 mshttp_502scheduled
Fail502502 mshttp_502scheduled
Fail502436 mshttp_502scheduled
Fail502634 mshttp_502scheduled
Fail502534 mshttp_502scheduled
Fail502588 mshttp_502scheduled
Fail502314 mshttp_502scheduled
Fail502291 mshttp_502scheduled
Fail502313 mshttp_502scheduled
Fail502574 mshttp_502scheduled
Fail502527 mshttp_502scheduled
Fail502688 mshttp_502scheduled
Fail502454 mshttp_502scheduled
Fail502443 mshttp_502scheduled
Fail502452 mshttp_502scheduled
Fail502605 mshttp_502scheduled
Fail502622 mshttp_502scheduled
Fail502344 mshttp_502scheduled
Fail502445 mshttp_502scheduled
Fail502632 mshttp_502scheduled
Fail502440 mshttp_502scheduled
Fail502593 mshttp_502scheduled
Fail502737 mshttp_502scheduled
Fail502588 mshttp_502scheduled
Fail502585 mshttp_502scheduled
Fail502554 mshttp_502scheduled
Fail502273 mshttp_502scheduled
Fail502248 mshttp_502scheduled
Fail502502 mshttp_502scheduled
Fail502512 mshttp_502scheduled
Fail502597 mshttp_502scheduled
Fail502346 mshttp_502scheduled
Pass200371 ms—scheduled
Pass200579 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=1207

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