Axiom statusLiveFetched seconds agoSource: status.axiom.co
Is Axiom down?
Live status check · All systems operational
Live status pulled from status.axiom.co, cached and revalidated every 60 seconds. Below: the components that can break, what to do during an incident, and how to keep your scheduled jobs running independently.
About Axiom status
Axiom is the developer-flavored observability and event log platform built around APL, its query language, and is used heavily by serverless and Vercel teams. Incidents typically hit one slice at a time: the ingestion endpoint, the APL query engine and dashboards, or the alerts pipeline.
Components and surfaces that can break
- Surface 01
Event ingestion endpoint (api.axiom.co).
- Surface 02
APL query engine and dashboards.
- Surface 03
Alerts and monitors.
What to do if Axiom is actually down
Buffer events client-side during ingestion outages
Most Axiom client libraries already buffer and retry on ingestion failures. Don't drop events on the floor: keep the buffer alive (in-memory, on-disk, or via your own queue) so once api.axiom.co accepts writes again, the backlog flushes and your timeline stays continuous.
Query outages don't mean data loss
If APL queries are failing or the dashboard is blank, that's a read-path problem, not a write-path one. Events that already arrived are still durably stored, and events arriving during the incident will land too. Once the query engine recovers, everything is queryable on the same timeline.
Pair Axiom alerts with an external watcher
If your alerts run inside Axiom on Axiom-stored data, an Axiom incident can silence them at the worst possible time. For anything safety-critical (paid uptime, payment errors, security signals), add an external heartbeat or watcher so a missing alert is itself an alert.
Keep firing through the incident
Schedule your own Axiom health check with Crontap
Hourly APL aggregate queries, daily anomaly digest to Slack, weekly retention exports. Crontap fires the endpoint that runs your APL query against Axiom's Query API and posts the result to your channel of choice.
External HTTP cron hits your endpoint on the cadence you pick, stores every response, and emails you the moment a run fails. Pro schedules down to 1 minute; $3.25/mo annual flat for unlimited jobs.
Go deeper
Axiom status: FAQ
- Where can I see the official Axiom status?
- status.axiom.co publishes component status for ingestion, query, dashboards, and alerts, plus a history feed at status.axiom.co/history.atom. Components are tracked separately, so a query incident does not necessarily mean ingestion is broken.
- Can I verify Axiom is receiving my events on a schedule?
- Yes. Schedule a small probe with Crontap that ingests a known synthetic event (e.g. a heartbeat with a unique id) and then runs an APL query a minute later asserting the event appeared. If ingestion or query is degraded, the probe fails and Crontap alerts you, independent of Axiom's own status page.
- What happens to my Axiom alerts if ingestion is delayed?
- Axiom alerts evaluate APL queries over data that has been ingested. If ingestion is delayed, the alert window may be empty or under-counted, and time-based thresholds can fail to trigger until the backlog catches up. After an ingestion incident, expect a burst of late-firing alerts as the buffered events arrive and re-enter the alert window.