Amplitude

Affected: Data Export

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-20 20:13 UTC

   We are investigating errors affecting some customers using the Data Export API. Affected Export API requests may return 500 errors.

2. resolved 2026-10-20 20:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Amplitude's status page.

Affected: Data Processing, Event Streaming, Data Export

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-10-17 14:45 UTC

   A fix has been implemented and we are monitoring the recovery. No data is lost.

2. monitoring 2026-10-17 15:47 UTC

   We are continuing to monitor for any further issues.

3. resolved 2026-10-17 16:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Amplitude's status page.

Affected: Web Application

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-10-13 18:53 UTC

   Since 2026-10-13 00:28 PT (07:28 UTC), we have identified an issue affecting Funnel charts in light theme where the conversion percentage data label displays as unreadable white text on a white background. This issue has been resolved as of 2026-10-13 01:24 PT (08:24 UTC). The...

Excerpts are shortened. Read the full incident on Amplitude's status page.

Affected: Data Export

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-10-08 03:33 UTC

   We are currently investigating an issue where all BigQuery exports are lagging for US (not EU) due to a downstream issue.

2. identified 2026-10-08 04:09 UTC

   A small fraction of new jobs are still getting stuck, we are continuing to investigate further.

3. monitoring 2026-10-08 04:36 UTC

   Currently recovering backlog of effected jobs successfully, monitoring closely for full recovery.

4. resolved 2026-10-08 05:04 UTC

   This incident has been resolved

Excerpts are shortened. Read the full incident on Amplitude's status page.

Affected: Guides & Surveys

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-10-05 18:56 UTC

   Between 11:40 AM and 11:48 AM PT on October 5, 2026, Amplitude experienced a full outage of the Guides and Surveys service. During this time, users may have been unable to create, publish, or edit Guides and Surveys, or may have seen Guides and Surveys fail to load for end...

Excerpts are shortened. Read the full incident on Amplitude's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-02 18:35 UTC

   Beginning at approximately 11:15 AM PT, we are currently investigating an issue affecting the Amplitude US environment. Some customers may experience slow page loads, pages that fail to load, or errors when accessing the Amplitude platform. Our Engineering team is actively...

2. investigating 2026-10-02 18:36 UTC

   We are continuing to investigate this issue.

3. resolved 2026-10-02 18:43 UTC

   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.

Excerpts are shortened. Read the full incident on Amplitude's status page.

Affected: Data Export

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-28 21:09 UTC

   We are actively investigating an incident in our data exports. Once the issue is resolved, data will continue to be exported. No data is lost.

2. investigating 2026-09-28 21:09 UTC

   We are continuing to investigate this issue.

3. identified 2026-09-28 23:37 UTC

   Warehouse exports should now start exporting data to warehouses and storage buckets but explicit export APIs are still blocked.

4. resolved 2026-09-29 02:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Amplitude's status page.

Affected: Data Export

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-24 19:47 UTC

   Since 2026-09-24 09:30 PT (17:30 UTC), Amplitude has been experiencing a delay in Data Export processing due to a lagging data partition. Realtime data processing and Amplitude charts and dashboards are not impacted. No data is being lost, and delayed exports will complete once...

2. identified 2026-09-24 19:58 UTC

   The issue has been identified and a fix is being implemented. We will provide another update in 30 minutes.

3. monitoring 2026-09-24 20:13 UTC

   A fix has been implemented and we are monitoring the results. We will provide another update in 30 minutes.

4. monitoring 2026-09-24 20:43 UTC

   We are continuing to monitor for any further issues. We will provide another update in 30 minutes.

5. resolved 2026-09-24 21:22 UTC

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

Excerpts are shortened. Read the full incident on Amplitude's status page.

Affected: Data Export

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-23 08:02 UTC

   Since 2026-09-22 16:50 PT (23:50 UTC), we have been experiencing an issue with automated data exports to all export destinations. This only affects exports that filter events before export. Customers using export destinations may notice that new data is not being delivered to...

