Bugsnag: BugSnag Marketing Site Down
Cloudflare outage, Nov 18, 2025 · 77 vendors, 81 incidents
Bugsnag’s incident blames Cloudflare as the cause. (hop 1, posted +3 h 11 min vs the first vendor naming Cloudflare)
“…BugSnag Marketing Site Down This incident has been resolved. Due to a reported global Cloudflare outage, the BugSnag marketing site may currently be inaccessible for some users. This will not impact a…”
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["Cloudflare<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>13 vendors, 13 blamed Cloudflare<br/>Stytch, Zed, NordLayer +10"]:::blames
root --> h1
h4["1 to 4 hours later<br/>19 vendors, 19 blamed Cloudflare<br/>GitLab, Gorgias, Cursor +16"]:::blames
root --> h4
later["Later<br/>7 vendors, 7 blamed Cloudflare<br/>RudderStack, Brex, Maven Central +4"]:::blames
root --> later
me["Bugsnag (this incident)<br/>posted +3 h 11 min"]:::me
h4 --- meFull event: timeline, evidence and all vendors →
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
Timeline of updates
- identified
Due to a reported global Cloudflare outage, the BugSnag marketing site may currently be inaccessible for some users. This will not impact any BugSnag dashboard functionality or BugSnag APIs. Users can still access the BugSnag dashboard by navigating to app.bugsnag.com
- resolved
This incident has been resolved.
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).