outages.live
Live

Bugsnag

Bugsnag is operational

Checked 30 s ago Operational

History

90 days agoToday

Incidents in 90 days

2

Days with an incident

4

Median duration

24 h 27 min

Longest incident

46 h 33 min

Components

7
BugSnag Dashboard Operational
90 days ago1 day with an incidentToday
BugSnag Error Reporting API Operational
90 days agoNo incidentsToday
BugSnag Sessions API Operational
90 days ago1 day with an incidentToday
BugSnag Upload API Operational
90 days agoNo incidentsToday
BugSnag Data Access API Operational
90 days agoNo incidentsToday
BugSnag OTLP Trace Reporting API Operational
90 days ago3 days with an incidentToday
BugSnag Remote MCP Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 1, 2026

Duration46 h 33 min14:34 to 13:07Issues with the Traces and Spans APIDegraded

This incident has been resolved.

Aug 20, 2026

Duration2 h 21 min17:36 to 19:57Sessions processing delaysDegraded

This incident has been resolved.

Follow Bugsnag

Your coding agent knows when Bugsnag is down, and tells you when a failure is theirs, not yours. You can also get Bugsnag incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "bugsnag" and tell me if Bugsnag has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=bugsnag
Slack
/feed subscribe https://outages.cc/feed.xml?providers=bugsnag

Go from tracking outages to fixing production issues with Polylane.

Try Polylane