Ingestion Halted for EAP data in EU
OutageThe issue with EAP ingestion in EU has been resolved.
Sentry is up and running. Sentry collects application errors and performance traces.
Worked out from the incidents Sentry reported, so it is an estimate and not a measurement.
Last incident: “Ingestion Halted for EAP data in EU”, 3 days ago.
The issue with EAP ingestion in EU has been resolved.
Dashboard is back to operational.
We have identified a networking issue with an upstream provider and are working on mitigations.
We are processing real-time data for all data types again.
Ingestion is now operating normally.
Sentry’s official status page says: All Systems Operational. This page checks it again when you load it, at most every 5 minutes.
The most recent incident Sentry reported was “Ingestion Halted for EAP data in EU”, 3 days ago (2026-10-14 05:46 UTC). Its last full outage started 3 days ago.
Sentry reports 41 components on its status page, including Dashboard, Slack, Password-Based, US Error Ingestion, EU Error Ingestion. Each is checked again whenever this page refreshes.
Pause deploys that depend on it, queue or retry failed jobs once it recovers, and check whether a mirror or cache can cover the gap.
Check the ingestion rows, not the app row. Sentry splits event ingestion, alerting and the dashboard, and ingestion is tracked separately for US and EU data residency.
Alerting ('US Errors Alerting', 'EU Errors Alerting') and the Slack/email integrations are separate components from ingestion — events are stored even when notifications lag.
If the status above is operational but Sentry still fails for you, the cause is probably on your side: try another network, clear the cache, or check your own connection. If it shows a degradation or an outage, others are affected too.
OpenUptime checks your site every minute and sends an alert to Slack, Telegram, email or a webhook the moment it stops responding. It is open source and free to start.