Damn, is it down?

All services / PNC Bank / Nov 1, 2026 / Evidence

Evidence

Evidence: PNC Bank, Nov 1, 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: Retracted: we published this in error. The evidence is kept here so you can see why. How we verify outages

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

9 of 13Checks failed in the window
4 of 4Regions failing
origin_resetMost 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
origin_reset9

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-PacificKIXPass404257 ms—
US EastORDPass40423 ms—
EuropeAMSPass404124 ms—
US WestSJCPass404119 ms—

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 PNC Bank 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

13 checks, 9 failed (first , last ).

Failed checks

Failed checks
Check time (UTC)Probe ran (UTC)ResultHTTPLatencyError codeTrigger
Fail520157 msorigin_resetscheduled
Fail520130 msorigin_resetscheduled
Fail520280 msorigin_resetscheduled
Fail520169 msorigin_resetscheduled
Fail520186 msorigin_resetscheduled
Fail520102 msorigin_resetscheduled
Fail520160 msorigin_resetscheduled
Fail520379 msorigin_resetscheduled
Fail520118 msorigin_resetscheduled
All 13 checks, passes included
All checks in the window
Check time (UTC)Probe ran (UTC)ResultHTTPLatencyError codeTrigger
Fail520157 msorigin_resetscheduled
Fail520130 msorigin_resetscheduled
Fail520280 msorigin_resetscheduled
Fail520169 msorigin_resetscheduled
Fail520186 msorigin_resetscheduled
Fail520102 msorigin_resetscheduled
Fail520160 msorigin_resetscheduled
Fail520379 msorigin_resetscheduled
Fail520118 msorigin_resetscheduled
Pass404138 ms—scheduled
Pass404251 ms—scheduled
Pass404308 ms—scheduled
Pass40435 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=13

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