SolarWinds Observability Outage History

SolarWinds Observability is up right now

Pingoru has recorded 50 incidents for SolarWinds Observability: 32 in the last 12 months and 2 in the last 90 days.

Source: status.cloud.solarwinds.com

50incidents recorded
32last 12 months
2last 90 days
6 hourstypical duration
Incidents per month
036AprMayJunJulAugSepOct1
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct1%
Pingoru began tracking SolarWinds Observability in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202623 of 720 (0%)
May 202600 of 744 (0%)
June 202667 of 720 (1%)
July 202622 of 744 (0%)
August 2026111 of 744 (1%)
September 202600 of 720 (0%)
October 202614 of 508 (1%)

Incidents, newest first

Minor October 6, 2026 Degraded Data Ingestion [NA-01, EU-01] 4h 17m Alerting, Logs

Started Oct 06, 2026, 12:06 PM UTC· resolved Oct 06, 2026, 04:24 PM UTC

  1. investigating Oct 06, 2026, 12:06 PM UTC

    We are currently investigating an issue affecting log ingestion for a subset of customers. Customers using former Papertrail log ingestion endpoints may experience delayed processing or failed ingestion of new log data. Services not utilizing the affected ingestion path remain operational. We will provide an update within the hour.

  2. investigating Oct 06, 2026, 01:11 PM UTC

    We continue to investigate an issue affecting log ingestion for a subset of customers. Customers using former Papertrail log-ingestion endpoints may experience delayed processing or failed ingestion of new log data. Services not using the affected ingestion path remain operational. We will provide an update within the hour.

  3. identified Oct 06, 2026, 01:43 PM UTC

    We’ve identified the root cause of the degraded Logs data ingestion and are working on a fix. Customers using former Papertrail log ingestion endpoints may experience delayed processing or failed ingestion of new log data. Services not utilizing the affected ingestion path remain operational. Affected customers may see gaps in the telemetry data and experience missing alerts. We will provide an update within the hour.

  4. identified Oct 06, 2026, 02:42 PM UTC

    We’ve identified the root cause of the degraded Logs data ingestion and are still working on a fix. Customers using former Papertrail log ingestion endpoints may experience delayed processing or failed ingestion of new log data. Services not utilizing the affected ingestion path remain operational. Affected customers may see gaps in the telemetry data and experience missing alerts. We will provide an update within the hour.

  5. identified Oct 06, 2026, 03:38 PM UTC

    We’ve identified the root cause of the degraded Logs data ingestion and are still working on a fix. Customers using former Papertrail log ingestion endpoints may experience delayed processing or failed ingestion of new log data. Services not utilizing the affected ingestion path remain operational. Affected customers may see gaps in the telemetry data and experience missing alerts. We will provide an update within the hour.

  6. monitoring Oct 06, 2026, 04:03 PM UTC

    A fix has been implemented for the Logs data ingestion issue and the backlog is being processed. Customers using former Papertrail log ingestion endpoints may continue to experience delayed processing of new log data. Services not utilizing the affected ingestion path remain operational. Affected customers may see gaps in the telemetry data and experience missing alerts. We will provide an update within the hour.

  7. resolved Oct 06, 2026, 04:24 PM UTC

    The data ingestion issue has been resolved and data has been completely processed. Systems are now stable and operating as normal.

Read the full incident report →

Minor August 20, 2026 Delayed Data Ingestion [EU-01] 10h 28m Alerting, APM, DEM, RUM and 6 more

