Live / Amplitude / Incident
Amplitude: Delayed S3 export
Amplitude · amplitude.comMinor incidentResolved2026-11-05 16:12 UTC
Public — what happened
Summary
Amplitude said its S3 Data Export was delayed for some customers on November 5, with the affected period running from 5:00 AM to 10:18 AM UTC and the affected export pipelines blocked. The company said it did not expect any data to be lost. Later that day it reported that the problem had been identified and reduced, though it warned it could come back until a fix was in place. By 15:11 UTC a fix was in place and exports were catching up, and the incident was marked resolved at 16:12 UTC.
Affected
Data Export
Timeline
- Started — 2026-11-05 14:22 UTC
- Investigating — 2026-11-05 14:22 UTC
- Identified — 2026-11-05 14:42 UTC
- Monitoring — 2026-11-05 15:11 UTC
- Resolved — 2026-11-05 16:12 UTC · 1h 49m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Amplitude against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Amplitude: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Amplitude report →
More from Amplitude
Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.