2. monitoring 2026-09-23 08:39 UTC

   Since 2026-09-22 16:50 PT (23:50 UTC), we experienced an issue with automated data exports to export destinations that filter events before export. We have deployed a fix and are now monitoring the system to confirm exports and backfills fully recover. No data has been lost. No...

3. monitoring 2026-09-23 09:13 UTC

   We continue to monitor system recovery following the deployed fix for automated data exports. No customer action is required at this time.

4. monitoring 2026-09-23 09:45 UTC

   We continue to monitor system recovery following the deployed fix for automated data exports. No customer action is required at this time.

5. monitoring 2026-09-23 10:19 UTC

   We're still working to confirm that automated data exports are getting back to normal. No customer action is required at this time.

6. monitoring 2026-09-23 10:43 UTC

   We've identified that this issue can also affect exports without event filtering, due to backlog from the affected jobs. Previously we noted impact was limited to exports with event filtering, we're updating that guidance as we've confirmed broader impact. If you're experiencing...

7. monitoring 2026-09-23 11:25 UTC

   We're seeing recovery across most affected export jobs, and most customers should now see exports returning to normal. A subset of jobs are still catching up, and we're continuing to monitor until all exports are fully recovered. No customer action is required at this time.

8. monitoring 2026-09-23 12:47 UTC

   Automatic export jobs are running again for most customers. Recovery looks on track, though we're still confirming full resolution and continuing to monitor closely. No customer action is required at this time

9. monitoring 2026-09-23 14:07 UTC

   We are continuing to monitor for any further issues.

10. resolved 2026-09-23 14:07 UTC

    This incident has been resolved. All affected export jobs have fully recovered and are running normally. We don't expect any data loss, and no action is required on your end.

Excerpts are shortened. Read the full incident on Amplitude's status page.

Affected: Data Export

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-22 18:49 UTC

   Starting at 17:00 UTC, new data is not being delivered to Snowflake Data Share destinations. Existing shared data remains available, and data ingestion and analytics in Amplitude are not affected. No data loss is expected. Our team has identified an authentication issue on our...

2. identified 2026-09-22 19:19 UTC

   The authentication issue and fix path have been identified; implementation is in progress. No data loss is expected. No customer action is needed. We will share another update in 30 minutes.

3. identified 2026-09-22 19:50 UTC

   Implementation of a fix is in progress. Snowflake Data Share delivery remains affected. No data loss is expected, and no customer action is needed. Delayed data will be delivered once the issue is resolved. We will provide another update in 30 minutes.

4. identified 2026-09-22 20:19 UTC

   We continue to work on implementing a fix for the authentication issue affecting Snowflake Data Share delivery. Delivery remains affected. No data loss is expected, and no customer action is needed. Delayed data will be delivered once the issue is resolved. We will provide...

5. identified 2026-09-22 20:49 UTC

   We continue to work on implementing a fix for the authentication issue affecting Snowflake Data Share delivery. Data Share delivery remains affected. No data loss is expected, and no customer action is needed. Delayed data will be delivered once the issue is resolved. We will...

6. identified 2026-09-22 21:19 UTC

   We continue to work on implementing a fix for the authentication issue affecting Snowflake Data Share delivery. Data Share delivery remains affected. No data loss is expected, and no customer action is needed. Delayed data will be delivered once the issue is resolved. We will...

7. identified 2026-09-22 21:50 UTC

   Implementation of a fix is in progress. Snowflake Data Share delivery remains affected. No data loss is expected, and no customer action is needed. Delayed data will be delivered once the issue is resolved. We will provide another update in 30 minutes.

8. identified 2026-09-22 22:20 UTC

   Our team is continuing to work on a fix for the authentication issue affecting Snowflake Data Share delivery. Data Share delivery remains affected. No data loss is expected, and no customer action is needed. Delayed data will be delivered once the issue is resolved. We will...

