Axiom incident

Ingest through Firehose impacted

Resolved after 3 hours 9 minutes, affecting Ingest, on June 30, 2026.

resolved Jun 30, 2026, 09:39 PM UTC

We have rolled back the changes we have made in our infrastructure to fix the firehose ingestion. Firehose ingestion should be back now.

Started
Jun 30, 2026, 06:30 PM UTC
Resolved
Jun 30, 2026, 09:39 PM UTC
Duration
3h 9m
Detected by Pingoru
Jun 30, 2026, 06:30 PM UTC

Affected components

Ingest

Update timeline

  1. investigating Jun 30, 2026, 06:30 PM UTC

    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.

  2. resolved Jun 30, 2026, 09:39 PM UTC

    We have rolled back the changes we have made in our infrastructure to fix the firehose ingestion. Firehose ingestion should be back now.

Your product runs on more than Axiom

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →