Damn, is it down?

All services / Replit / Nov 8, 2026 / Evidence

Evidence

Evidence: Replit, Nov 8, 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/1113/evidence. Free to reuse with attribution.

0 of 129Checks 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 Replit 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

129 checks, 0 failed.

All 129 checks, passes included
All checks in the window
Check time (UTC)Probe ran (UTC)ResultHTTPLatencyError codeTrigger
Pass200188 ms—scheduled
Pass200102 ms—scheduled
Pass200109 ms—scheduled
Pass200103 ms—scheduled
Pass20068 ms—scheduled
Pass20097 ms—scheduled
Pass200113 ms—scheduled
Pass200113 ms—scheduled
Pass200144 ms—scheduled
Pass20099 ms—scheduled
Pass20090 ms—scheduled
Pass200119 ms—scheduled
Pass20086 ms—scheduled
Pass20086 ms—scheduled
Pass200136 ms—scheduled
Pass20099 ms—scheduled
Pass20084 ms—scheduled
Pass200113 ms—scheduled
Pass200102 ms—scheduled
Pass200105 ms—scheduled
Pass20064 ms—scheduled
Pass200122 ms—scheduled
Pass20096 ms—scheduled
Pass20094 ms—scheduled
Pass20064 ms—scheduled
Pass200110 ms—scheduled
Pass200107 ms—scheduled
Pass200101 ms—scheduled
Pass200117 ms—scheduled
Pass200106 ms—scheduled
Pass20055 ms—scheduled
Pass200116 ms—scheduled
Pass200124 ms—scheduled
Pass200117 ms—scheduled
Pass200105 ms—scheduled
Pass200102 ms—scheduled
Pass200109 ms—scheduled
Pass200122 ms—scheduled
Pass20064 ms—scheduled
Pass200116 ms—scheduled
Pass200118 ms—scheduled
Pass200135 ms—scheduled
Pass20056 ms—scheduled
Pass200127 ms—scheduled
Pass200171 ms—scheduled
Pass20095 ms—scheduled
Pass200126 ms—scheduled
Pass20089 ms—scheduled
Pass200136 ms—scheduled
Pass20063 ms—scheduled
Pass200101 ms—scheduled
Pass200159 ms—scheduled
Pass200124 ms—scheduled
Pass200124 ms—scheduled
Pass20052 ms—scheduled
Pass20088 ms—scheduled
Pass200132 ms—scheduled
Pass20093 ms—scheduled
Pass200118 ms—scheduled
Pass200104 ms—scheduled
Pass20068 ms—scheduled
Pass20093 ms—scheduled
Pass200102 ms—scheduled
Pass20061 ms—scheduled
Pass200102 ms—scheduled
Pass20054 ms—scheduled
Pass200100 ms—scheduled
Pass200122 ms—scheduled
Pass20098 ms—scheduled
Pass20093 ms—scheduled
Pass200111 ms—scheduled
Pass20075 ms—scheduled
Pass200124 ms—scheduled
Pass20091 ms—scheduled
Pass200113 ms—scheduled
Pass200127 ms—scheduled
Pass200111 ms—scheduled
Pass200149 ms—scheduled
Pass20087 ms—scheduled
Pass20095 ms—scheduled
Pass20084 ms—scheduled
Pass200106 ms—scheduled
Pass20084 ms—scheduled
Pass20086 ms—scheduled
Pass200127 ms—scheduled
Pass200182 ms—scheduled
Pass20099 ms—scheduled
Pass20072 ms—scheduled
Pass20099 ms—scheduled
Pass200155 ms—scheduled
Pass20064 ms—scheduled
Pass200115 ms—scheduled
Pass20070 ms—scheduled
Pass200129 ms—scheduled
Pass200100 ms—scheduled
Pass200129 ms—scheduled
Pass200103 ms—scheduled
Pass200104 ms—scheduled
Pass200164 ms—scheduled
Pass200112 ms—scheduled
Pass200124 ms—scheduled
Pass200163 ms—scheduled
Pass200252 ms—scheduled
Pass200124 ms—scheduled
Pass200138 ms—scheduled
Pass20079 ms—scheduled
Pass200133 ms—scheduled
Pass200135 ms—scheduled
Pass200145 ms—scheduled
Pass200267 ms—scheduled
Pass200135 ms—scheduled
Pass20073 ms—scheduled
Pass200207 ms—scheduled
Pass200173 ms—scheduled
Pass200121 ms—scheduled
Pass200117 ms—scheduled
Pass200187 ms—scheduled
Pass20065 ms—scheduled
Pass20087 ms—scheduled
Pass200120 ms—scheduled
Pass200191 ms—scheduled
Pass200111 ms—scheduled
Pass200110 ms—scheduled
Pass20095 ms—scheduled
Pass200487 ms—scheduled
Pass200201 ms—scheduled
Pass200152 ms—scheduled
Pass200117 ms—scheduled
Pass200151 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=1113

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