Amplitude incident: We are actively investigating an issue with our realtime ingestion pipelines.

Affected components

• Data Export
• Data Processing
• Event Streaming

1. resolvedSep 10, 2026, 04:01 UTC

   This incident has been resolved.

2. monitoringSep 10, 2026, 03:21 UTC

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

3. investigatingSep 10, 2026, 03:07 UTC

   We are actively investigating an issue with our realtime ingestion pipelines. No data is lost.

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.

• Elasticsearch: Replication bug causing slow recoveriesMajor · Sep 1, 2026, 08:16 UTC
• MongoDB Atlas: Impaired Cluster operations in AWS me-central-1 and AWS me-south-1Major · Sep 3, 2026, 16:44 UTC
• Elasticsearch: Elastic Agent enrollment/check-in failures on 9.5.3 (and 9.4.6) with Fleet remote Elasticsearch outputMajor · Sep 9, 2026, 20:44 UTC
• Elasticsearch: Kibana access restored for UI-assigned Organization Owners on Hosted deploymentsMajor · Sep 10, 2026, 01:30 UTC
• Snowflake: INC20000150Minor · Aug 28, 2026, 00:07 UTC
• Telnyx: Intermittent delays for some outbound messagesMinor · Sep 2, 2026, 21:33 UTC
• ElevenLabs: Claude MCP connection not workingMinor · Sep 9, 2026, 12:41 UTC
• Telnyx: Failed/delayed call recording deliveries, faxes and conference establishmentMinor · Sep 9, 2026, 14:53 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