9. identified 2026-09-22 22:50 UTC

   Implementation of a fix is in progress. Snowflake Data Share delivery remains affected. No data loss is expected, and no customer action is needed. Delayed data will be delivered once the issue is resolved. We will provide another update in 30 minutes.

10. identified 2026-09-22 23:21 UTC

    Implementation of a fix is still in progress. Snowflake Data Share delivery remains affected. No data loss is expected, and no customer action is needed. Delayed data will be delivered once the issue is resolved. We will provide another update in 30 minutes.

11. identified 2026-09-22 23:50 UTC

    We are deploying a fix for the issue affecting Snowflake Data Share delivery and will verify recovery once deployment is complete. Data Share delivery remains affected. No data loss is expected, and no customer action is needed. Delayed data will be delivered once the issue is...

12. monitoring 2026-09-22 23:53 UTC

    A fix has been deployed for the issue affecting Snowflake Data Share delivery. We are monitoring recovery. No data loss is expected, and no customer action is needed. Delayed data will be delivered once the issue is resolved. We will provide another update in 30 minutes.

13. monitoring 2026-09-23 00:23 UTC

    The authentication issue affecting Snowflake Data Share delivery has been fixed. We are monitoring recovery as delayed data is processed. No data loss is expected, and no customer action is needed. We will provide another update in 30 minutes.

14. resolved 2026-09-23 00:53 UTC

    The authentication issue affecting Snowflake Data Share delivery has been resolved. Snowflake Data Share exports are operating normally. No data loss is expected, and no customer action is needed.

Excerpts are shortened. Read the full incident on Amplitude's status page.

Affected: Data Processing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-17 20:05 UTC

   Since 11:30 AM PST, Amplitude has been experiencing a realtime data pipeline delay. Some data may not yet appear in Amplitude in real time and may be delayed before it can be streamed or exported to downstream destinations. Our team is actively investigating the source of the...

2. investigating 2026-09-17 20:05 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-09-17 20:34 UTC

   Recovery is underway, and we are monitoring the system to confirm full recovery. There is no data loss, and no customer action is needed. We will provide the next update in 30 minutes.

4. monitoring 2026-09-17 21:05 UTC

   We are continuing to monitor the system to confirm full recovery. There is no data loss, and no customer action is needed. We will provide the next update in 30 minutes.

5. resolved 2026-09-17 21:15 UTC

   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...

Excerpts are shortened. Read the full incident on Amplitude's status page.

Affected: Data Processing, Event Streaming, Data Export

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-10 03:07 UTC

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

2. monitoring 2026-09-10 03:21 UTC

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

3. resolved 2026-09-10 04:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Amplitude's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-09-09 20:32 UTC

   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...

Excerpts are shortened. Read the full incident on Amplitude's status page.

Affected: Data Processing, Event Streaming, Data Export

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-26 15:23 UTC

   We are currently investigating this issue.

2. identified 2026-08-26 15:54 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-08-26 16:51 UTC

   A fix has been implemented, and we are monitoring the results. Realtime data processing remains delayed, but events are catching up. No data was lost, and no customer action is required. We will provide another update when more information is available.

4. resolved 2026-08-26 18:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Amplitude's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-08-25 20:48 UTC

   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...

Excerpts are shortened. Read the full incident on Amplitude's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-25 02:06 UTC

   Since 2026-08-24 16:45 PT (23:45 UTC), new sign-ins were unable to load the Amplitude login page (app.amplitude.com/login), which appeared blank. Users with an active session were not signed out and could continue working as normal.

2. monitoring 2026-08-25 03:03 UTC

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

3. resolved 2026-08-25 03:23 UTC

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

Excerpts are shortened. Read the full incident on Amplitude's status page.

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-08-19 17:41 UTC

   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...

Excerpts are shortened. Read the full incident on Amplitude's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-08-14 02:30 UTC

   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.

Excerpts are shortened. Read the full incident on Amplitude's status page.

Affected: Data Processing, Event Streaming, Data Export

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-12 23:39 UTC

   Since 2026-08-12 16:39 PT (23:39 UTC), we have been experiencing a delay in realtime data processing. We are actively investigating the source of the issue and will work to deploy a fix. No data is lost.

