May <var data-var='date'>22</var>, <var data-var='time'>19:14</var> PDT Completed - The configuration update has been completed successfully, and verification has been finalized. All systems and services are operating normally. Thank you everyone for your coordination and support throughout the maintenance window. May <var data-var='date'>22</var>, <var data-var='time'>18:56</var> PDT Verifying - The planned maintenance has been completed successfully. We are currently in the verification stage and actively validating all services and functionalities to ensure everything is operating as expected. May <var data-var='date'>22</var>, <var data-var='time'>17:00</var> PDT In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. May <var data-var='date'>21</var>, <var data-var='time'>16:58</var> PDT Scheduled - We will be applying underlying configuration changes that require a long maintenance window. Some page loads may fail or slow during this window. Expected Impacted Areas: * All Areas of Web Application * MCP Not Impacted: * Ingestion Pipeline

Planned Configuration Maintenance

May <var data-var='date'>21</var>, <var data-var='time'>23:32</var> PDT Resolved - 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. May <var data-var='date'>21</var>, <var data-var='time'>23:06</var> PDT Monitoring - 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. May <var data-var='date'>21</var>, <var data-var='time'>19:51</var> PDT Investigating - We are currently investigating elevated application latency affecting portions of the platform. Users may experience slower page loads, delayed query responses, or intermittent timeouts.

Application Performance Degradation

May <var data-var='date'>19</var>, <var data-var='time'>06:02</var> PDT Resolved - This incident has been resolved. May <var data-var='date'>19</var>, <var data-var='time'>05:58</var> PDT Monitoring - A fix has been implemented and we are monitoring the results. May <var data-var='date'>19</var>, <var data-var='time'>05:45</var> PDT Investigating - We are actively investigating a lag in processing data in EU. All data is received and no data is lost.

Ingestion lag in EU

May <var data-var='date'>14</var>, <var data-var='time'>19:03</var> PDT Resolved - This incident has been resolved. May <var data-var='date'>14</var>, <var data-var='time'>15:47</var> PDT Monitoring - A fix has been implemented and we are monitoring the results. May <var data-var='date'>14</var>, <var data-var='time'>15:47</var> PDT Update - We are continuing to investigate this issue. May <var data-var='date'>14</var>, <var data-var='time'>14:42</var> PDT Investigating - We are noticing slower than normal processing in our ingestion pipelines

Slower realtime processing

May <var data-var='date'> 5</var>, <var data-var='time'>12:44</var> PDT Resolved - This incident has been resolved. May <var data-var='date'> 5</var>, <var data-var='time'>12:27</var> PDT Monitoring - A fix has been implemented and we are monitoring the results. May <var data-var='date'> 5</var>, <var data-var='time'>12:13</var> PDT Investigating - 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.

Ingestion lag in our batch pipeline

Apr <var data-var='date'>29</var>, <var data-var='time'>07:33</var> PDT Resolved - This incident has been resolved. Apr <var data-var='date'>29</var>, <var data-var='time'>02:54</var> PDT Update - The issue has been resolved. Apr <var data-var='date'>29</var>, <var data-var='time'>02:10</var> PDT Update - We are continuing to monitor for any further issues. Apr <var data-var='date'>29</var>, <var data-var='time'>01:59</var> PDT Update - We are continuing to monitor for any further issues. Apr <var data-var='date'>29</var>, <var data-var='time'>01:39</var> PDT Monitoring - 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. Apr <var data-var='date'>29</var>, <var data-var='time'>01:30</var> PDT Update - 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. Apr <var data-var='date'>29</var>, <var data-var='time'>01:20</var> PDT Identified - 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 metrics for the last 1 hour. c) Experiment evaluation API is experiencing higher latencies. d) Cohort syncs to all 3rd party destinations is experiencing higher latencies. We've identified the issue and are working closely with our cloud provider to mitigate it. We will provide an update within the next hour, or sooner if new information becomes available. Apr <var data-var='date'>29</var>, <var data-var='time'>01:15</var> PDT Investigating - 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 metrics for the last 1 hour. c) Experiment evaluation API is experiencing higher latencies. d) Cohort syncs to all 3rd party destinations is experiencing higher latencies. We've identified the issue and are working closely with our cloud provider to mitigate it. We will provide an update within the next hour, or sooner if new information becomes available.

