Is Bugsnag Down?

No — Bugsnag is up

Reachable from all 8 checked regions

Average response time: 224ms

Last checked 2 hours ago · checks run every 6 hours

Official status page: https://bugsnag.status.smartbear.com

Bugsnag uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

137ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 23 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

23-day clean streak

Aug 22 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

gru

305ms

DNS 192ms TCP 2ms TLS 13ms TTFB 295ms

iad

156ms

DNS 89ms TCP 2ms TLS 10ms TTFB 144ms

jnb

419ms

DNS 362ms TCP 0ms TLS 9ms TTFB 411ms

lax

134ms

DNS 56ms TCP 1ms TLS 11ms TTFB 122ms

lhr

176ms

DNS 67ms TCP 10ms TLS 15ms TTFB 165ms

nrt

209ms

DNS 141ms TCP 1ms TLS 11ms TTFB 198ms

ord

141ms

DNS 68ms TCP 8ms TLS 11ms TTFB 131ms

sin

259ms

DNS 136ms TCP 1ms TLS 20ms TTFB 247ms

What Bugsnag does

BugSnag is an application error monitoring service. SDKs in web, mobile and backend applications report crashes and exceptions to its API, group them into issues, and attach session data so teams can judge how many users an error affects. It is usually wired into release pipelines through source map and symbol uploads, and read through a web dashboard.

What an outage looks like

The BugSnag dashboard fails to load or issue lists stop updating. More consequential is the Error Reporting API, a separate component: when it is unavailable your applications keep running while the errors they generate do not arrive, so the dashboard looks quiet rather than broken. Sessions, uploads, data access and OTLP trace reporting each have their own component.

What to do about it

Check status.bugsnag.com, which redirects to bugsnag.status.smartbear.com, and read the component rather than the banner. Distinguish a Dashboard incident, where reporting continues and you cannot see it, from an Error Reporting API incident, where the gap is in the data itself. Hold release steps that depend on the Upload API rather than shipping without symbol files.

Is it down for everyone, or just you?

If this page says Bugsnag is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

Bugsnag outage FAQ

My BugSnag dashboard is empty. Does that mean no errors happened?

No, and this is the failure mode worth knowing. BugSnag Dashboard and BugSnag Error Reporting API are separate components. If the reporting API is the affected one, your applications are still failing and the events are simply not arriving, so quiet is the symptom rather than the good news. Check the Error Reporting API row before relaxing.

Will errors be lost during a BugSnag outage?

BugSnag does not publish delivery or retry guarantees on its status page, and behaviour differs by SDK and platform, so assume events raised while the reporting API was unavailable may be missing. Treat the window as a gap in coverage rather than proof of stability, and cross-check application logs for the same period.

Why does status.bugsnag.com send me to a SmartBear address?

BugSnag's status page is published on SmartBear's status domain, so status.bugsnag.com redirects to bugsnag.status.smartbear.com. The page itself is scoped to BugSnag and lists only BugSnag components. It is the right page despite the unfamiliar hostname, which is worth knowing before you dismiss it as the wrong company mid-incident.

Does a BugSnag outage block our deploys?

Only if your pipeline treats it as blocking. The Upload API, used for source maps and symbol files, is its own component. When it is down, deploys can still ship, but the builds released during that window may produce unreadable stack traces later. Most teams prefer to hold the release or re-upload symbols once it recovers.

Is trace data affected by the same incidents as error reporting?

Not necessarily. BugSnag reports OTLP Trace Reporting API separately from the Error Reporting API and the Sessions API. An incident can take out trace ingestion while error events continue to arrive, or the reverse. Check the specific row for the signal you are missing rather than assuming all telemetry stopped together.

How we measure this

We request Bugsnag's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Bugsnag publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Bugsnag goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required