Snapshot 257142

Document
Status page
URL
https://status.honeybadger.io/
Fetched
HTTP status
200
Content type
text/html; charset=utf-8
Fetch mode
static
Size
104107 bytes
SHA-256 (raw)
b69d2fbc265326845208ec27afc887037815199ff3238d5427bf08affa7f663b
SHA-256 (normalized text)
5782a6305ff2843888a3097ad25526fb7b30bd95179fa00f397f9c06771b14b0

Normalized text

Scripts and page chrome removed; this is what change detection compares.

Subscribe to UpdatesSubscribe
All Systems Operational
About This Site
Welcome to the Honeybadger.io status page.
Uptime over the past 90 days. View historical uptime.
Web Application Operational
API Operational
Outbound SMS via Twilio Operational
Payments via Stripe Operational
AWS cloudFront Operational
AWS route53 Operational
Pusher Pusher REST API Operational
Pusher WebSocket client API Operational
Pusher Presence channels Operational
Pusher Webhooks Operational
Slack Notifications Operational
Slack Apps/Integrations/APIs Operational
PagerDuty Events API (US) Operational
PagerDuty Events API (EU) Operational
Outbound email Operational
AWS dynamodb-eu-central-1 Operational
AWS dynamodb-us-east-1 Operational
AWS dynamodb-ap-southeast-1 Operational
AWS dynamodb-eu-west-2 Operational
AWS dynamodb-us-west-2 Operational
AWS ecs-us-east-1 Operational
AWS ecs-eu-central-1 Operational
AWS elb-eu-central-1 Operational
AWS elb-us-east-1 Operational
AWS lambda-eu-central-1 Operational
AWS lambda-ap-southeast-1 Operational
AWS lambda-eu-west-2 Operational
AWS lambda-us-east-1 Operational
AWS lambda-us-west-2 Operational
AWS s3-eu-central-1 Operational
AWS s3-sa-east-1 Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Related
No incidents or maintenance related to this downtime.
Past Incidents
Nov 11, 2026
No incidents reported today.
Nov 10, 2026
No incidents reported.
Nov 9, 2026
No incidents reported.
Nov 8, 2026
No incidents reported.
Nov 7, 2026
Delayed error processing and missed alerts (US region)
Resolved - 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. No error data was lost: every error report we received was stored.
For roughly 1,900 error reports received between 13:38 and 13:41 UTC, some follow-up steps did not run. As a result, you may not have received an alert for a new error first seen in that window, and a resolved error that recurred in that window may not have been automatically reopened. Some of these occurrences may also appear more than once in search results and occurrence counts.
The issue has been resolved and processing has been normal since 13:45 UTC. We are working on fixing the alerts and duplicate occurrences that were affected, and we have identified the code change that will prevent this from happening during future maintenance.
Nov 7, 06:01 PST
Nov 6, 2026
No incidents reported.
Nov 5, 2026
No incidents reported.
Nov 4, 2026
No incidents reported.
Nov 3, 2026
No incidents reported.
Nov 2, 2026
No incidents reported.
Nov 1, 2026
No incidents reported.
Oct 31, 2026
No incidents reported.
Oct 30, 2026
No incidents reported.
Oct 29, 2026
No incidents reported.
Oct 28, 2026
No incidents reported.
Incident History Powered by Atlassian Statuspage