Skip to main content
Airbrake logo

Is Airbrake Down?

No — Airbrake is up

Reachable from all 8 checked regions

Average response time: 691ms

Last checked · checks run every 6 hours

Official status page: https://status.airbrake.io

Airbrake uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
934ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 34 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

34-day clean streak
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 32 checks
Sep 17: 100.00% uptime, 32 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 32 checks
Sep 21: 100.00% uptime, 32 checks
Sep 22: 100.00% uptime, 32 checks
Sep 23: 100.00% uptime, 36 checks
Sep 24: 100.00% uptime, 32 checks
Sep 25: 100.00% uptime, 32 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 47 checks
Sep 30: 100.00% uptime, 32 checks
Oct 1: 100.00% uptime, 32 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 31 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 31 checks
Sep 14 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
599ms
DNS 50ms TCP 22ms TLS 47ms TTFB 577ms
arn
794ms
DNS 78ms TCP 35ms TLS 73ms TTFB 747ms
cdg
716ms
DNS 65ms TCP 24ms TLS 51ms TTFB 688ms
dfw
575ms
DNS 255ms TCP 29ms TLS 62ms TTFB 544ms
ewr
500ms
DNS 270ms TCP 7ms TLS 18ms TTFB 486ms
fra
478ms
DNS 29ms TCP 21ms TLS 46ms TTFB 450ms
gru
1518ms
DNS 256ms TCP 124ms TLS 253ms TTFB 1296ms
yyz
351ms
DNS 113ms TCP 18ms TLS 40ms TTFB 333ms

What Airbrake does

Airbrake is an error and performance monitoring service for web and mobile applications. Client libraries embedded in an application report exceptions to Airbrake, which groups them, keeps their history and notifies the team. It also tracks deploys, so a spike in errors can be tied to the release that caused it. Teams rely on it to learn that something else has broken.

What an outage looks like

New errors stop appearing in the dashboard and the application looks healthier than it is, which is the symptom worth recognising fastest. The dashboard itself may fail to load or return errors while your application keeps reporting normally. Deploy markers stop being recorded, so the release timeline develops a gap. Alert notifications may stop while collection continues.

What to do about it

Read status.airbrake.io, which reports eight components: Web App, Notifier API, Read API, Notifications, Airbrake Notifiers, Deploy Tracking, Performance Monitoring API and Website. Match your symptom to the row before drawing conclusions. If only Read API or Web App is affected, your errors are still being received and the gap is in your view of them, not in the record.

Is it down for everyone, or just you?

If this page says Airbrake 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

Sentry
Sentry
Honeybadger
Honeybadger
Rollbar
Rollbar
Bugsnag
Bugsnag

Airbrake outage FAQ

My Airbrake dashboard is empty. Does that mean no errors were recorded?
Not necessarily. Airbrake reports Notifier API, the endpoint your application sends to, as a component separate from Read API, which serves what you look at. An empty or failing dashboard during an incident is consistent with errors still arriving and simply not being readable yet. Check which of the two rows is affected on status.airbrake.io before concluding that an incident window is missing from your error history.
Will errors sent during an Airbrake outage be lost?
Airbrake notifier libraries send reports over the network without blocking your application, and they are not an unlimited buffer. Airbrake does not publish a guarantee covering every failure mode, so treat the incident window as a possible gap rather than assuming full capture. If you need certainty about what happened during that period, your own application logs are the record to check.
I stopped getting Airbrake alerts. Is everything fine?
Silence from an error monitor is ambiguous and should not be read as good news. Airbrake reports Notifications as a component separate from error ingestion, so errors can keep being collected while no message reaches your inbox or chat. During an incident, open the dashboard directly on a schedule rather than waiting for an alert that may not be able to arrive.
Is it Airbrake or my own integration?
Compare scope. A bad API key, a misconfigured environment or a notifier library that failed to initialise affects one application or one deploy, and other projects in the same account keep reporting. An Airbrake incident affects every project at once. Airbrake also lists Airbrake Notifiers as its own component, so check that row before you start rewriting your integration.
Does an Airbrake outage affect deploy tracking separately?
Yes, Deploy Tracking is its own component. A deploy made during an incident can be missed even while errors continue to be recorded, which leaves the release timeline with a gap and makes it harder to attribute a later error spike to the correct version. If a deploy falls inside an incident window, note the version yourself so the correlation is not lost.

How we measure this

  • We request Airbrake's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • 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. We only change the 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 Airbrake publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Airbrake goes down

This page refreshes every 6 hours. 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