Experiencing Issues with Outbound SMS via Twilio

About This Site

Welcome to the Honeybadger.io status page.

Uptime over the past 90 days. View historical uptime.
Web Application Operational
90 days ago
100.0 % uptime
Today
API Operational
90 days ago
100.0 % uptime
Today
Outbound SMS via Twilio Degraded Performance
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.

No incidents or maintenance related to this downtime.

Jul 9, 2026

No incidents reported today.

Jul 8, 2026
Elevated error rates on the US error reporting API
Resolved - 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 sent by client libraries without retry logic during this period were not received and cannot be recovered. The Honeybadger web application, dashboards, uptime monitoring, and our EU region were not affected.

What happened: Beginning at 06:18 UTC, we started receiving error reports at roughly triple our normal total API volume. The service tier that ingests this traffic was at its overnight capacity level and became saturated. Our autoscaling responded, but the metrics it relied on significantly under-measured the failed traffic, so capacity was added far too slowly — full recovery came at 08:23 UTC when scaling caught up and absorbed the load. Compounding the problem, PagerDuty alerts were not fired to wake up a human due to a misconfiguration.

What we've done: We've fixed the underlying scaling weakness: API capacity now also scales directly on load-balancer error rates (previously we scaled only on request rates, and that scaling doesn't respond quickly enough), and we've doubled the maximum capacity of the ingestion tier. These changes are already deployed to both US and EU regions. We're also evaluating adding adaptive per-key rate limiting to the ingestion service.

We're sorry for the disruption, and for any gaps this caused in your error data during the window.
Jul 8, 04:48 PDT
Jul 7, 2026

No incidents reported.

Jul 6, 2026

No incidents reported.

Jul 5, 2026

No incidents reported.

Jul 4, 2026

No incidents reported.

Jul 3, 2026

No incidents reported.

Jul 2, 2026

No incidents reported.

Jul 1, 2026

No incidents reported.

Jun 30, 2026

No incidents reported.

Jun 29, 2026

No incidents reported.

Jun 28, 2026

No incidents reported.

Jun 27, 2026

No incidents reported.

Jun 26, 2026

No incidents reported.

Jun 25, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage