outages.live
Live

Honeybadger

Honeybadger is operational

Checked 3 min ago Operational

History

90 days agoToday

Incidents in 90 days

1

Days with an incident

1

Median duration

1 min

Longest incident

1 min

Components

31
Web Application Operational
90 days agoNo incidentsToday
API Operational
90 days ago1 day with an incidentToday
Outbound SMS via Twilio Operational
90 days agoNo incidentsToday
Payments via Stripe Operational
90 days agoNo incidentsToday
AWS cloudFront Operational
90 days agoNo incidentsToday
AWS route53 Operational
90 days agoNo incidentsToday
Pusher Pusher REST API Operational
90 days agoNo incidentsToday
Pusher WebSocket client API Operational
90 days agoNo incidentsToday
Pusher Presence channels Operational
90 days agoNo incidentsToday
Pusher Webhooks Operational
90 days agoNo incidentsToday
Slack Notifications Operational
90 days agoNo incidentsToday
Slack Apps/Integrations/APIs Operational
90 days agoNo incidentsToday
PagerDuty Events API (US) Operational
90 days agoNo incidentsToday
PagerDuty Events API (EU) Operational
90 days agoNo incidentsToday
Outbound email Operational
90 days agoNo incidentsToday
AWS dynamodb-eu-central-1 Operational
90 days agoNo incidentsToday
AWS dynamodb-us-east-1 Operational
90 days agoNo incidentsToday
AWS dynamodb-ap-southeast-1 Operational
90 days agoNo incidentsToday
AWS dynamodb-eu-west-2 Operational
90 days agoNo incidentsToday
AWS dynamodb-us-west-2 Operational
90 days agoNo incidentsToday
AWS ecs-us-east-1 Operational
90 days agoNo incidentsToday
AWS ecs-eu-central-1 Operational
90 days agoNo incidentsToday
AWS elb-eu-central-1 Operational
90 days agoNo incidentsToday
AWS elb-us-east-1 Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Aug 15, 2026

Duration1 min20:48 to 20:48Elevated failure rates on the US error reporting APINotice

Between 19:54 and 20:07 UTC on August 15, requests to our US error reporting API (api.honeybadger.io) experienced an elevated failure rate. During this window, a majority of requests to submit errors and events timed out or received 5xx responses. Browser (JavaScript) error reporting, source map uploads, the Honeybadger web application, dashboards, uptime monitoring, and our EU region were not affected. What happened: Beginning at 19:54 UTC, a single source began submitting error reports at roughly 150 times its normal rate, with payloads several times larger than average. This more than doubled the total volume of data arriving at our ingestion tier, which saturated within a minute. Because the saturated service kept accepting connections rather than returning errors outright, our autoscaling and alerting — which watch for error responses — did not register the problem quickly, and capacity was added later than it should have been. Service recovered at 20:07 UTC once additional capaci

Follow Honeybadger

Your coding agent knows when Honeybadger is down, and tells you when a failure is theirs, not yours. You can also get Honeybadger 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.live/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 "honeybadger" and tell me if Honeybadger 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.live/feed.xml?providers=honeybadger
Slack
/feed subscribe https://outages.live/feed.xml?providers=honeybadger

Go from tracking outages to fixing production issues with Polylane.

Try Polylane