Vendor reports: degradedResolved · vendor status “resolved”Official status API

Ingestion backlog

Reported by Sentry · Developer Tools & CI/CD · source last read 3 min ago

Vendor start
Aug 31, 2026, 20:31 UTC
Vendor's clock
Resolved
Aug 31, 2026, 22:43 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
2 h 12 min
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Sentry reports degraded: "Ingestion backlog".[E1, E2]
  • The vendor marked it resolved at 2026-08-31 22:43 UTC.[E3, E7]

Affected products and regions

  • Components: US Error Ingestion, US Errors Alerting, API, US Transaction Ingestion, US Attachment Ingestion, US Profile Ingestion, US Spans Alerting, US Replay Ingestion, US Span Ingestion, US Cron Monitoring, US Uptime Monitoring, Integration Pipeline, Custom Metrics (beta), US Size Analysis Ingestion, Seer, US Snapshot Ingestion.[E6]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-08-31 22:43 UTC · summary s1, evidence 0368957e98b0af5a

Evidence (7)
  1. E1Sentry reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Ingestion backlog". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-08-31 20:31 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: US Error Ingestion, US Errors Alerting, API, US Transaction Ingestion, US Attachment Ingestion, US Profile Ingestion, US Spans Alerting, US Replay Ingestion, US Span Ingestion, US Cron Monitoring, US Uptime Monitoring, Integration Pipeline, Custom Metrics (beta), US Size Analysis Ingestion, Seer, US Snapshot Ingestion. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-08-31 22:43 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: US Error Ingestion, US Errors Alerting, API, US Transaction Ingestion, US Attachment Ingestion, US Profile Ingestion, US Spans Alerting, US Replay Ingestion, US Span Ingestion, US Cron Monitoring, US Uptime Monitoring, Integration Pipeline, Custom Metrics (beta), US Size Analysis Ingestion, Seer, US Snapshot Ingestion

No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.

Potential relevance

Sentry is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Aug 31, 2026, 20:31 UTCVendor-reported startVendor time
  2. Aug 31, 2026, 22:43 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.