Data Processing Delays

Apr <var data-var='date'>28</var>, <var data-var='time'>10:00</var> PDT Resolved - 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.

Amplitude web application not loading

Apr <var data-var='date'>23</var>, <var data-var='time'>13:32</var> PDT Resolved - This incident has been resolved. Apr <var data-var='date'>23</var>, <var data-var='time'>13:02</var> PDT Monitoring - 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. Apr <var data-var='date'>23</var>, <var data-var='time'>12:56</var> PDT Investigating - 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 experience errors when loading Amplitude web pages.

Apr <var data-var='date'>15</var>, <var data-var='time'>18:11</var> PDT Resolved - This incident has been resolved. Apr <var data-var='date'>15</var>, <var data-var='time'>17:21</var> PDT Update - 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. Apr <var data-var='date'>15</var>, <var data-var='time'>17:20</var> PDT Update - 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. Apr <var data-var='date'>15</var>, <var data-var='time'>16:09</var> PDT Monitoring - 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 delayed event data in 3rd party Event Streaming destinations for the last 3 hrs. Our team has identified the issue and is actively working on a resolution. There is no data loss, and data will still be sent to downstream destinations. No customer action is needed at this time. We will provide the next update in an hour.

Event Streaming Delay

Apr <var data-var='date'>13</var>, <var data-var='time'>14:00</var> PDT Resolved - This incident has been resolved. Apr <var data-var='date'>13</var>, <var data-var='time'>13:53</var> PDT Monitoring - 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 occurs at end of day. Apr <var data-var='date'>13</var>, <var data-var='time'>08:45</var> PDT Identified - 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 new event properties and (b) use those new event properties for filtering, creating cohorts. The issue has been identified, and the team is working on a fix that will remove all of these event properties. You may see some irregularities during this time. Once the mistakenly-added event properties are deleted, some post-processing will occur at the end of the day to restore any new event properties which could not be added to event property overages (new ones, added after 8:45 am PDT, assuming the project was put over the 2000 event property limit due to this change).

Event properties showing as over quota for orgs using Guides and Surveys

Apr <var data-var='date'>12</var>, <var data-var='time'>03:52</var> PDT Resolved - This incident has been resolved. Apr <var data-var='date'>12</var>, <var data-var='time'>03:47</var> PDT Monitoring - A fix has been implemented and we are monitoring the results. Apr <var data-var='date'>12</var>, <var data-var='time'>02:52</var> PDT Update - We are continuing to investigate this issue Apr <var data-var='date'>12</var>, <var data-var='time'>01:24</var> PDT Investigating - 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 investigating the source of the issue and working to restore normal operations. Auto-scaling measures have been initiated. We do not expect permanent data loss for events that are retried by client SDKs. No customer action is needed at this time beyond ensuring your SDKs are configured with retry logic. We will provide the next update by 2026-04-12 02:00 PT (09:00 UTC).

EU data collection endpoint api.eu.amplitude.com is DOWN

Apr <var data-var='date'> 6</var>, <var data-var='time'>17:48</var> PDT Resolved - This incident has been resolved. Apr <var data-var='date'> 6</var>, <var data-var='time'>16:39</var> PDT Monitoring - 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 Apr <var data-var='date'> 6</var>, <var data-var='time'>12:53</var> PDT Investigating - We are currently investigating an issue affecting user authentication for: Ampli CLI, MCP Server, Notion/Atlassian chart previews.

Users Unable to Sign In with External Tools

Apr <var data-var='date'> 3</var>, <var data-var='time'>16:52</var> PDT Resolved - This incident has been resolved. Apr <var data-var='date'> 3</var>, <var data-var='time'>16:33</var> PDT Update - All systems are operational. Apr <var data-var='date'> 3</var>, <var data-var='time'>15:23</var> PDT Update - Our data pipeline are catching up with no expected data loss, incident is expected to be fully resolved shortly. Apr <var data-var='date'> 3</var>, <var data-var='time'>15:14</var> PDT Monitoring - We're continuing to monitor as services recover. Apr <var data-var='date'> 3</var>, <var data-var='time'>15:07</var> PDT Update - 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. Apr <var data-var='date'> 3</var>, <var data-var='time'>14:56</var> PDT Update - We are continuing to investigate this issue. Apr <var data-var='date'> 3</var>, <var data-var='time'>14:52</var> PDT Investigating - We are currently investigating a site-wide outage.