Started Aug 20, 2026, 02:13 PM UTC· resolved Aug 21, 2026, 12:41 AM UTC

  1. investigating Aug 20, 2026, 02:13 PM UTC

    We’ve identified the cause of the delay in Logs, Metrics & Traces data ingestion and are working on a fix. New data may not appear in the UI, alerts could be delayed, and some dashboards might show missing or outdated values. We’ll provide an update within the hour.

  2. identified Aug 20, 2026, 02:49 PM UTC

    We’ve identified the cause of the delay in Logs, Metrics and Traces data ingestion and are working on a fix. New data may not appear in the UI, alerts could be delayed, and some dashboards might show missing or outdated values. We’ll provide an update within the hour.

  3. identified Aug 20, 2026, 03:51 PM UTC

    The ingestion delay has fully recovered, and the latest data should now be visible in the UI. Alerting has also returned to real-time processing. There will be data gaps in the UI between 9:40 UTC and 14:40 UTC while we complete the backfill. We are actively replaying the missing data, and the backfill is expected to take approximately 24–48 hours to complete. Next update within 8 hours.

  4. identified Aug 20, 2026, 11:40 PM UTC

    The backfill is making progess, however, some customers may still see data gaps in the UI between 9:40 UTC and 14:40 UTC while it completes. We are still actively replaying the missing data, and the backfill is expected to take approximately an hour to complete. Next update within 1 hour.

  5. resolved Aug 21, 2026, 12:41 AM UTC

    The backfill is now complete. All data has been restored. New data is now processing normally, and alerts and dashboards should reflect up-to-date information.

Read the full incident report →

Minor July 23, 2026 Degraded Alert Notifications [NA-01, NA-02, EU-01, AP-01] 25m Alerting, Logs

Started Jul 23, 2026, 08:16 AM UTC· resolved Jul 23, 2026, 08:42 AM UTC

  1. investigating Jul 23, 2026, 08:16 AM UTC

    We’re currently investigating an issue with alert notifications. Alerts may have been missed and notifications are degraded for some customers. We’ll provide another update within the hour.

  2. identified Jul 23, 2026, 08:32 AM UTC

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

  3. monitoring Jul 23, 2026, 08:35 AM UTC

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

  4. resolved Jul 23, 2026, 08:42 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 29, 2026 Degraded Web Interface NA-01 1h 2m Network Observability

Started Jun 29, 2026, 11:11 AM UTC· resolved Jun 29, 2026, 12:13 PM UTC

  1. investigating Jun 29, 2026, 11:11 AM UTC

    We’re currently investigating degraded performance in the web interface. Some customers may experience intermittent UI errors, or missing monitoring data on the home page. We’ll provide another update within the hour.

  2. identified Jun 29, 2026, 11:41 AM UTC

    We’ve identified the cause of the web interface degradation and are working on a fix. Intermittent UI errors, and missing monitoring data may still affect some customers. Next update in 1 hour.

  3. monitoring Jun 29, 2026, 12:03 PM UTC

    A fix has been implemented for the web interface issues, and we’re actively monitoring to ensure full recovery. Some customers may still experience intermittent UI or dashboard issues as systems stabilize. We’ll provide an update within the hour.

  4. resolved Jun 29, 2026, 12:13 PM UTC

    The web interface issues have been resolved and services have returned to normal operations.

Read the full incident report →

Major June 27, 2026 Degraded data ingestion: [logs3.papertrailapp.com] 45m Logs

Started Jun 27, 2026, 12:18 AM UTC· resolved Jun 27, 2026, 01:03 AM UTC

  1. investigating Jun 27, 2026, 12:32 AM UTC

    We are currently investigating this issue.

  2. monitoring Jun 27, 2026, 12:52 AM UTC

    A fix has been implemented for the Logs data ingestion issue. We’re actively monitoring system stability and verifying end-to-end delivery across impacted systems. We’ll provide an update within the hour.

  3. resolved Jun 27, 2026, 01:03 AM UTC

    The data ingestion issue has been resolved and systems are stable.

Read the full incident report →

Minor June 16, 2026 Delayed Data Ingestion [ AP-01 ] 3h 10m Alerting, APM

Started Jun 16, 2026, 07:52 AM UTC· resolved Jun 16, 2026, 11:03 AM UTC

  1. investigating Jun 16, 2026, 07:52 AM UTC

    We are currently investigating an issue with Metrics data ingestion. As a result of this issue, submitting new data through the API might fail temporarily. We’ll provide an update within the hour.

  2. investigating Jun 16, 2026, 09:20 AM UTC

    We are still investigating this issue.

  3. monitoring Jun 16, 2026, 10:30 AM UTC

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

  4. resolved Jun 16, 2026, 11:03 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 12, 2026 Temporarily unavailable web UI in NA-02 –

