We started checking Honeybadger on November 2, 2026, which is 7 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Honeybadger reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Honeybadger's own status page declared. Below it, any public chatter we saw about Honeybadger and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Honeybadger's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about Honeybadger in the last 24 hours, which is not evidence that nothing is wrong.
Honeybadger's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Honeybadger's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Honeybadger next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
100.00%
733
US-West
100.00%
582
Europe
100.00%
531
Asia-Pacific
100.00%
322
Their declared record
Honeybadger's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Delayed error processing and missed alerts (US region)All systems operational
Nov 7, 2026, 2:01 PM UTC to Nov 7, 2026, 2:01 PM UTC (0 min)resolved
their latest update (Nov 7, 2026, 2:01 PM UTC): Between 13:38 and 13:45 UTC on November 7, during planned maintenance on one of our Redis servers, part of our error-processing pipeline failed after the server switched to its upgraded node. Processing of incoming errors in the US region was delayed by up to about six minutes. N…
Elevated failure rates on the US error reporting APIAll systems operational
Aug 15, 2026, 8:48 PM UTC to Aug 15, 2026, 8:48 PM UTC (0 min)resolved
their latest update (Aug 15, 2026, 8:48 PM UTC): 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 repor…
Elevated error rates on the US error reporting APIPartial outage
Jul 8, 2026, 11:48 AM UTC to Jul 8, 2026, 11:48 AM UTC (0 min)resolved
their latest update (Jul 8, 2026, 11:48 AM UTC): Between 06:22 and 08:23 UTC on July 8, requests to our US error reporting API (api.honeybadger.io) experienced a highly elevated failure rate. During this window, a majority of requests to submit errors, events, and check-ins received 5xx responses or timed out. Error reports sen…
Delays with notificationsMinor incident
Mar 12, 2026, 7:27 PM UTC to Mar 12, 2026, 7:27 PM UTC (0 min)resolved
their latest update (Mar 12, 2026, 7:27 PM UTC): We had a backlog in our notifications queue that prevented timely delivery of alerts to channels such as Email, Slack, etc. The backlog has been processed as of 19:20 UTC.
Our autoscaling rules for this service had a monitoring gap that prevented a scale-out to maintain a low la…
Outage in check-in processingPartial outage
Jan 14, 2026, 8:40 PM UTC to Jan 14, 2026, 8:48 PM UTC (7 min)resolved
their latest update (Jan 14, 2026, 8:48 PM UTC): This incident has been resolved.
Insights queries and dashboards are unavailablePartial outage
Oct 22, 2025, 7:46 PM UTC to Oct 22, 2025, 8:15 PM UTC (28 min)resolved
their latest update (Oct 22, 2025, 8:15 PM UTC): This incident has been resolved.
Error ingestion API is downMajor outage
Oct 22, 2025, 1:09 PM UTC to Oct 22, 2025, 1:16 PM UTC (7 min)resolved
their latest update (Oct 22, 2025, 1:16 PM UTC): The EU API has been restored.
Delays in error processingAll systems operational
Oct 20, 2025, 1:44 PM UTC to Oct 20, 2025, 7:58 PM UTC (6h 15m)resolved
their latest update (Oct 20, 2025, 7:58 PM UTC): This incident has been resolved.
AWS outage in us-east-1Partial outage
Oct 20, 2025, 8:00 AM UTC to Oct 20, 2025, 8:00 AM UTC (0 min)resolved
their latest update (Oct 20, 2025, 8:00 AM UTC): Our systems were affected by the DynamoDB outage in AWS' us-east-1 region. Impacts included not being able to log use the web app, uptime checks not being executed on time, and check-ins being falsely reported as missing. We are evaluating what steps we can take to mitigate these…
Delay in stats and check-in processingMinor incident
Feb 12, 2025, 1:30 PM UTC to Feb 12, 2025, 1:30 PM UTC (0 min)resolved
their latest update (Feb 12, 2025, 1:30 PM UTC): We had an interruption in processing of check-in alerts and in-app stats from about 12:30 to about 13:30 UTC. This may have resulted in a failure or a delay in reporting check-ins that went missing during that period.
Showing the 10 most recent of 51 incidents Honeybadger has declared in the history we hold.
These entries are Honeybadger's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Honeybadger's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.