Amplitude Website Outage

Mar <var data-var='date'>27</var>, <var data-var='time'>18:30</var> PDT Completed - The scheduled maintenance has been completed. Mar <var data-var='date'>27</var>, <var data-var='time'>18:07</var> PDT Verifying - Configuration update has been complete; currently verifying. Mar <var data-var='date'>27</var>, <var data-var='time'>17:00</var> PDT In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Mar <var data-var='date'>26</var>, <var data-var='time'>13:00</var> PDT Scheduled - We will be applying underlying configuration changes that require a short maintenance window. Some page loads may fail for a short time during this window.

Mar <var data-var='date'>27</var>, <var data-var='time'>10:11</var> PDT Resolved - We have fixed the issue Mar <var data-var='date'>27</var>, <var data-var='time'>09:42</var> PDT Identified - We have identified a fix. We are rolling the fix out. Mar <var data-var='date'>27</var>, <var data-var='time'>08:52</var> PDT Investigating - 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 a fix.

Amplitude Experiment Issue with Charts Loading

Mar <var data-var='date'>26</var>, <var data-var='time'>20:00</var> PDT Resolved - Some Flags and experiments that were targeting cohorts did not evaluate users into control and treatment correctly. This has been fixed

Amplitude Experiment Evaluation

Mar <var data-var='date'>25</var>, <var data-var='time'>11:09</var> PDT Resolved - This incident has been resolved. Mar <var data-var='date'>25</var>, <var data-var='time'>11:00</var> PDT Investigating - 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 and is actively working to deploy a fix. We expect no data loss. No customer action is needed at this time. We will provide the next update by 12:00 PM PT (19:00 UTC).

Experiment Creation Unavailable

Mar <var data-var='date'>20</var>, <var data-var='time'>13:00</var> PDT Resolved - This incident has been resolved. Mar <var data-var='date'>20</var>, <var data-var='time'>12:13</var> PDT Monitoring - We have verified the fix, and the management-api is now fully operational. We will remain in a period of active monitoring to ensure continued stability. Mar <var data-var='date'>20</var>, <var data-var='time'>10:31</var> PDT Identified - Since 2026-03-20 approximately 09:00 AM PT (16:00 UTC), the Experiment Flags Management API (/api/1/flags) has been returning incomplete results. Customers using the Flags Management API may see empty responses when listing feature flags, even though flags remain visible and functional in the Amplitude UI. The Experiments API (/api/1/experiments) is not affected. Our team has identified the root cause and a fix has been deployed. We are monitoring the rollout to confirm the issue is fully resolved. No data has been lost, and flags continue to evaluate correctly for end users. No customer action is needed at this time. We will provide the next update by 2026-03-20 12:00 PM PT (19:00 UTC).

Experiment Management API Degradation

Mar <var data-var='date'>16</var>, <var data-var='time'>13:55</var> PDT Resolved - Duration: March 16, 2026, 11:20 AM PT to 1:17 PM PT Between 11:20 AM PT and 1:17 PM PT, the Experiment Evaluation Service experienced a partial outage, resulting in elevated 500, 502, and 503 errors for some requests. Our team has successfully resolved the issue, and the service is now operating normally. We apologize for any inconvenience this disruption may have caused.

Experiment Evaluation Service Outage

Mar <var data-var='date'>16</var>, <var data-var='time'>09:00</var> PDT Resolved - Between 2026-03-16 08:57 AM PT (15:57 UTC) and 09:23 AM PT (16:23 UTC), some Amplitude users experienced intermittent 500 errors when loading charts, dashboards, and reports in Analytics and Experiment. A second brief interruption occurred at approximately 09:49 AM PT (16:49 UTC), during which some requests again returned 500 errors. The issue was caused by a temporary database disruption that has since automatically recovered. Our team has confirmed that services are operating normally. No data loss occurred, and no customer action is needed. We are actively investigating the root cause to prevent recurrence and will continue to monitor the system.

