Honeybadger had 6 outages in the last 2 years totaling 6h 57m of downtime — averaging 0.2 incidents per month.
There were 6 Honeybadger outages since October 20, 2025 totaling 6h 57m of downtime. Each is summarised below — incident details, duration, and resolution information.
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 latency on the queue. This monitoring gap has been resolved.
A recent deploy has resulted in our rejecting some check-in API requests. We are in the process of deploying a fix.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
API ingestion of errors has been interrupted. We are deploying a fix.
The US API has been restored, and the EU API restoration is in process.
The EU API has been restored.
Our error processing pipeline has been impacted by the AWS outage earlier this morning. Errors are being processed, but the end-to-end latency is much higher than normal. We are working to restore the processing to full capacity.
We're continuing to monitor the AWS outage. Errors are being processed, but may be delayed. Uptime checks are also delayed, so you may notice lag with uptime notifications and status page updates.
Processing has been restored and all systems are normal. We'll continue to monitor as AWS continues to restore service. Thanks!
This incident has been resolved.
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 kinds of impacts from this kind of outage in the future. Additionally, our status page was not updated in a timely manner due to our not having configured various AWS services as dependent components of our status page. We have fixed that issue, so future AWS outages will result in our status page automatically being updated.