2. monitoring 2026-08-13 00:54 UTC

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

3. monitoring 2026-08-13 01:32 UTC

   We are continuing to monitor for any further issues.

4. monitoring 2026-08-13 02:45 UTC

   Data processing is now recovering. There is no data loss, and all data will continue to be sent to downstream destinations once processed. No customer action is needed at this time. We estimate full recovery within the next 1-2 hours and will provide our next update within 30...

5. monitoring 2026-08-13 02:58 UTC

   We are continuing to monitor for any further issues.

6. resolved 2026-08-13 03:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Amplitude's status page.

Affected: Data Processing, Event Streaming, Data Export

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-02 05:45 UTC

   We are investigating a delay in real time data processing. No data is lost

2. monitoring 2026-08-02 05:59 UTC

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

3. resolved 2026-08-02 06:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Amplitude's status page.

Affected: Data Processing, Event Streaming, Data Export

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-01 02:07 UTC

   We are actively investigating a delay in our pipeline processing. No data is lost.

2. monitoring 2026-08-01 02:53 UTC

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

3. monitoring 2026-08-01 03:47 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-08-01 03:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Amplitude's status page.

Affected: Web Application, Data Processing, Data Reception

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. resolved 2026-07-24 17:05 UTC

   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...

Excerpts are shortened. Read the full incident on Amplitude's status page.

Affected: Data Export

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-24 14:45 UTC

   We are currently investigating this issue.

2. monitoring 2026-07-24 15:15 UTC

   The jobs waiting on google's end have started recovering and we are seeing jobs making progress within Amplitude too

3. resolved 2026-07-24 15:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Amplitude's status page.

Affected: Data Processing, Event Streaming, Data Export

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-23 14:35 UTC

   We are actively investigating a delay in real time data processing. No data is lost.

2. identified 2026-07-23 14:46 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-07-23 14:52 UTC

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

4. resolved 2026-07-23 17:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Amplitude's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-07-22 20:20 UTC

   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.

Excerpts are shortened. Read the full incident on Amplitude's status page.

Affected: Web Reporting, Web Application, Web Application, Web Application, Web Application, MCP

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-13 21:31 UTC

   Since 2026-07-13 14:04 PT, we have been experiencing issues with the Amplitude user interface (UI) MCP and rest APIs. Our team is actively investigating the source of the issue and will work to deploy a fix. We expect no data loss. No customer action is needed at this time. EU...

2. investigating 2026-07-13 21:32 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-07-13 21:53 UTC

   A fix has been implemented, and we're monitoring the results

4. resolved 2026-07-13 23:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Amplitude's status page.

Affected: Agents and Chat

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-13 18:51 UTC

   Some users may be unable to load or use AI-powered features. We are investigating and will provide updates as more information becomes available.

2. investigating 2026-07-13 23:16 UTC

   We are continuing to investigate this issue.

3. resolved 2026-07-13 23:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Amplitude's status page.

Affected: Web Reporting

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-13 11:41 UTC

   Since 2026-07-12 11:47:42 PM PDT (2026-07-13 07:47:42 AM CET), we have been experiencing issues with the Amplitude user interface (UI). Currently, the Custom Metrics metric details page may fail to load or display an error. Our team is actively investigating the source of the...

2. identified 2026-07-13 14:05 UTC

   We have identified the root cause and a fix is being deployed. We will post an update as the deployment completes.

3. monitoring 2026-07-13 14:32 UTC

   A fix has been deployed and the metric details page is loading normally again. We are monitoring error rates to confirm full recovery across all regions before resolving. No data was lost during this incident.

4. resolved 2026-07-13 14:59 UTC

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

Excerpts are shortened. Read the full incident on Amplitude's status page.

Affected: Web Application, Web Application, Web Application, Guides & Surveys, Session Replay

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-13 06:15 UTC

   We are investigating elevated latency affecting services in our EU production environment. Some customers may experience slower response times while our team works to identify the cause and mitigate impact. We will provide another update within 60 minutes or sooner if we have...

