Damn, is it down?

All services / ChargePoint / Nov 5, 2026 / Evidence

Evidence

Evidence: ChargePoint, 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: 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/834/evidence. Free to reuse with attribution.

0 of 90Checks 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.

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

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

90 checks, 0 failed.

All 90 checks, passes included
All checks in the window
Check time (UTC)Probe ran (UTC)ResultHTTPLatencyError codeTrigger
Pass200308 ms—scheduled
Pass20052 ms—scheduled
Pass20033 ms—scheduled
Pass200311 ms—scheduled
Pass200135 ms—scheduled
Pass200143 ms—scheduled
Pass200534 ms—scheduled
Pass200420 ms—scheduled
Pass20091 ms—scheduled
Pass20087 ms—scheduled
Pass302—bot_blocked_networkscheduled
Pass20084 ms—scheduled
Pass200107 ms—scheduled
Pass200585 ms—scheduled
Pass20078 ms—scheduled
Pass20069 ms—scheduled
Pass200117 ms—scheduled
Pass200917 ms—scheduled
Pass20092 ms—scheduled
Pass200414 ms—scheduled
Pass20069 ms—scheduled
Pass20085 ms—scheduled
Pass200460 ms—scheduled
Pass200320 ms—scheduled
Pass200390 ms—scheduled
Pass200476 ms—scheduled
Pass20052 ms—scheduled
Pass20083 ms—scheduled
Pass200160 ms—scheduled
Pass20040 ms—scheduled
Pass302—bot_blocked_networkscheduled
Pass200431 ms—scheduled
Pass200595 ms—scheduled
Pass200393 ms—scheduled
Pass200411 ms—scheduled
Pass20096 ms—scheduled
Pass20068 ms—scheduled
Pass302—bot_blocked_networkscheduled
Pass200116 ms—scheduled
Pass20078 ms—scheduled
Pass200396 ms—scheduled
Pass200362 ms—scheduled
Pass200128 ms—scheduled
Pass2001031 ms—scheduled
Pass20062 ms—scheduled
Pass20075 ms—scheduled
Pass20051 ms—scheduled
Pass20096 ms—scheduled
Pass200112 ms—scheduled
Pass20049 ms—scheduled
Pass20064 ms—scheduled
Pass200363 ms—scheduled
Pass200131 ms—scheduled
Pass20080 ms—scheduled
Pass20081 ms—scheduled
Pass200125 ms—scheduled
Pass20064 ms—scheduled
Pass20074 ms—scheduled
Pass20098 ms—scheduled
Pass20060 ms—scheduled
Pass200871 ms—scheduled
Pass20054 ms—scheduled
Pass20076 ms—scheduled
Pass20048 ms—scheduled
Pass20074 ms—scheduled
Pass302—bot_blocked_networkscheduled
Pass200633 ms—scheduled
Pass302—bot_blocked_networkscheduled
Pass200594 ms—scheduled
Pass20096 ms—scheduled
Pass200804 ms—scheduled
Pass20064 ms—scheduled
Pass200398 ms—scheduled
Pass200136 ms—scheduled
Pass20080 ms—scheduled
Pass200635 ms—scheduled
Pass200115 ms—scheduled
Pass200105 ms—scheduled
Pass200173 ms—scheduled
Pass20069 ms—scheduled
Pass200346 ms—scheduled
Pass20095 ms—scheduled
Pass20043 ms—scheduled
Pass2001088 ms—scheduled
Pass20087 ms—scheduled
Pass20096 ms—scheduled
Pass200101 ms—scheduled
Pass200170 ms—scheduled
Pass20063 ms—scheduled
Pass20042 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=834

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