Sentry.io timeouts

What to do

• Check whether your product depends on Sentry. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 6h 39m it lasted.

  Anything that failed between 2026-05-11 15:32 UTC and 2026-05-11 22:11 UTC may need a replay.

• Subscribe to Sentry's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=sentry works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Sentry 7

1. investigatingMay 11, 2026, 3:32 PM UTC

   We are seeing increased UI and API timeouts and errors, due to an overloaded database cluster. Ingestion and alerting should not be affected

   provider

2. investigatingMay 11, 2026, 6:57 PM UTC

   We are continuing to investigate degraded database performance.

   provider

3. investigatingMay 11, 2026, 7:28 PM UTC

   Ingestion for spans, replays, and crons is delayed by about 15 minutes.

   provider

4. investigatingMay 11, 2026, 8:25 PM UTC

   Our event database continues to have issues and we are actively investigating the issue.

   provider

5. investigatingMay 11, 2026, 9:08 PM UTC

   We are working on restoring normal service. API and application performance should be improved, ingestion still has delays.

   provider

6. monitoringMay 11, 2026, 9:39 PM UTC

   We have implemented a fix and are monitoring the situation

   provider

7. resolvedMay 11, 2026, 10:11 PM UTC

   Database performance has returned to normal

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.