2. investigating 2026-07-13 07:56 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-07-13 08:20 UTC

   We implemented a rollback to mitigate elevated latency affecting services in our EU production environment, and performance has recovered. We are continuing to monitor the environment closely to confirm stability.

4. resolved 2026-07-13 08:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Amplitude's status page.

Affected: Web Reporting

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-07-09 09:12 UTC

   Between 2026-07-08 5:24 PM PT (00:24 UTC Jul 9) and 2026-07-09 1:50 AM PT (08:50 UTC), shared embeds and public dashboard/chart links displayed blank pages. Customers accessing shared Amplitude content via embed URLs or public links were unable to view charts during this window....

2. resolved 2026-07-09 09:45 UTC

   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.

Excerpts are shortened. Read the full incident on Amplitude's status page.

Affected: Data Processing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-07-05 15:56 UTC

   Our data processing systems are delayed. This incident started at 6:30 PDT. Current status: Our ingestion systems are working as expected and no data is lost. We've identified the issue and the data processing system is catching up now. ETA to fully resolved is ~2hours (11 PDT)

2. monitoring 2026-07-05 18:06 UTC

   Realtime data is fully caught up and available all features within Amplitude should have data fully available. Some export data from the past hour may still be delayed.

3. resolved 2026-07-05 19:11 UTC

   All systems are caught up and functioning normally.

Excerpts are shortened. Read the full incident on Amplitude's status page.

Affected: Data Processing, Event Streaming, Data Export

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-18 19:29 UTC

   We are currently investigating this issue. No data is lost.

2. monitoring 2026-06-18 21:03 UTC

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

3. investigating 2026-06-18 22:21 UTC

   We are currently investigating this issue.

4. monitoring 2026-06-18 23:59 UTC

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

5. monitoring 2026-06-19 02:26 UTC

   We are continuing to monitor for any further issues.

6. resolved 2026-06-19 04:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Amplitude's status page.

Affected: Data Processing, Event Streaming, Data Export

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-04 18:55 UTC

   We are actively investigating an issue where our realtime data ingestion is lagging. No data is lost.

2. monitoring 2026-06-04 19:17 UTC

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

3. monitoring 2026-06-04 21:02 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-06-04 23:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Amplitude's status page.

Affected: Web Application, Web Application, Web Application, Web Application, Guides & Surveys, Session Replay

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-06-03 13:13 UTC

   We are aware of renewed issues affecting the Amplitude application. Some users may currently be unable to access the application or may experience errors when loading the interface. We have identified the issue and are actively working to restore service. We do not expect any...

2. resolved 2026-06-03 13:26 UTC

   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...

Excerpts are shortened. Read the full incident on Amplitude's status page.

Affected: Web Reporting, Web Application, Web Application, Web Application, Web Application, Guides & Surveys, Session Replay

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-03 12:25 UTC

   Since 2026-06-03 04:58 AM PT (11:58 AM UTC), we have been experiencing issues with the Amplitude platform. Currently, users may be unable to access the Amplitude application or experience significant errors when attempting to load the interface. Our team is actively...

2. resolved 2026-06-03 12:52 UTC

   We have resolved the issue affecting the Amplitude application, and services are operating normally again. We do not expect any data loss as a result of this incident. Our team will continue to monitor the system to ensure stability. Thank you for your patience.

Excerpts are shortened. Read the full incident on Amplitude's status page.

Affected: Web Application, Web Application, Web Application, Guides & Surveys, Session Replay, Heatmaps

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-22 02:51 UTC

   We are currently investigating elevated application latency affecting portions of the platform. Users may experience slower page loads, delayed query responses, or intermittent timeouts.

2. monitoring 2026-05-22 06:06 UTC

   We have identified the root cause and implemented a fix. We are currently monitoring the application to ensure performance remains stable and services continue to recover as expected.

