Damn, is it down?

All services / Cocoapods / Nov 13, 2026 / Evidence

Evidence

Evidence: Cocoapods, Nov 13, 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/1253/evidence. Free to reuse with attribution.

69 of 73Checks failed in the window
4 of 4Regions failing
http_500Most 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_50069

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-PacificKIXPass200516 ms—
US EastORDPass20057 ms—
EuropeAMSPass200289 ms—
US WestSJCPass200127 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 Cocoapods 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

73 checks, 69 failed (first , last ).

Failed checks

Failed checks
Check time (UTC)Probe ran (UTC)ResultHTTPLatencyError codeTrigger
Fail500239 mshttp_500scheduled
Fail500244 mshttp_500scheduled
Fail500244 mshttp_500scheduled
Fail500254 mshttp_500scheduled
Fail500262 mshttp_500scheduled
Fail500247 mshttp_500scheduled
Fail500160 mshttp_500scheduled
Fail500236 mshttp_500scheduled
Fail500229 mshttp_500scheduled
Fail500220 mshttp_500scheduled
Fail500243 mshttp_500scheduled
Fail500121 mshttp_500scheduled
Fail500253 mshttp_500scheduled
Fail5001252 mshttp_500scheduled
Fail500180 mshttp_500scheduled
Fail500276 mshttp_500scheduled
Fail500233 mshttp_500scheduled
Fail500159 mshttp_500scheduled
Fail500244 mshttp_500on demand
Fail500276 mshttp_500scheduled
Fail500235 mshttp_500scheduled
Fail500213 mshttp_500scheduled
Fail500244 mshttp_500scheduled
Fail500242 mshttp_500scheduled
Fail500222 mshttp_500scheduled
Fail500211 mshttp_500scheduled
Fail500296 mshttp_500scheduled
Fail500232 mshttp_500scheduled
Fail500214 mshttp_500scheduled
Fail500255 mshttp_500scheduled
Fail500241 mshttp_500scheduled
Fail500310 mshttp_500scheduled
Fail500223 mshttp_500scheduled
Fail500243 mshttp_500scheduled
Fail500246 mshttp_500scheduled
Fail500229 mshttp_500scheduled
Fail500257 mshttp_500scheduled
Fail500251 mshttp_500scheduled
Fail500252 mshttp_500scheduled
Fail500163 mshttp_500scheduled
Fail500229 mshttp_500scheduled
Fail500255 mshttp_500scheduled
Fail500157 mshttp_500scheduled
Fail500274 mshttp_500scheduled
Fail500231 mshttp_500scheduled
Fail500229 mshttp_500scheduled
Fail500238 mshttp_500scheduled
Fail500136 mshttp_500scheduled
Fail500241 mshttp_500scheduled
Fail500211 mshttp_500scheduled
Fail500292 mshttp_500scheduled
Fail500250 mshttp_500scheduled
Fail500178 mshttp_500scheduled
Fail500156 mshttp_500scheduled
Fail500230 mshttp_500scheduled
Fail500258 mshttp_500scheduled
Fail500151 mshttp_500scheduled
Fail500242 mshttp_500scheduled
Fail500208 mshttp_500scheduled
Fail500255 mshttp_500scheduled
Fail500207 mshttp_500scheduled
Fail500249 mshttp_500scheduled
Fail500250 mshttp_500scheduled
Fail50089 mshttp_500scheduled
Fail500222 mshttp_500scheduled
Fail500210 mshttp_500scheduled
Fail500148 mshttp_500scheduled
Fail500293 mshttp_500scheduled
Fail500191 mshttp_500scheduled
All 73 checks, passes included
All checks in the window
Check time (UTC)Probe ran (UTC)ResultHTTPLatencyError codeTrigger
Pass200403 ms—scheduled
Fail500239 mshttp_500scheduled
Fail500244 mshttp_500scheduled
Fail500244 mshttp_500scheduled
Fail500254 mshttp_500scheduled
Fail500262 mshttp_500scheduled
Fail500247 mshttp_500scheduled
Fail500160 mshttp_500scheduled
Fail500236 mshttp_500scheduled
Fail500229 mshttp_500scheduled
Fail500220 mshttp_500scheduled
Fail500243 mshttp_500scheduled
Fail500121 mshttp_500scheduled
Fail500253 mshttp_500scheduled
Fail5001252 mshttp_500scheduled
Fail500180 mshttp_500scheduled
Fail500276 mshttp_500scheduled
Fail500233 mshttp_500scheduled
Fail500159 mshttp_500scheduled
Fail500244 mshttp_500on demand
Fail500276 mshttp_500scheduled
Fail500235 mshttp_500scheduled
Fail500213 mshttp_500scheduled
Fail500244 mshttp_500scheduled
Fail500242 mshttp_500scheduled
Fail500222 mshttp_500scheduled
Fail500211 mshttp_500scheduled
Fail500296 mshttp_500scheduled
Fail500232 mshttp_500scheduled
Fail500214 mshttp_500scheduled
Fail500255 mshttp_500scheduled
Fail500241 mshttp_500scheduled
Fail500310 mshttp_500scheduled
Fail500223 mshttp_500scheduled
Fail500243 mshttp_500scheduled
Fail500246 mshttp_500scheduled
Fail500229 mshttp_500scheduled
Fail500257 mshttp_500scheduled
Fail500251 mshttp_500scheduled
Fail500252 mshttp_500scheduled
Fail500163 mshttp_500scheduled
Fail500229 mshttp_500scheduled
Fail500255 mshttp_500scheduled
Fail500157 mshttp_500scheduled
Fail500274 mshttp_500scheduled
Fail500231 mshttp_500scheduled
Fail500229 mshttp_500scheduled
Fail500238 mshttp_500scheduled
Fail500136 mshttp_500scheduled
Fail500241 mshttp_500scheduled
Fail500211 mshttp_500scheduled
Fail500292 mshttp_500scheduled
Fail500250 mshttp_500scheduled
Fail500178 mshttp_500scheduled
Fail500156 mshttp_500scheduled
Fail500230 mshttp_500scheduled
Fail500258 mshttp_500scheduled
Fail500151 mshttp_500scheduled
Fail500242 mshttp_500scheduled
Fail500208 mshttp_500scheduled
Fail500255 mshttp_500scheduled
Fail500207 mshttp_500scheduled
Fail500249 mshttp_500scheduled
Fail500250 mshttp_500scheduled
Fail50089 mshttp_500scheduled
Fail500222 mshttp_500scheduled
Fail500210 mshttp_500scheduled
Fail500148 mshttp_500scheduled
Fail500293 mshttp_500scheduled
Fail500191 mshttp_500scheduled
Pass200267 ms—scheduled
Pass200241 ms—scheduled
Pass200155 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=1253

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