Damn, is it down?

All services / SuprSend / Nov 6, 2026 / Evidence

Evidence

Evidence: SuprSend, Nov 6, 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: Vendor-reported issue: only the company's status page flagged it; our checks and user reports did not confirm an outage. How we verify outages

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

0 of 33Checks failed in the window
0 of 4Regions failing
—Most 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

No failed checks with an error code in this window.

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: none recorded.

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

33 checks, 0 failed.

All 33 checks, passes included
All checks in the window
Check time (UTC)Probe ran (UTC)ResultHTTPLatencyError codeTrigger
Pass200101 ms—scheduled
Pass200242 ms—scheduled
Pass200160 ms—scheduled
Pass200187 ms—scheduled
Pass200244 ms—scheduled
Pass200154 ms—scheduled
Pass200251 ms—on demand
Pass200119 ms—scheduled
Pass200122 ms—scheduled
Pass200168 ms—scheduled
Pass200173 ms—scheduled
Pass200185 ms—scheduled
Pass200208 ms—scheduled
Pass200261 ms—scheduled
Pass200196 ms—scheduled
Pass200173 ms—scheduled
Pass200248 ms—scheduled
Pass200276 ms—scheduled
Pass20036 ms—scheduled
Pass200104 ms—scheduled
Pass200288 ms—on demand
Pass200207 ms—scheduled
Pass20053 ms—scheduled
Pass200164 ms—scheduled
Pass200279 ms—scheduled
Pass200216 ms—scheduled
Pass200373 ms—scheduled
Pass200108 ms—scheduled
Pass200129 ms—scheduled
Pass200313 ms—scheduled
Pass200217 ms—scheduled
Pass200229 ms—scheduled
Pass20041 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=1013

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