3. resolved 2026-05-22 06:32 UTC

   The issue causing elevated application latency has been resolved. We have confirmed that system performance has returned to normal levels and continue to monitor closely to ensure ongoing stability.

Excerpts are shortened. Read the full incident on Amplitude's status page.

Affected: Data Processing, Event Streaming, Data Export

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-19 12:45 UTC

   We are actively investigating a lag in processing data in EU. All data is received and no data is lost.

2. monitoring 2026-05-19 12:58 UTC

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

3. resolved 2026-05-19 13:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Amplitude's status page.

Affected: Data Processing, Event Streaming, Data Export

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-14 21:42 UTC

   We are noticing slower than normal processing in our ingestion pipelines

2. investigating 2026-05-14 22:47 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-05-14 22:47 UTC

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

4. resolved 2026-05-15 02:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Amplitude's status page.

Affected: Data Processing, Data Export

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-05 19:13 UTC

   We are investigating an incident in our batch ingestion pipeline that is causing ingestion issues in 1 partition. No data is lost and we are actively working on remediating this delay.

2. monitoring 2026-05-05 19:27 UTC

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

3. resolved 2026-05-05 19:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Amplitude's status page.

Affected: Evaluation API, Data Processing, Cohort Export, Amazon Web Services

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-04-29 08:15 UTC

   Our data processing systems are delayed. This incident started at 2026-04-29 12:20 AM PT. Current status: a) Our ingestion systems are working as expected and no data is lost. Our processing systems are not processing newly ingested data. b) Impacted customers will see delayed...

2. identified 2026-04-29 08:20 UTC

   Our data processing systems are delayed. This incident started at 2026-04-29 12:20 AM PT. Current status: a) Our ingestion systems are working as expected and no data is lost. Our processing systems are not processing newly ingested data. b) Impacted customers will see delayed...

3. identified 2026-04-29 08:30 UTC

   AWS has identified the issue and is actively working on a resolution. We will provide an update within the next hour, or sooner if new information becomes available.

4. monitoring 2026-04-29 08:39 UTC

   AWS and Amplitude has mitigated the issue and are seeing recovery on impacted services. We will continue to monitor the status and provide an update within the next hour, or sooner if new information becomes available.

5. monitoring 2026-04-29 08:59 UTC

   We are continuing to monitor for any further issues.

6. monitoring 2026-04-29 09:10 UTC

   We are continuing to monitor for any further issues.

7. monitoring 2026-04-29 09:54 UTC

   The issue has been resolved.

8. resolved 2026-04-29 14:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Amplitude's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2026-04-28 17:00 UTC

   The Amplitude web application in the US was briefly inaccessible. We identified the issue to be related to a misconfigured feature flag. The issue started at 10:00 AM PST, lasting 10 minutes, and is now resolved.

Excerpts are shortened. Read the full incident on Amplitude's status page.

Affected: Web Application, Web Application, Web Application, Web Application, Guides & Surveys, MCP

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-04-23 19:56 UTC

   Amplitude web application in US is not accessible. The issue started around 12:20 PST we're still investigating the root cause. Amplitude in EU is working as expected. a) Our ingestion systems were working as expected and we were not losing any data. b) Impacted customers might...

2. monitoring 2026-04-23 20:02 UTC

   We have identified the issue to be related to a misconfigured configuration in our feature flags. We have reverted the change as of 1PM PT and we should be back to normal now. We'll still monitor this for a bit before resolving the issue.

3. resolved 2026-04-23 20:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Amplitude's status page.

Affected: Event Streaming

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-04-15 23:09 UTC

   Since 2026-04-15 12:20 PT (19:20 UTC), Amplitude has been experiencing high latency in Event Streaming. Current status: a) Our ingestion and data processing systems are working as expected and no data is lost. b) All of our customers are impacted. c) Impacted customers will see...

2. monitoring 2026-04-16 00:20 UTC

   Event streaming has largely recovered. Fewer than 1% of events are still experiencing delays of over 30 minutes. We’ll provide another update once latency has returned to normal for all data.

