Is Axiom Down?

No — Axiom is up

Reachable from all 8 checked regions

Average response time: 845ms

Last checked 34 minutes ago · checks run every 6 hours

Official status page: https://status.axiom.co

Axiom uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

863ms

Avg response, 30 days

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

30-day history

64-day clean streak

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

817ms

DNS 26ms TCP 8ms TLS 28ms TTFB 816ms

lhr

527ms

DNS 20ms TCP 2ms TLS 7ms TTFB 527ms

nrt

1009ms

DNS 103ms TCP 1ms TLS 14ms TTFB 1008ms

ord

456ms

DNS 36ms TCP 1ms TLS 26ms TTFB 456ms

sin

1798ms

DNS 168ms TCP 1ms TLS 10ms TTFB 1797ms

sjc

506ms

DNS 25ms TCP 2ms TLS 12ms TTFB 505ms

syd

1063ms

DNS 61ms TCP 1ms TLS 6ms TTFB 1062ms

yyz

585ms

DNS 5ms TCP 12ms TLS 32ms TTFB 585ms

What Axiom does

Axiom is a managed store for logs, traces and events, queried with its own pipe-based language, APL. Teams send data in through OpenTelemetry collectors, Vector and similar agents and query it without managing indexes or capacity. It runs separate US and EU deployments, which matters for anyone with data residency requirements, and is used by engineering teams at Vercel and Cal.com among others.

What an outage looks like

The console fails to load or authentication stalls, so dashboards and saved queries are unreachable at the moment you need them. Ingest is the more serious failure: agents buffer and then drop events, leaving a gap in the dataset that persists after recovery. Queries can return partial results, and monitors built on Axiom stop firing, which looks like silence rather than an alert.

What to do about it

Check status.axiom.co and read your region, because Axiom reports its US and EU components separately and publishes uptime for each. Distinguish console problems from ingest problems: a degraded console still leaves data arriving, while an ingest fault creates a permanent gap. Axiom has run incidents affecting one authentication method only, so trying a different sign-in route is worth a moment before escalating.

Is it down for everyone, or just you?

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

Axiom outage FAQ

Is Axiom down for everyone or just my region?

Axiom operates separate US and EU deployments and reports them as distinct components with their own uptime figures, so an incident in one commonly leaves the other untouched. Check the region your organisation was provisioned in rather than the top-level banner. If both regions read operational, the problem is more likely your API token, your collector configuration or your network egress rules.

Do I lose log data during an Axiom outage?

It depends on what is failing. If the console is degraded but ingest is healthy, data keeps arriving and only your view of it is broken. If ingest is affected, your shippers buffer for as long as their configuration allows and then discard events, which leaves a permanent hole in the dataset. Collector buffer settings are what decide how much of an outage you survive.

Will my Axiom monitors still alert during an incident?

Assume not. Monitors evaluate data inside Axiom, so an ingest or query fault means they have nothing to fire on and you get silence instead of an alert. This is the failure mode worth planning for: an observability outage removes the thing that would tell you about other outages, so a second, independent signal for your most critical alerts is a reasonable precaution.

Can I still sign in if Axiom authentication is degraded?

Often yes, through a different method. Axiom has published incidents where console access via one identity provider was unavailable while other sign-in routes kept working and all stored data was unaffected. If your usual login fails, try an alternative before assuming the platform is down, and read the component line rather than the banner, which will report the whole console as degraded.

How we measure this

We request Axiom'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 Axiom 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 Axiom 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