Damn, is it down?

All services / Cloud & developer

smartbear.com · Cloud & developer

Is Bugsnag down?

Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.

What's broken? (optional)
Is it just me?
No problems detected

Live diagnosis

Is it just me?

Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.

Your browser → smartbear.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—

Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.

Live outage map

No reports in the last 24 hours.

Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.

User reports

0

Near baseline. 0 in the last hour. Typical hour is about 0.

Our checks

Reaching it

Last check reached it in 1076 ms · 9 min ago.

Reports and checks

Reports compared with the typical volume, with check latency and failures overlaid101481 ms15:1521:1503:1509:0015:00
ReportsTypical baselineCheck latencyFailed checkTimes in UTC
Numbers behind the chart
Time (UTC)ReportsBaselineLatencyFailed checks
03:1500.0392 ms0
03:3000.01266 ms0
03:4500.0353 ms0
04:0000.0729 ms0
04:1500.0724 ms0
04:3000.0403 ms0
04:4500.0753 ms0
05:0000.01169 ms0
05:1500.0480 ms0
05:3000.0408 ms0
05:4500.0384 ms0
06:0000.0787 ms0
06:1500.0467 ms0
06:3000.097 ms0
06:4500.0587 ms0
07:0000.0784 ms0
07:1500.0634 ms0
07:3000.0598 ms0
07:4500.0612 ms0
08:0000.0582 ms0
08:1500.0833 ms0
08:3000.0661 ms0
08:4500.0663 ms0
09:0000.0427 ms0
09:1500.0358 ms0
09:3000.0311 ms0
09:4500.0769 ms0
10:0000.0477 ms0
10:1500.0467 ms0
10:3000.0683 ms0
10:4500.0382 ms0
11:0000.0904 ms0
11:1500.0475 ms0
11:3000.01481 ms0
11:4500.0269 ms0
12:0000.0703 ms0
12:1500.0553 ms0
12:3000.0967 ms0
12:4500.0237 ms0
13:0000.0513 ms0
13:1500.0750 ms0
13:3000.0835 ms0
13:4500.0400 ms0
14:0000.0797 ms0
14:1500.0469 ms0
14:3000.0351 ms0
14:4500.0567 ms0
15:0000.01076 ms0

Reliability

Score 100/100 · grade A

100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage

90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.

Bugsnag status badge Embed a live Bugsnag status badge

Free, no iframe or script. Updates every minute and links back here. More options on the embed page · JSON · MCP server

Bugsnag status and 30-day uptime badge

Past outages

No outages on record for Bugsnag yet. Outages of 10 minutes or more get their own page here.

All Bugsnag outages · Every recent outage

Having trouble with Bugsnag?

One report per service every 10 minutes from this network. No account.

What's broken? (optional)

Notes are stored for rate-limit context and are not shown publicly.

Questions

Is Bugsnag down right now?

Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.

Bugsnag not working for me but the status is fine. What now?

If Bugsnag is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Bugsnag's side.

How does Damn is it down decide Bugsnag's status?

Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.

How often is Bugsnag checked?

About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.