Is Bugsnag Down?

No — Bugsnag is up

Bugsnag's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 279 ms

Right now

The verdict is the worse of these two. How we decide

Bugsnag's status page

bugsnag.status.smartbear.com · read 3 minutes ago · checked every 3 minutes

Operational

Bugsnag's components, as its status page reports them
Component	Status
BugSnag Dashboard	Operational
BugSnag Error Reporting API	Operational
BugSnag Sessions API	Operational
BugSnag Upload API	Operational
BugSnag Data Access API	Operational
BugSnag OTLP Trace Reporting API	Operational
BugSnag Remote MCP	Operational

Open their status page

FlareWarden checks

bugsnag.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 279 ms
Checked: 1 hour ago

By region

Amsterdam reachable, 237 ms
Chicago reachable, 175 ms
London reachable, 113 ms
San Jose reachable, 408 ms
Singapore reachable, 248 ms
Sydney reachable, 251 ms
Tokyo reachable, 360 ms
Toronto reachable, 444 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Amsterdam	86 ms	3 ms	13 ms	228 ms
Chicago	105 ms	2 ms	10 ms	166 ms
London	52 ms	3 ms	12 ms	104 ms
San Jose	93 ms	2 ms	15 ms	400 ms
Singapore	151 ms	2 ms	11 ms	240 ms
Sydney	192 ms	1 ms	9 ms	247 ms
Tokyo	270 ms	1 ms	11 ms	356 ms
Toronto	340 ms	1 ms	11 ms	439 ms

We check that bugsnag.com loads, not every feature behind it. Test it yourself

History

Incidents Bugsnag reported

Since Oct 22, 16 days · from bugsnag.status.smartbear.com

Incidents: 0
Major or critical: 0
Median to resolve: —

No incidents reported in this window.

Bugsnag website availability

Measured by FlareWarden · bugsnag.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 234ms

Last 30 days

69-day clean streak

Oct 8 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of bugsnag.com from multiple regions every 6 hours. Bugsnag's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 69 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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 17 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. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
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. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Bugsnag itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Bugsnag goes down

We check Bugsnag every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required