Intermittent Errors in Analytics and Experiment

Mar <var data-var='date'>10</var>, <var data-var='time'>09:00</var> PDT Resolved - A migration to transition some Growth orgs to a new permission system, which is activated by a feature flag, did not operate correctly, resulting in the appearance of lost role assignments for users. This affected some Growth orgs that have project-based permissions. Removing the feature flag for these orgs reverted them to the old permission system, restoring all role assignments correctly.

Missing Role Assignments for Growth Orgs

Mar <var data-var='date'> 2</var>, <var data-var='time'>20:46</var> PST Resolved - This incident has been resolved. Mar <var data-var='date'> 2</var>, <var data-var='time'>20:22</var> PST Monitoring - A fix has been implemented and we are monitoring the results. Mar <var data-var='date'> 2</var>, <var data-var='time'>18:53</var> PST Investigating - We've identified an issue with search queries failing within the Resource Center due to an issue with an upstream provider. We are working with them to identify the root cause.

Resource Center search is degraded

Feb <var data-var='date'>27</var>, <var data-var='time'>19:00</var> PST Completed - The scheduled maintenance has been completed. Feb <var data-var='date'>27</var>, <var data-var='time'>18:44</var> PST Verifying - The configuration change has been completed. Verifying affected services. Feb <var data-var='date'>27</var>, <var data-var='time'>17:00</var> PST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Feb <var data-var='date'>26</var>, <var data-var='time'>16:45</var> PST Scheduled - We will be applying underlying configuration changes that require a short maintenance window. Some page loads may fail for a short time during this window.

Feb <var data-var='date'>27</var>, <var data-var='time'>15:47</var> PST Resolved - As of 3:10 PM PT, we have fully recovered and all systems are operating normally. Feb <var data-var='date'>27</var>, <var data-var='time'>14:22</var> PST Identified - Since 2026-02-27 1:14 PT, some Amplitude users may have experienced issues while loading charts/dashboards. Our team is actively investigating the source of the issue and working to deploy a fix. New data ingested recently might be delayed and not show up in results by up to 30 mins. We expect no data loss. No customer action is needed at this time. We will provide the next update by 2026-02-27 3:00 PM PT.

Query errors

Feb <var data-var='date'>26</var>, <var data-var='time'>14:58</var> PST Resolved - This incident has been resolved. Feb <var data-var='date'>26</var>, <var data-var='time'>12:56</var> PST Monitoring - The rollback has been applied and we are monitoring recovery. Feb <var data-var='date'>26</var>, <var data-var='time'>12:55</var> PST Identified - We've identified the root cause and rollback has been triggered. Feb <var data-var='date'>26</var>, <var data-var='time'>12:48</var> PST Update - We are continuing to investigate this issue. Feb <var data-var='date'>26</var>, <var data-var='time'>12:48</var> PST Investigating - Since 2026-02-26 12:00 PT (20:00 UTC), some Amplitude users may experience a "Something went wrong" error page when loading the Amplitude application. Users with certain permission configurations may be unable to access the platform. Our team is actively investigating the source of the issue and working to deploy a fix. We expect no data loss. No customer action is needed at this time. We will provide the next update by 2026-02-26 1:30 PM PT (21:30 UTC).

Is Amplitude down?

Amplitude status is UP

Lastest published events

Planned Configuration Maintenance

Application Performance Degradation

Ingestion lag in EU

Amplitude Services, Components and Regions

Recent Amplitude events

Planned Configuration Maintenance

Application Performance Degradation

Ingestion lag in EU

Slower realtime processing

Ingestion lag in our batch pipeline

Data Processing Delays

Get your FREE account now,
5 monitors included!

Is Amplitude down?

Amplitude status is UP

Lastest published events

Planned Configuration Maintenance

Application Performance Degradation

Ingestion lag in EU

Amplitude Services, Components and Regions

Recent Amplitude events

Planned Configuration Maintenance

Application Performance Degradation

Ingestion lag in EU

Slower realtime processing

Ingestion lag in our batch pipeline

Data Processing Delays

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!