Started Jun 12, 2026, 12:00 AM UTC· resolved Jun 12, 2026, 12:00 AM UTC

  1. resolved Jun 12, 2026, 12:42 AM UTC

    There was a short window when the web UI was unavailable. Based on reports from external tests this was due to Azure stability issues and unrelated to SolarWinds services.

Read the full incident report →

Minor June 6, 2026 Delayed Data Ingestion [NA-01] 1h 13m Logs

Started Jun 06, 2026, 01:51 AM UTC· resolved Jun 06, 2026, 03:04 AM UTC

  1. identified Jun 06, 2026, 01:51 AM UTC

    We’ve identified the cause of the delay in Logs data ingestion and are working on a fix. New data may not appear in the UI, alerts could be delayed, and some dashboards might show missing or outdated values. We’ll provide an update within the hour.

  2. monitoring Jun 06, 2026, 02:31 AM UTC

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

  3. resolved Jun 06, 2026, 03:04 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 4, 2026 Delayed Alert Notifications [NA-01] 36m Alerting

Started Jun 04, 2026, 01:25 PM UTC· resolved Jun 04, 2026, 02:01 PM UTC

  1. identified Jun 04, 2026, 01:25 PM UTC

    Starting at 12:33 UTC we noticed higher than normal latency with alerts, resulting in alert delivery being delayed. We've identified the issue causing delays in alert delivery and are working on a fix. Some alerts may still be delayed in the meantime. Next update in 1 hour.

  2. monitoring Jun 04, 2026, 01:33 PM UTC

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

  3. resolved Jun 04, 2026, 02:01 PM UTC

    The issue impacting alert notifications has been resolved. Alerts are now being sent as expected. Some customers may have delayed delivery of any alerts that would have been triggered during the incident window.

Read the full incident report →

Notice April 28, 2026 Degraded Web Interface [NA-01] 1h 11m

Started Apr 28, 2026, 12:30 PM UTC· resolved Apr 28, 2026, 01:41 PM UTC

  1. resolved Apr 28, 2026, 02:12 PM UTC

    Between 12:30 PM UTC and 01:41 PM UTC widgets were intermittently broken for all customers on the NA-01 data cell. The web interface issues have been resolved and services have returned to normal operations.

Read the full incident report →

Critical April 28, 2026 Degraded Alert Notifications [NA-01, NA-02, EU-01, AP-01] 1h 48m Alerting

Started Apr 28, 2026, 07:22 AM UTC· resolved Apr 28, 2026, 09:11 AM UTC

  1. investigating Apr 28, 2026, 07:22 AM UTC

    We’ve identified the cause of the email alert notification issue and are actively working on a fix. Some alerts may have been missed, and email notifications remain degraded. We’ll provide our next update in 1 hour.

  2. investigating Apr 28, 2026, 07:23 AM UTC

    We are continuing to investigate this issue.

  3. identified Apr 28, 2026, 07:37 AM UTC

    Alerts may have been missed, and email notifications remain degraded. We’ll provide our next update in 1 hour.

  4. monitoring Apr 28, 2026, 08:43 AM UTC

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

  5. resolved Apr 28, 2026, 09:11 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 23, 2026 Degraded Web Interface [EU-01] 26m

Started Mar 23, 2026, 10:14 AM UTC· resolved Mar 23, 2026, 10:41 AM UTC

  1. investigating Mar 23, 2026, 10:14 AM UTC

    We’re currently investigating a degradation in the web interface. Some customers may experience intermittent UI errors, or non-loading monitoring data on the home page. We’ll provide another update within the hour.

  2. monitoring Mar 23, 2026, 10:31 AM UTC

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

  3. resolved Mar 23, 2026, 10:41 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 13, 2026 Degraded Data Ingestion [NA-01] 1h 50m Alerting, APM, Logs, Database Observability and 3 more

