Amplitude incident: Slower realtime processing

Affected components

• Data Export
• Data Processing
• Event Streaming

1. resolvedMay 15, 2026, 02:03 UTC

   This incident has been resolved.

2. monitoringMay 14, 2026, 22:47 UTC

   A fix has been implemented and we are monitoring the results.

3. investigatingMay 14, 2026, 22:47 UTC

   We are continuing to investigate this issue.

4. investigatingMay 14, 2026, 21:42 UTC

   We are noticing slower than normal processing in our ingestion pipelines

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Amplitude's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Confluent Cloud: Elevated error rates and latency on produce and consume operations on AWS us-east-1 AZ4Major · May 8, 2026, 01:14 UTC
• New Relic: UI and Data Irregularities - US RegionMajor · May 15, 2026, 00:06 UTC
• DigitalOcean: Anthropic reported outage that's impacting access to their Serverless Inference modelsMajor · May 15, 2026, 01:21 UTC
• Linode: [DirtyFrag] Linux Privilege Escalation VulnerabilityMinor · May 8, 2026, 13:40 UTC
• Linode: [Fragnesia] Linux Privilege Escalation VulnerabilityMinor · May 13, 2026, 21:02 UTC
• Mixpanel: Query API degraded performanceMinor · May 14, 2026, 23:17 UTC

How often does Amplitude have incidents?

Amplitude reported 17 incidents in the last 90 days, 7 of them major or critical. A typical incident lasted 2h 23m. See Amplitude's uptime and incident history