Is Axiom down?

Last checked 9m ago
Current status
Axiom is up

No incidents right now.

Official status page: https://status.axiom.co/# · Polled every 5 minutes · 12 components tracked

Axiom is operational right now. Last checked 9m ago; the most recent incident resolved 36d ago.

Real-time Axiom status, recent outages, and incident history — pulled directly from Axiom's official status page at https://status.axiom.co/# every 5 minutes. Pingoru tracks 12 Axiom services and has captured 3 incidents in the last 90 days (99.54% uptime). Get email, Slack, Discord, or webhook alerts the moment Axiom reports a new incident — free for 5 monitors, no credit card.

Users who monitor Axiom also follow these Cloud Infrastructure services: Amazon Web Services DigitalOcean Cisco Umbrella Wasabi Vercel Hetzner HashiCorp Egnyte Dyn Genesys Cloud View all 6,000+ providers
Axiom uptime 99.54% uptime · past 90 days
Mon Wed Fri
JunJulAugSep
Less More

Recent outages & incidents

Past 90 days
  1. Resolved
    Started Aug 12, 2026, 08:08 PM UTC · Resolved Aug 12, 2026, 08:08 PM UTC
    App
    Timeline · 5 updates
    • investigating · Aug 10, 2026, 05:08 PM UTC

      Status: Investigating Access to the Axiom Console is only available through Email, Google, and SAML/SSO authentication at present. Authentication with Github is unavailable. There is no impact on Axiom data or other services. Affected components App (Degraded performance)

    • identified · Aug 11, 2026, 06:35 AM UTC

      Status: Identified Access to Axiom Console through Github is unavailable. Other authentication methods are not affected. Resolution is expected soon. All Axiom data and other services are unaffected. Affected components App (Degraded performance)

    • identified · Aug 11, 2026, 12:13 PM UTC

      Status: Identified Access to the Axiom Console is only available through Email, Google, and SAML/SSO authentication at present. Authentication with Github is unavailable. There is no impact on Axiom data or other services. Affected components App (Degraded performance)

    • monitoring · Aug 11, 2026, 05:13 PM UTC

      Status: Monitoring Access to the Axiom Console through Github is available as well as all other authentication methods. We are monitoring for any further disruption. Users might experience a one-time email verification step for their Primary Github email. The Primary email address should be configured as the email used with an Axiom account. Additional verified emails can be used to access separate Axiom accounts. Affected components App (Operational)

    • resolved · Aug 12, 2026, 08:08 PM UTC

      Status: Resolved Access to the Axiom Console through Github is available as well as all other authentication methods. Users might experience a one-time email verification step for their Primary Github email. The Primary email address should be configured as the email used with an Axiom account. Additional verified emails can be used to access separate Axiom accounts. Affected components App (Operational)

    Latest: Status: Resolved Access to the Axiom Console through Github is available as well as all other authentication methods. Users might experience a one-time email verification step for …

  2. Resolved
    Started Jul 15, 2026, 10:26 AM UTC · Resolved Jul 15, 2026, 10:26 AM UTC
    Querying
    Timeline · 2 updates
    • investigating · Jul 15, 2026, 10:17 AM UTC

      Status: Investigating Some queries are failing due to recent deployment, we are on it. Affected components Querying (Degraded performance) Querying (Degraded performance)

    • resolved · Jul 15, 2026, 10:26 AM UTC

      Status: Resolved A revert has happened, the query service is now operating normally. The root cause has also been identified and we are actively working on it so queries are not affected again. Affected components Querying (Operational) Querying (Operational)

    Latest: Status: Resolved A revert has happened, the query service is now operating normally. The root cause has also been identified and we are actively working on it so queries are not af…

  3. Resolved
    Started Jun 30, 2026, 09:39 PM UTC · Resolved Jun 30, 2026, 09:39 PM UTC
    Ingest
    Timeline · 2 updates
    • investigating · Jun 30, 2026, 06:30 PM UTC

      Status: Investigating We are investigating reports of 403 errors when using Firehose (/v1/ingest/.../firehose) with our US edge domain. As a workaround, impacted customers can use our legacy ingest endpoint: https://api.axiom.co/v1/datasets/.../ingest/firehose. Affected components Ingest (Degraded performance)

    • resolved · Jun 30, 2026, 09:39 PM UTC

      Status: Resolved We have rolled back the changes we have made in our infrastructure to fix the firehose ingestion. Firehose ingestion should be back now. Affected components Ingest (Operational)

    Latest: Status: Resolved We have rolled back the changes we have made in our infrastructure to fix the firehose ingestion. Firehose ingestion should be back now. Affected components Ingest…

Outage history

Past 90 days · 3 incidents View full outage history →