Started Mar 13, 2026, 09:04 PM UTC· resolved Mar 13, 2026, 10:54 PM UTC

  1. identified Mar 13, 2026, 09:04 PM UTC

    We’ve identified the root cause of the degraded Logs, Metrics, and Traces data ingestion and are working on a fix. Affected customers may see gaps in the telemetry data and experience missing alerts. Next update in 1 hour.

  2. identified Mar 13, 2026, 10:02 PM UTC

    We’ve identified the root cause of the degraded Logs, Metrics, and Traces data ingestion and are working on a fix. Affected customers may see gaps in the telemetry data and experience missing alerts. Next update in 1 hour.

  3. resolved Mar 13, 2026, 10:54 PM UTC

    The data ingestion issue has been resolved and systems are stable. Customers using Node.js APM instrumentation libraries may need to restart these applications to see metrics and trace data.

Read the full incident report →

Minor March 9, 2026 Degraded Digital Experience Monitoring [Washington DC AWS] 20m DEM

Started Mar 09, 2026, 07:43 PM UTC· resolved Mar 09, 2026, 08:04 PM UTC

  1. identified Mar 09, 2026, 07:43 PM UTC

    We’ve identified the issue causing degraded Digital Experience Monitoring and are implementing a fix. Customers may experience degradation of synthetic checks & alerts from the affected regions. We’ll provide another update in 1 hour.

  2. monitoring Mar 09, 2026, 07:52 PM UTC

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

  3. resolved Mar 09, 2026, 08:04 PM UTC

    The Digital Experience Monitoring issue has been resolved. Affected probes are now stable and running synthetic checks as expected. Missed synthetic checks during the affected window will not be re-run and may show as missing in the dashboards.

Read the full incident report →

Critical March 3, 2026 Degraded Data Ingestion NA-01 3h 57m Alerting, APM, DEM, RUM and 2 more

Started Mar 03, 2026, 12:38 AM UTC· resolved Mar 03, 2026, 04:35 AM UTC

  1. investigating Mar 03, 2026, 12:38 AM UTC

    We’re currently investigating delay in Logs Metrics and Traces data ingestion. As a result, New data may not appear in the UI, alerts may be delayed, and some dashboards could show missing or outdated values. We’ll provide another update within the hour.

  2. identified Mar 03, 2026, 01:02 AM UTC

    We’ve identified the root cause of the degraded Logs, Metrics and Traces data ingestion and are working on a fix. Affected customers may see gaps in the telemetry data and experience missing alerts. Next update in 1 hour.

  3. identified Mar 03, 2026, 01:55 AM UTC

    We’ve identified the root cause of the degraded Logs, Metrics and Traces data ingestion and are working on a fix. Affected customers may see gaps in the telemetry data and experience missing alerts. Next update in 1 hour.

  4. identified Mar 03, 2026, 02:52 AM UTC

    We’ve identified the root cause of the degraded Heroku metrics data ingestion and are working on a fix. Affected customers may see gaps in the telemetry data and experience missing alerts. All other services for Logs, Metrics and Traces are operating normally. Next update in 1 hour.

  5. resolved Mar 03, 2026, 04:35 AM UTC

    The data ingestion issue has been resolved and systems are stable.

Read the full incident report →

Critical March 2, 2026 Degraded Digital Experience Monitoring [Middle East] 3d 15h Alerting, DEM

