# Ingest through Firehose impacted

- Provider: [Axiom](https://down.guide/axiom)
- Level: confirmed
- Impact: Degraded
- lasted 3h 9m
- started 2026-06-30 18:30 UTC
- us
- id: DWN-19d43b23a0
- Official page: https://status.axiom.co/incidents/01KWCWQZVFN8SH115DQY7CYVC1

## Updates from Axiom
### 2026-06-30 18:30 UTC: 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.

### 2026-06-30 21:39 UTC: resolved
We have rolled back the changes we have made in our infrastructure to fix the firehose ingestion.
Firehose ingestion should be back now.

From the builder: does your app depend on Axiom? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=axiom) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Axiom.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-19d43b23a0), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
