Feb 24, 02:08 EST
Resolved - This incident has been resolved.

Feb 24, 00:52 EST
Monitoring - We have deployed a fix and we are monitoring the results.
We will provide another update once the issue is fully resolved.

Feb 24, 00:29 EST
Identified - We have identified the underlying issue and are working on a fix.
It is important to note that no data has been lost, and it will be backfilled and available once the service is operational again.

Feb 23, 23:31 EST
Investigating - We are investigating increased latency processing RUM data.
As a result of this issue, some users may see gaps or delays in RUM graphs as well as empty or partial query results on RUM Sessions, RUM Analytics, RUM Application, and Error Tracking pages.

Feb 18, 15:37 EST
Resolved - This incident has been resolved.

Feb 18, 14:30 EST
Monitoring - We are investigating delays in a subset of Distribution Metrics and Monitor Evaluations, which began at 18:33 UTC.

Feb 11, 21:08 EST
Resolved - This incident has been resolved.

Feb 11, 20:49 EST
Update - The remaining impact is limited to AWS Streams metrics. We are continuing to monitor for any further issues.

Feb 11, 20:32 EST
Monitoring - A fix has been implemented and we are monitoring the results.

Feb 11, 20:20 EST
Identified - The issue has been identified and a fix is being implemented.

Feb 11, 19:57 EST
Investigating - We are investigating increased latency processing Traces in APM Trace Search and AWS streams metrics.
As a result of this issue, some users may see missing or delayed traces in APM Trace Search, and delayed AWS stream metrics since 00:13 UTC.

Feb 11, 18:44 EST
Resolved - This incident has been resolved.

Feb 11, 18:28 EST
Monitoring - A fix has been implemented and we are monitoring the results.

Feb 11, 17:28 EST
Update - Teams continue to work to mitigate the impact of this issue. At this time, APM Trace Processing, APM Trace Monitors are still delayed. Distribution Metrics monitors were delayed between 21:35 and 22:15 UTC

Feb 11, 16:51 EST
Update - Teams continue to work to mitigate the impact of this issue. At this time, APM Trace Processing, APM Trace Monitors are still delayed and Distribution Metrics monitors are delayed starting from 21:35 UTC

Feb 11, 16:18 EST
Identified - Teams have identified the issue and are working to mitigate at this time

Feb 11, 15:56 EST
Investigating - We are investigating increased latency processing Traces in APM Trace Search.
As a result of this issue, some users may see missing or delayed traces in APM Trace Search and delayed APM Trace Monitors since 21:30 UTC.

Feb 5, 12:43 EST
Resolved - This incident has been resolved.

Feb 5, 12:23 EST
Monitoring - We have observed full recovery of monitors and will continue to monitor

Feb 5, 12:01 EST
Update - We are observing recovery for the vast majority of monitors and are continuing to work on a full fix for this issue.

Feb 5, 11:50 EST
Update - We are continuing to work on a fix for this issue.

Feb 5, 11:31 EST
Identified - The issue has been identified and a fix is being implemented.

Feb 5, 11:28 EST
Update - We are continuing to investigate this issue.

Feb 5, 11:11 EST
Update - We are continuing to investigate this issue.

Feb 5, 11:10 EST
Update - We are continuing to investigate this issue.

Feb 5, 11:04 EST
Update - We are continuing to investigate this issue.

Feb 5, 10:24 EST
Investigating - We are currently investigating this issue.

Jan 29, 14:55 EST
Resolved - This incident has been resolved.

Jan 29, 14:09 EST
Update - We are continuing to monitor the fix and will continue to provide regular updates.

Jan 29, 13:36 EST
Monitoring - We have deployed a fix and we are monitoring the results. We will continue to provide regular updates.

Jan 29, 13:06 EST
Update - We are continuing to work on a fix for this issue. It is important to note that no data has been lost, and evaluations will be caught up once the service is operational again.

Jan 29, 12:46 EST
Identified - We have identified the underlying issue and are working on a fix. It is important to note that no data has been lost, and evaluations will be caught up once the service is operational again.

Jan 29, 12:35 EST
Investigating - We are investigating delays in Monitors evaluations, which began at 17:15 UTC.

Jan 28, 18:36 EST
Resolved - This incident has been resolved.

Jan 28, 18:13 EST
Monitoring - A fix has been implemented and we are monitoring the results.

Jan 28, 17:08 EST
Identified - The issue has been identified and a fix is being implemented.

Jan 28, 16:21 EST
Update - We are continuing to investigate this issue.

Jan 28, 15:30 EST
Investigating - We are investigating delays in service checks monitors evaluation, which began at 20:26 1/28/2026 UTC.

Jan 22, 14:27 EST
Resolved - This incident has been resolved.

Jan 22, 14:13 EST
Monitoring - A fix has been implemented and we are monitoring the results.

Jan 22, 14:01 EST
Update - We are continuing to investigate this issue.

Jan 22, 13:51 EST
Investigating - We are investigating loading issues on our web application. As a result, some users might be getting errors when loading the web application.

Please note that data processing and alerts are not affected by this incident.

Jan 18, 09:24 EST
Resolved - This incident is resolved. There's no more delay for the processing of Events, nor impact on the event stream, event based widgets and event based monitors.

Jan 18, 08:26 EST
Update - Recovery is in progress and the new estimated time of recovery would be 14h30 UTC.

Jan 18, 07:35 EST
Update - We have identified the issue and scaled up for recovery, with a recovery estimated to be around 14h30 UTC. We'll continue to give updates as recovery progresses.

Jan 18, 07:33 EST
Identified - We are investigating increased latency processing Events.
As a result of this issue, some users may see delays or gaps in the event stream or for event based widgets or event based monitors.

Dec 12, 18:43 EST
Resolved - This incident has been resolved.

Dec 12, 18:31 EST
Monitoring - A fix has been implemented and we are monitoring the results.

Dec 12, 17:41 EST
Identified - The issue has been identified and a fix is being implemented.

Dec 12, 16:53 EST
Update - We are continuing to investigate this issue.

Dec 12, 16:49 EST
Investigating - We are investigating increased latency processing Processes data.
As a result of this issue, some users may see delays or gaps for data based on Process Monitoring.
To prevent spurious alerts, we have temporarily disabled monitors based on this data.