Started Mar 02, 2026, 08:22 AM UTC· resolved Mar 06, 2026, 12:00 AM UTC

  1. investigating Mar 02, 2026, 08:22 AM UTC

    We’re currently investigating an issue affecting Digital Experience Monitoring. Customers may experience degradation of synthetic checks & alerts from the affected regions. We’ll share another update within the hour.

  2. investigating Mar 02, 2026, 09:07 AM UTC

    Due to the on going conflict in the Middle East, our probes in this region are currently unavailable. Customers may experience degradation of synthetic checks & alerts from the affected regions. To mitigate any impact to tests, customer should pick an alternate region to execute tests from. We'll share another update within in the next 4 hours or sooner.

  3. identified Mar 02, 2026, 01:03 PM UTC

    We are continuously monitoring the situation, however our probes in this region remain unavailable at this time. To mitigate any impact to tests, customer should pick an alternate region to execute tests from. We'll share another update within in the next 4 hours or sooner.

  4. identified Mar 02, 2026, 04:59 PM UTC

    We are continuously monitoring the situation, however our probes in this region remain unavailable at this time. To mitigate any impact to tests, customer should pick an alternate region to execute tests from. We'll share another update within in the next 12 hours or sooner.

  5. identified Mar 03, 2026, 04:43 AM UTC

    We are continuously monitoring the situation, however our probes in this region remain unavailable at this time. To mitigate any impact to tests, customer should pick an alternate region to execute tests from. We'll share another update within in the next 12 hours or sooner.

  6. identified Mar 03, 2026, 04:27 PM UTC

    We are continuously monitoring the situation, however our probes in this region remain unavailable at this time. To mitigate any impact to tests, customers should pick an alternate region to execute tests from. We will share another update within in the next 24 hours or sooner.

  7. identified Mar 04, 2026, 04:49 PM UTC

    We are continuously monitoring the situation, however our probes in this region remain unavailable at this time. To mitigate any impact to tests, customers should pick an alternate region to execute tests from. We will share another update within in the next 24 hours or sooner.

  8. identified Mar 05, 2026, 07:19 PM UTC

    We are continuously monitoring the situation, however our probes in this region remain unavailable at this time. To mitigate any impact to tests, customers should pick an alternate region to execute tests from. We will share another update within in the next 24 hours or sooner.

  9. identified Mar 05, 2026, 11:48 PM UTC

    Due to a regional infrastructure disruption impacting an AWS datacenter in the Middle East -https://health.aws.amazon.com/health/status, the Dubai DEM probes will continue to be unavailable. As a result, Synthetic checks configured to run from this location may not execute as expected. While AWS continues recovery efforts, we recommend customers using this location temporarily update the configuration of their monitoring checks to run from an alternative testing location. Recommended action If you have checks configured to run from the Middle East/United Arab Emirates/Dubai, please update the configuration to use another available location to ensure uninterrupted monitoring. Steps: 1. Navigate to SolarWinds Observability → Digital Experience. 2. Open the affected check configuration. 3. Update the test location from Middle East/United Arab Emirates/Dubai to another available region. 4. Save the updated configuration. This change will help ensure continued test execution while the affected infrastructure is restored. Our teams are monitoring the situation closely and will provide updates as the impacted location becomes available again. If you need assistance identifying affected checks or selecting alternative monitoring locations, please contact SolarWinds Support and our team will be happy to help. Thank you for understanding.

  10. resolved Mar 06, 2026, 12:00 AM UTC

    We will continue to share progress and any new developments via email and in-app messaging.

Read the full incident report →

Minor February 4, 2026 Degraded Log Archives [NA-01] 1h Logs

Started Feb 04, 2026, 11:14 PM UTC· resolved Feb 05, 2026, 12:14 AM UTC

  1. investigating Feb 04, 2026, 11:14 PM UTC

    We are currently investigating an issue with log archives. As a result of this issue, log archiving will be delayed. We’ll provide an update within the hour.

  2. resolved Feb 05, 2026, 12:14 AM UTC

    The incident has been resolved. Log archives from February 4, 2026 01:00 to 21:00 UTC should now exist, 00:00 will be created later.

Read the full incident report →

Minor December 2, 2025 Degraded Webhook notifications [NA-01, NA-02, EU-01, AP-01] 35m Alerting

Started Dec 02, 2025, 01:07 PM UTC· resolved Dec 02, 2025, 01:42 PM UTC

  1. investigating Dec 02, 2025, 01:07 PM UTC

    We have identified an issue where webhook notifications from the SolarWinds Observability SaaS may contain malformed JSON in notification body. This could impact processing by any third party integrations via webhooks and using default templates. Notifications using custom templates are not affected. Our team is actively working on a resolution and will provide updates as soon as possible.

  2. monitoring Dec 02, 2025, 01:25 PM UTC

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

  3. monitoring Dec 02, 2025, 01:26 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Dec 02, 2025, 01:42 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 18, 2025 Delayed Data Ingestion [NA-01, EU-01] 2h 25m Alerting, Logs

