Amplitude Outage History

The issue has been resolved, and the platform is operating normally again. Our Engineering team will continue to monitor the platform closely to ensure everything remains stable. Thank you for your patience and understanding while we worked to resolve this issue.

This incident has been resolved.

This incident has been resolved. We don't expect any data loss, and no action is required on your end.

From approximately 11:30 AM PDT (18:30 UTC) to 2:14 PM PDT (21:14 UTC), Amplitude experienced delays affecting the realtime data pipeline. Some data may have been delayed before appearing in Amplitude in real time. The issue has been resolved. There is no data loss, and no customer action is needed.

This incident has been resolved.

Some S3 export files delivered between September 9 at 20:32 UTC and September 10 at 04:01 UTC were missing the bucket-owner-full-control permission, which prevented affected customers from reading them. The issue is resolved. Exports moving forward and outside this timeframe are not impacted. No data was lost. For impacted files in the affected timeframe, set your bucket's Object Ownership to Bucket owner enforced (disable ACLs), if compatible with your bucket access requirements. If you have questions or continue to experience issues, please submit a support request.

This incident has been resolved.

Incident timeline Resolved — Amplitude is accessible once again, and customers should be able to access the platform as expected. Posted Aug 25, 2026 - 14:03 PT Investigating — Since approximately 13:48 PT, some customers may have experienced a brief interruption when using Amplitude. Posted Aug 25, 2026 - 13:48 PT We apologize for the disruption.

A fix was deployed, and the issue was fully resolved.

On 2026-08-19 at 10:41:25 AM PT, some customers who had not explicitly enabled AI through the AI Controls page were placed in “Admin preview,” and non-admin users could not access AI features. The issue was fully resolved at 12:41 PM PT on 2026-08-19. No data was impacted, and no customer action is required.

On 2026-08-13 at 7:45 PM PT (2:45 AM UTC on 2026-08-14), we experienced a data ingestion latency. The issue was fully resolved at 8:35 PM PT (3:35 AM UTC on 2026-08-14), and all data has since been recovered. There was no data loss, and no customer action is required.

This incident has been resolved.

Between approximately 2026-07-24 03:39–05:00 PT (10:39–12:00 UTC), some customers may have experienced intermittent connectivity issues while accessing Amplitude or sending data, including connection timeouts. This was caused by an AWS networking disruption in the us-west-2 region affecting multiple upstream AWS services. The issue originated outside of Amplitude's infrastructure and was resolved by AWS. Our SDKs queue undelivered events on-device and automatically retry sending them, so we expect minimal to no data loss from this incident. No ingested data was lost and no action is required.

This incident has been resolved.

We identified the source of the issue and rolled back the responsible change at 12:06 PM PT (19:06 UTC). Error rates have returned to normal, and we are actively monitoring to confirm full stability. There is no data loss. No customer action is needed at this time.

This incident has been resolved.

This incident has been resolved.

The incident has been resolved and the Custom Metrics metrics details page displays normally now.

This incident has been resolved.

This incident is resolved. Shared embeds and public links have been stable since 1:50 AM PT (08:50 UTC), and we have verified affected links render normally. A permanent fix ships later today. No data was lost and no customer action is needed.

All systems are caught up and functioning normally.

This incident has been resolved.

This incident has been resolved.

Service has been restored for the Amplitude application, and users should now be able to access the application normally. We have implemented a fix and are monitoring the system to ensure continued stability. We do not expect any data loss at this time. Thank you for your patience.