3. monitoring 2026-04-16 00:21 UTC

   Event streaming has largely recovered. Fewer than 1% of events are still experiencing delays of over one hour. We’ll provide another update once latency has returned to normal for all data.

4. resolved 2026-04-16 01:11 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Amplitude's status page.

Affected: Guides & Surveys

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-04-13 15:45 UTC

   At 8:45 am PDT, Guides and Surveys added a large number of event properties. Which projects are impacted? Any project that previously had less than 2000 event properties and that now has 2000 or more event properties. What's the impact? All such projects are unable to (a) add...

2. monitoring 2026-04-13 20:53 UTC

   Erroneous events have been deleted. Event property limits should be accurate again and new event properties should be usable again. Any event properties that came in only during the overage window (and haven't been sent again since) will not be usable until post-processing...

3. resolved 2026-04-13 21:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Amplitude's status page.

Affected: Data Reception

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-12 08:24 UTC

   Since 2026-04-12 00:43 PT (07:43 UTC), the EU data collection endpoint (api.eu.amplitude.com) has been experiencing service disruptions. Customers sending event data to the EU endpoint may encounter errors, and data ingestion may be temporarily unavailable. Our team is actively...

2. investigating 2026-04-12 09:52 UTC

   We are continuing to investigate this issue

3. monitoring 2026-04-12 10:47 UTC

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

4. resolved 2026-04-12 10:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Amplitude's status page.

Affected: CLI/Codegen, MCP

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-06 19:53 UTC

   We are currently investigating an issue affecting user authentication for: Ampli CLI, MCP Server, Notion/Atlassian chart previews.

2. monitoring 2026-04-06 23:39 UTC

   A fix has been implemented, and we are monitoring recovery. Some users may need to re-authenticate the following components to restore full functionality: • Ampli CLI • MCP Server • Notion and Atlassian chart previews

3. resolved 2026-04-07 00:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Amplitude's status page.

Affected: Web Reporting, Evaluation API, Web Application, Web Application, Web Application, Data Processing, Web Application, Guides & Surveys, Event Streaming, Data Export, Session Replay, AI Feedback, Agents and Chat

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-03 21:52 UTC

   We are currently investigating a site-wide outage.

2. investigating 2026-04-03 21:56 UTC

   We are continuing to investigate this issue.

3. investigating 2026-04-03 22:07 UTC

   We have identified the issue and a fix has been deployed, services are being restored. Analytics event collection is not been impacted and no data loss is expected.

4. monitoring 2026-04-03 22:14 UTC

   We're continuing to monitor as services recover.

5. monitoring 2026-04-03 22:23 UTC

   Our data pipeline are catching up with no expected data loss, incident is expected to be fully resolved shortly.

6. monitoring 2026-04-03 23:33 UTC

   All systems are operational.

7. resolved 2026-04-03 23:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Amplitude's status page.

Affected: Web Application

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-27 15:52 UTC

   For some flags, the exposures chart is not loading properly. For some experiments, the analysis page is not loading properly saying "This experiment's user property is not available yet. It will appear after users are assigned." and "Invalid user property gp:". We are working on...

2. identified 2026-03-27 16:42 UTC

   We have identified a fix. We are rolling the fix out.

3. resolved 2026-03-27 17:11 UTC

   We have fixed the issue

Excerpts are shortened. Read the full incident on Amplitude's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-03-27 03:00 UTC

   Some Flags and experiments that were targeting cohorts did not evaluate users into control and treatment correctly. This has been fixed

Excerpts are shortened. Read the full incident on Amplitude's status page.

Affected: Flag Configurations API

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-25 18:00 UTC

   Components Affected: Experiments Message: Since 2026-03-25 10:09 AM PT (17:09 UTC), users have been unable to create new experiments in Amplitude Experiment. Existing experiments and other Experiment functionality are not affected. Our team has identified the source of the issue...

2. resolved 2026-03-25 18:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Amplitude's status page.