Started Nov 18, 2025, 03:57 PM UTC· resolved Nov 18, 2025, 06:22 PM UTC

  1. investigating Nov 18, 2025, 03:57 PM UTC

    We’re currently investigating delay in Logs data ingestion. As a result, New data may not appear in the UI, alerts may be delayed, and some dashboards could show missing or outdated values. We’ll provide another update within the hour.

  2. identified Nov 18, 2025, 05:02 PM UTC

    We’ve identified the cause of the delay in Logs data ingestion and are working on a fix. New data may not appear in the UI, alerts could be delayed, and some dashboards might show missing or outdated values. We’ll provide an update within the hour.

  3. identified Nov 18, 2025, 06:04 PM UTC

    We’ve identified the cause of the delay in Logs data ingestion and are working on a fix. New data may not appear in the UI, alerts could be delayed, and some dashboards might show missing or outdated values. We’ll provide an update within the hour.

  4. monitoring Nov 18, 2025, 06:15 PM UTC

    A fix for the Logs data ingestion delay has been deployed, and we’re actively monitoring to ensure full recovery. Some new data may still be missing from the UI, alerts may be delayed, and dashboards could reflect outdated information. We’ll share another update within the hour.

  5. resolved Nov 18, 2025, 06:22 PM UTC

    The ingestion delay issue has been resolved. New data is now processing normally, and alerts and dashboards should reflect up-to-date information.

Read the full incident report →

Major November 18, 2025 Degraded Performance [NA-01, NA-02, EU-01, AP-01] 4h 3m Login, Alerting, APM, DEM and 8 more

Started Nov 18, 2025, 11:50 AM UTC· resolved Nov 18, 2025, 03:54 PM UTC

  1. investigating Nov 18, 2025, 11:50 AM UTC

    We’re currently investigating degraded performance in the web interface. Some customers may experience intermittent failures accessing the web interface. We’ll provide another update within the hour.

  2. investigating Nov 18, 2025, 12:09 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Nov 18, 2025, 12:24 PM UTC

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

  4. investigating Nov 18, 2025, 12:54 PM UTC

    We’re currently observing intermittent degradation in performance of the web interface and issue with delayed ingestion of logs. We’ll provide another update within the hour.

  5. investigating Nov 18, 2025, 01:53 PM UTC

    We are continuing to investigate this issue.

  6. identified Nov 18, 2025, 02:52 PM UTC

    Web Interface is accessible now. We’ve identified the cause of the delay in Logs data ingestion and are working on a fix. New data may not appear in the UI, alerts could be delayed, and some dashboards might show missing or outdated values. We’ll provide an update within the hour.

  7. resolved Nov 18, 2025, 03:54 PM UTC

    The web interface issues have been resolved and services have returned to normal operations.

Read the full incident report →

Minor October 31, 2025 Degraded Data Ingestion [NA-01 and EU-01] 1h 29m Alerting, Logs

Started Oct 31, 2025, 02:26 AM UTC· resolved Oct 31, 2025, 03:56 AM UTC

  1. investigating Oct 31, 2025, 02:26 AM UTC

    We are currently investigating an issue with [Logs] data ingestion. As a result of this issue, submitting new data through the API might fail temporarily. We’ll provide an update within the hour.

  2. investigating Oct 31, 2025, 02:46 AM UTC

    We are continuing to investigate this issue.

  3. identified Oct 31, 2025, 03:03 AM UTC

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

  4. monitoring Oct 31, 2025, 03:50 AM UTC

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

  5. resolved Oct 31, 2025, 03:56 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 15, 2025 Delayed Data Ingestion EU-01 47m Logs

Started Sep 15, 2025, 01:14 AM UTC· resolved Sep 15, 2025, 02:02 AM UTC

  1. investigating Sep 15, 2025, 01:14 AM UTC

    We’re currently investigating delay in Logs data ingestion. As a result, new data may not appear in the UI, alerts may be delayed, and some dashboards could show missing or outdated values. We’ll provide another update within the hour.

  2. monitoring Sep 15, 2025, 01:50 AM UTC

    A fix for the Logs data ingestion delay has been deployed, and we’re actively monitoring to ensure full recovery. Some new data may still be missing from the UI, alerts may be delayed, and dashboards could reflect outdated information. We’ll share another update within the hour.

  3. resolved Sep 15, 2025, 02:02 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 5, 2025 Delayed Data Ingestion NA-01 19m APM

