Is Honeybadger Down?

No — Honeybadger is up

Honeybadger's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 519 ms

Right now

The verdict is the worse of these two. How we decide

Honeybadger's status page

status.honeybadger.io · read 4 minutes ago · checked every 3 minutes

Operational

Honeybadger's components, as its status page reports them
Component	Status
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

1 more, all operational · show all 13

All of Honeybadger's components
Component	Status
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
Outbound email	Operational

18 locations All operational

Open their status page

FlareWarden checks

honeybadger.io from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 519 ms
Checked: 1 hour ago

By region

Ashburn reachable, 199 ms
Chicago reachable, 270 ms
Johannesburg reachable, 2123 ms
London reachable, 212 ms
Los Angeles reachable, 239 ms
Singapore reachable, 355 ms
São Paulo reachable, 179 ms
Tokyo reachable, 582 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Ashburn	169 ms	3 ms	8 ms	185 ms
Chicago	105 ms	22 ms	27 ms	183 ms
Johannesburg	374 ms	248 ms	254 ms	1130 ms
London	73 ms	17 ms	21 ms	132 ms
Los Angeles	157 ms	11 ms	15 ms	197 ms
Singapore	114 ms	5 ms	7 ms	344 ms
São Paulo	151 ms	2 ms	9 ms	170 ms
Tokyo	16 ms	82 ms	84 ms	266 ms

We check that honeybadger.io loads, not every feature behind it. Test it yourself

History

Incidents Honeybadger reported

Since Oct 22, 15 days · from status.honeybadger.io

Incidents: 0
Major or critical: 0
Median to resolve: —

No incidents reported in this window.

Honeybadger website availability

Measured by FlareWarden · honeybadger.io

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 530ms

Last 30 days

59-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of honeybadger.io from multiple regions every 6 hours. Honeybadger's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 59 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What Honeybadger does

Honeybadger is an application monitoring service covering exception tracking, uptime checks and cron job monitoring, used mainly by Ruby, JavaScript, PHP, Python and Go teams. Applications report errors to its API and Honeybadger groups them, tracks their history and notifies the team. Because it is the thing that tells you something else broke, its own failures are unusually easy to miss.

What an outage looks like

Errors stop appearing in the dashboard and the application looks unusually healthy, which is the most dangerous symptom this service has. Notifications stop arriving in Slack, PagerDuty, email or SMS while errors continue to be recorded. Uptime and cron checks may not report, so a missed job produces no alert. The web application can be unreachable while error ingestion continues normally.

What to do about it

Read status.honeybadger.io, which is unusually detailed: alongside Web Application and API it reports its own upstream dependencies as components, including Outbound email, Outbound SMS via Twilio, Slack Notifications, PagerDuty Events API for US and EU, Pusher, Stripe and a long list of per-region AWS services. Match the symptom to the row. If only the notification components are affected, errors are still being collected and you should watch the dashboard directly until they recover.

Is it down for everyone, or just you?

If this page says Honeybadger is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Honeybadger outage FAQ

I have stopped getting Honeybadger alerts. Does that mean nothing is wrong?

Not necessarily, and this is the failure worth planning for. Honeybadger reports Outbound email, Outbound SMS via Twilio, Slack Notifications and the PagerDuty Events API as components separate from error ingestion, so errors can keep being recorded while no notification reaches you. Silence from an error monitor is ambiguous. Open the dashboard directly during an incident rather than treating a quiet channel as good news.

Will errors sent during a Honeybadger outage be lost?

Honeybadger client libraries generally send asynchronously and do not block your application, but they are not an unlimited buffer, and Honeybadger does not publish a guarantee covering every failure mode. Treat the incident window as a possible gap in your error history rather than assuming full capture, and check your own application logs for that period if you need certainty about what happened.

Is my Honeybadger problem actually an AWS or Twilio outage?

Quite possibly, and the status page is built to answer that. Honeybadger publishes AWS DynamoDB, ECS, ELB, Lambda, CloudFront and Route 53 per region as components, plus Twilio, Stripe, Pusher, Slack and PagerDuty. An incident on one of those upstream rows explains a Honeybadger symptom without Honeybadger itself having changed, and it usually means other tools you use are affected too.

The Honeybadger dashboard is down. Is error collection still working?

Often yes. Web Application and API are separate components, so the interface can be unreachable while the API keeps accepting error reports from your applications. Nothing needs re-sending in that case. Wait for the Web Application row to recover and the errors recorded during the window will be there when you can view them again.

Is Honeybadger down or is my integration misconfigured?

Compare scope. A configuration fault affects one application or one environment, usually after a deploy or an API key change, while a Honeybadger incident affects every project at once. status.honeybadger.io names the affected component directly. If the page is all-clear and only one of your applications has gone quiet, check that project's API key and reporting environment first.

How we measure this

We request Honeybadger's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Honeybadger publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Honeybadger itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Honeybadger goes down

We check Honeybadger every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required