Started Sep 05, 2025, 11:31 PM UTC· resolved Sep 05, 2025, 11:50 PM UTC

  1. investigating Sep 05, 2025, 11:31 PM UTC

    We’re currently investigating delay in Traces data ingestion. As a result, New data may not appear in the UI, alerts may be delayed, and some dashboards could show missing or outdated values. We’ll provide another update within the hour.

  2. identified Sep 05, 2025, 11:42 PM UTC

    We’ve identified the cause of the delay in Traces data ingestion and are working on a fix. New data may not appear in the UI, alerts could be delayed, and some dashboards might show missing or outdated values. We’ll provide an update within the hour.

  3. monitoring Sep 05, 2025, 11:46 PM UTC

    A fix for the Traces data ingestion delay has been deployed, and we’re actively monitoring to ensure full recovery. Some new data may still be missing from the UI, alerts may be delayed, and dashboards could reflect outdated information. We’ll share another update within the hour.

  4. resolved Sep 05, 2025, 11:50 PM UTC

    The ingestion delay issue has been resolved. New data is now processing normally, and alerts and dashboards should reflect up-to-date information.

Read the full incident report →

Minor August 22, 2025 Delayed Data Ingestion [Na-01] 2h 54m APM

Started Aug 22, 2025, 05:02 AM UTC· resolved Aug 22, 2025, 07:56 AM UTC

  1. investigating Aug 22, 2025, 05:02 AM UTC

    We’ve identified the cause of the delay in traces and metrics data ingestion and are working on a fix. New data may not appear in the UI, alerts could be delayed, and some dashboards might show missing or outdated values. We’ll provide an update within the hour.

  2. investigating Aug 22, 2025, 05:56 AM UTC

    we are continuing to investigate this issue.

  3. investigating Aug 22, 2025, 07:07 AM UTC

    We’re currently investigating delay in Metrics and Traces data ingestion. As a result, New data may not appear in the UI, alerts may be delayed, and some dashboards could show missing or outdated values. We’ll provide another update within the hour.

  4. monitoring Aug 22, 2025, 07:48 AM UTC

    A fix for the Metrics and Traces data ingestion delay has been deployed, and we’re actively monitoring to ensure full recovery. Some new data may still be missing from the UI, alerts may be delayed, and dashboards could reflect outdated information. We’ll share another update within the hour.

  5. resolved Aug 22, 2025, 07:56 AM UTC

    The ingestion delay issue has been resolved. New data is now processing normally, and alerts and dashboards should reflect up-to-date information.

Read the full incident report →

Minor July 21, 2025 Degraded Data Ingestion [NA-02] 2h 45m APM, Logs

Started Jul 21, 2025, 11:48 PM UTC· resolved Jul 22, 2025, 02:34 AM UTC

  1. investigating Jul 21, 2025, 11:48 PM UTC

    We are currently investigating an issue with Logs/Metrics/Traces data ingestion. As a result of this issue, submitting new data through the API might fail temporarily. We’ll provide an update within the hour.

  2. investigating Jul 22, 2025, 12:44 AM UTC

    We are currently investigating an issue with Logs/Metrics/Traces data ingestion. As a result of this issue, submitting new data through the API might fail temporarily. We’ll provide an update within the hour.

  3. investigating Jul 22, 2025, 01:44 AM UTC

    We are currently investigating an issue with Logs/Metrics/Traces data ingestion. As a result of this issue, submitting new data through the API might fail temporarily. We’ll provide an update within the hour.

  4. monitoring Jul 22, 2025, 02:20 AM UTC

    A fix has been implemented for the Logs/Metrics/Traces data ingestion issue. We’re actively monitoring system stability and verifying end-to-end delivery across impacted systems. We’ll provide an update within the hour.

  5. resolved Jul 22, 2025, 02:34 AM UTC

    The data ingestion issue has been resolved and systems are stable.

Read the full incident report →