New Relic

Affected: APM : US, APM Agent : US, Browser : US, Browser Agent : US, Infrastructure : US, Event API : US, Logs : US, Incident Intelligence API : US, Mobile : US, Infrastructure Agent : US, NRQL : US, Log API : US, Serverless : US, Metric API : US, Synthetics : US, Mobile Agent : US, OTLP API : US, Trace API : US, Synthetics : US

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 high confidence (taxonomy v0.2).

1. investigating 2026-09-25 19:57 UTC

   We are currently investigating a service interruption where a subset of customers may be experiencing delayed data in queries, charts, and dashboards as well as delayed or missing alert notifications for related data. Affected alerts are currently being suppressed.

2. investigating 2026-09-25 20:15 UTC

   We are continuing to investigate a service interruption where a subset of customers in the US region may be experiencing delayed data in queries, charts, and dashboards as well as delayed or missing alert notifications for related data. Affected alerts are currently being...

3. investigating 2026-09-25 20:39 UTC

   We are seeing recovery from some impacted services as we continue investigating a service interruption where a subset of customers in the US region may be experiencing delayed data in queries, charts, and dashboards as well as delayed or missing alert notifications for related...

4. identified 2026-09-25 21:27 UTC

   We continue seeing recovery for impacted services as we work to resolve this service interruption where a subset of customers in the US region may be experiencing delayed data in queries, charts, and dashboards as well as delayed or missing alert notifications for related data....

5. identified 2026-09-25 22:18 UTC

   At this time, we are seeing increased recovery of impacted services related to delayed data in queries, charts, and dashboards as well as delayed or missing alert notifications for related data in the US region.

6. resolved 2026-09-25 22:33 UTC

   Between 19:24 UTC and 22:04 UTC, a subset of customers in the US region may have experienced delayed data in queries, charts, and dashboards as well as delayed, missing or suppressed alert notifications for related data. We have investigated and resolved this service...

Excerpts are shortened. Read the full incident on New Relic'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. resolved 2026-09-25 03:56 UTC

   Between 01:10 UTC and 03:33 UTC on September 25th, some customers in the US, EU, and JP regions may have experienced intermittent UI errors while navigating the New Relic UI. Data ingest and alert notifications were not impacted. We have resolved this issue and impacted services...

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

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. monitoring 2026-09-16 10:08 UTC

   If you are experiencing issues and unable to access In-App support, please reach out to our Support team through this form: https://support.newrelic.com/s/contact-new-relic-support-form

2. resolved 2026-09-16 15:40 UTC

   All in-app services have returned to normal operations. Please reach out to New Relic support for assistance with any issues.

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

Affected: APM Agent : Europe, Browser Agent : Europe, Event API : Europe, Incident Intelligence API : Europe, Infrastructure Agent : Europe, Log API : Europe, Metric API : Europe, Mobile Agent : Europe, OTLP API : Europe, Trace API : Europe, Synthetics : Europe

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-09-16 00:14 UTC

   Between 23:06 UTC and 23:16 UTC, some customers in the EU region may have experienced errors when sending metric timeslice data to New Relic, issues in viewing metric timeslice data in real time, and delayed or missing alert notifications related to real time data. Impacted data...

Excerpts are shortened. Read the full incident on New Relic'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. investigating 2026-08-03 09:58 UTC

   We are investigating an issue where some customers in the EU and US regions may experience delays or errors when viewing the alerts and activity page.

2. resolved 2026-08-03 10:15 UTC

   Between 08:13 and 9:30 UTC on August 3rd, customers in the EU and US regions may have experienced an issue when trying to load the Alerts and Issues page in the New Relic UI. The issue is now resolved, and the impacted services have returned to normal service. Please close and...

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

Affected: APM : US, APM : Europe, Alerts : US, Alerts : Europe, APM : JP, Alerts : JP

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-07-17 10:21 UTC

   Between 15:00 UTC on July 14th and 10:00 UTC on July 17th, we experienced an issue where some customers experienced authorization issues when attempting to create, read or update E2M (Events-2-Metrics) rules in the US, EU and JP regions. This was due to a recent change we have...

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

Affected: Alerts : Europe, APM : Europe, Event API : Europe, Incident Intelligence API : Europe, Dashboards : Europe, Log API : Europe, Metric API : Europe, OTLP API : Europe, Trace API : Europe

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-07-06 08:23 UTC

   Between 07:20 and 08:12 UTC on July 6th, we experienced an issue where some customers in the EU region may have experienced a delay of entity relationships appearing and refreshing in the New Relic platform. The issue is now resolved and the impacted services have returned to...

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

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 high confidence (taxonomy v0.2).

1. resolved 2026-05-18 16:25 UTC

   Between 10:30 UTC and 13:32 UTC on May 16th, some customers in the US and EU regions may have experienced delayed data in queries, charts, and dashboards as well as delayed, missing, or false alert notifications for impacted data related to a service interruption involving a 3rd...

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

Affected: Alerts : US, APM : US, Auto-Telemetry with Pixie : US, AWS Lambda Integration : US, Browser : US, Dashboards : US, Incident Intelligence : US, Infrastructure : US, Infrastructure Integrations : US, Logs : US, Lookout : US, Mobile : US, Open Instrumentation : US, Proactive Detection : US, Serverless : US, Synthetics : US

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-05-15 00:06 UTC

   We are investigating an interruption where some customers in the US region may be experiencing issues loading the different pages in the New Relic UI. Some customers in the US region may be experiencing delayed data in queries, charts, and dashboards as well as delayed or...

2. investigating 2026-05-15 00:42 UTC

   We continue investigating an interruption where some customers in the US region may be experiencing issues loading the different pages in the New Relic UI. Some customers in the US region may be experiencing delayed data in queries, charts, and dashboards. After further review,...

3. monitoring 2026-05-15 01:16 UTC

   We are seeing recovery for impacted services, and continue monitoring New Relic systems for full recovery. Some customers in the US region may have experienced issues loading different pages in the New Relic UI. Some customers in the US region may have also experienced delayed...

4. resolved 2026-05-15 01:45 UTC

   Between 22:30 UTC on May 14th and 01:00 UTC on May 15th, 2026, some customers in the US region may have experienced issues loading different pages in the New Relic UI. Some customers may have also experienced delayed data in queries, charts, and dashboards. Data ingest and...

Excerpts are shortened. Read the full incident on New Relic'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. investigating 2026-04-13 12:44 UTC

   We are investigating an issue where some customers may be unable to query live edge data in the US region. Data ingest and alert notifications are not impacted by this interruption.

2. investigating 2026-04-13 12:49 UTC

   We are investigating an issue where some customers may be unable to query live edge data in the US region. Data ingest and alert notifications are not impacted by this interruption.

3. investigating 2026-04-13 12:55 UTC

   We are investigating an issue where some customers may be unable to query live edge data in the US region. Data ingest and alert notifications are not impacted by this interruption.

4. investigating 2026-04-13 13:58 UTC

   We are continuing to investigate an issue where some customers may be unable to query live edge data and some customers may notice stopped synthetic monitors in the US region. Technical teams are actively engaged and are exploring mitigation steps to address the issue. Data...

5. investigating 2026-04-13 14:41 UTC

   We are still investigating an issue where some customers may be unable to query live edge data and some customers may notice stopped synthetic monitors in the US region. We continue to work on the issue and understand root cause. We will continue to provide updates as we have...

6. resolved 2026-04-13 15:17 UTC

   Between 10:30 AM and 2:40 PM UTC on April 13th, some customers may have experienced an issue to query live edge data and some customers may have noticed stopped synthetic monitors in the US region. The issue is now resolved and impacted services have returned to normal...

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

Affected: Synthetics : US

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-04-09 09:51 UTC

   Some customers in the US region may be experiencing delayed Synthetics Checks execution data in queries with Synthetics Job Manager.

2. identified 2026-04-09 12:28 UTC

   We have identified the issue and working on a solution

3. monitoring 2026-04-09 14:05 UTC

   Our team has now issued a fix and are monitoring the issue.

4. monitoring 2026-04-09 16:48 UTC

   Between 02:34 UTC and 16:45 UTC on April 9th, 2026, some customers in the US region may have experienced delayed Synthetics Checks execution data in queries with Synthetics Job Manager. Impacted data may not be recoverable. We have investigated and resolved this service...

5. resolved 2026-04-09 20:46 UTC

   Between 02:34 UTC and 16:40 UTC on April 9th, 2026, some customers in the US region may have experienced delayed Synthetics Checks execution data in queries with Synthetics Job Manager. Impacted data may not be recoverable. We have investigated and resolved this service...

Excerpts are shortened. Read the full incident on New Relic'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. investigating 2026-03-24 05:22 UTC

   Some customers in the US and EU regions may experience discrepancies in NRComputeusage and NRConsumption usage values

2. investigating 2026-03-24 06:02 UTC

   We are continuing to investigate an issue where some customers in the US and EU regions may experience discrepancies in NRComputeusage and NRConsumption usage values

3. resolved 2026-03-24 10:31 UTC

   Between 2026-03-24 05:22:07 UTC and 2026-03-24 08:21:09 UTC on March Tuesday, some customers in the US/EU region may have experienced discrepancies in the NrComputeUsage and NRCompute usage values We have investigated and resolved a service interruption and impacted services...

Excerpts are shortened. Read the full incident on New Relic'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).

Names an upstream provider: Azure.

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

   We are investigating a service interruption where some customers in the US region with Azure integrations may experience 5xx errors when sending data to New Relic, issues in viewing data in real time, and delayed or missing alert notifications related to real time data. Impacted...

2. investigating 2026-03-20 15:53 UTC

   We are investigating a service interruption where some customers in the US region with Azure integrations may experience 5xx errors when sending data to New Relic, issues in viewing data in real time, and delayed or missing alert notifications related to real time data. Impacted...

3. investigating 2026-03-20 15:59 UTC

   We are seeing recovery for Azure integrations at this time. Some customers in the US region with Azure integrations may experience errors when sending data to New Relic, issues in viewing data in real time, and delayed or missing alert notifications related to real time data....

4. resolved 2026-03-20 16:10 UTC

   We have resolved this service interruption and impacted services have returned to normal operation. Between 15:10 UTC and 16:08 UTC, some customers in the US region with Azure integrations may have experiencde errors when sending data to New Relic, issues in viewing data in real...

Excerpts are shortened. Read the full incident on New Relic'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. investigating 2026-03-03 00:19 UTC

   Some customers in the US and EU regions may be experiencing delayed data in queries, charts, and dashboards as well as delayed or missing alert notifications for related data.

2. investigating 2026-03-03 00:21 UTC

   Some customers in the US and EU regions may be experiencing delayed data in queries, charts, and dashboards as well as delayed or missing alert notifications for related data.

3. investigating 2026-03-03 00:36 UTC

   We are continuing to investigate an issue where some customers in the US region may be experiencing delayed data in queries, charts, and dashboards as well as delayed or missing alert notifications for related data.

4. investigating 2026-03-03 01:02 UTC

   We are still investigating the an issue where some customers in the US region may be experiencing delayed data in queries, charts, and dashboards as well as delayed or missing alert notifications for related data. We have been seeing signs of recovery, and will continue to...

5. monitoring 2026-03-03 02:28 UTC

   We continue to see signs of recovery as we monitor impacted services. Some customers in the US region may be experiencing delayed data in queries, charts, and dashboards as well as delayed or missing alert notifications for related data. We will continue to provide updates until...

6. resolved 2026-03-03 02:59 UTC

   We resolved this service interruption and impacted services have returned to normal operation. Between 00:11 UTC and 02:45 UTC on March 3rd, 2026, some customers may have experienced delayed data in queries, charts, and dashboards as well as delayed or missing alert...

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

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-03-02 07:06 UTC

   Some customers in the US and EU region may experience delay in executing synthetics monitors

2. investigating 2026-03-02 07:35 UTC

   We have engaged our Cloud provider to assist with further investigation and are evaluating additional mitigation efforts.

3. resolved 2026-03-02 09:42 UTC

   Between 06:56 UTC and 08:44 UTC on March 02nd some customers in the US or EU region may have experienced Delay in executing synthetics monitors .We have investigated and resolved this service interruption and impacted services have returned to normal operations

Excerpts are shortened. Read the full incident on New Relic'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-02-18 10:06 UTC

   Between 09:20 UTC and 09:44 UTC on Wed Feb 18 2026, some customers in the USEU region may have experienced delayed data in queries, charts, and dashboards. We have investigated and resolved this service interruption and impacted services have returned to normal operations.

Excerpts are shortened. Read the full incident on New Relic'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. investigating 2026-02-05 16:20 UTC

   We are currently investigating an issue causing errors with Distributed Tracing

2. monitoring 2026-02-05 16:40 UTC

   Our Team has now issued a fix and are monitoring the issue.

3. resolved 2026-02-05 17:22 UTC

   Between 15:15 UTC and 16:30 UTC some customers may have experienced an issue with Distributed Tracing.

Excerpts are shortened. Read the full incident on New Relic'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. investigating 2026-01-21 22:23 UTC

   We are investigating an issue with alert behavior. Some customers in the US region may experience delayed or missing alert notifications related to real-time data.

2. investigating 2026-01-21 22:53 UTC

   We are continuing to investigate an issue with alerts irregularities where a subset of customers in the US region may experience delayed or missing alert notifications for real-time data.

3. identified 2026-01-22 00:00 UTC

   We have implemented a fix and are starting to see recovery for impacted services. A subset of customers in the US region may experience delayed or missing alert notifications for real-time data.

4. resolved 2026-01-22 00:46 UTC

   We have investigated and resolved this service interruption and impacted services have returned to normal operations. Between 19:58 UTC on January 21st, and 00:34 UTC on January 22nd, 2026, a subset of customers in the US region may have experienced issues with alert behavior...

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

Affected: APM : Europe, Alerts : US, Alerts : Europe, APM : US, Browser : Europe, Infrastructure : US, Infrastructure : Europe, Auto-Telemetry with Pixie : US, Logs : US, AWS Lambda Integration : US, Logs : Europe, Browser : US, Mobile : Europe, Infrastructure Agent : US, Infrastructure Agent : Europe, Dashboards : US, NRQL : Europe, Log API : US, Log API : Europe, Serverless : Europe, Incident Intelligence : US, Metric API : US, Metric API : Europe, Infrastructure : US, Synthetics : Europe, Infrastructure : Europe, OTLP API : US, OTLP API : Europe, Infrastructure Integrations : US, Infrastructure Integrations : Europe, Logs : US, Logs : Europe, Lookout : US, Mobile : US, Open Instrumentation : US, Proactive Detection : US, Serverless : US, Synthetics : US

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-01-12 15:21 UTC

   We are currently investing an issue causing timeouts/query lag in NRDB

2. investigating 2026-01-12 15:22 UTC

   We are continuing to investigate this issue.

3. investigating 2026-01-12 15:53 UTC

   We have engaged our additional teams to assist with further investigation and are evaluating additional mitigation efforts.

4. identified 2026-01-12 17:36 UTC

   Some customers in the US and EU region may experience errors when sending data to New Relic, issues in viewing data in real time, and delayed or missing alert notifications related to real time data. We are seeing recovery from mitigating actions and will continue to provide...

5. resolved 2026-01-12 18:10 UTC

   Our teams have resolved two concurrent service interruptions affecting data ingestion and query services. On January 12th, 2026, a subset of customers in the US and EU regions may have experienced latency or timeouts when querying data in New Relic. Teams implemented a fix,...

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

Affected: Infrastructure : US, Infrastructure : Europe

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 2025-12-18 23:30 UTC

   We are investigating a potential service interruption that may impact some customers. Please continue to monitor this page for updates.

2. investigating 2025-12-18 23:52 UTC

   Some customers in the US and EU region may experience false loss of signal alert notifications.

3. investigating 2025-12-19 00:23 UTC

   We are continuing to investigate this issue.

4. investigating 2025-12-19 01:00 UTC

   We are continuing to investigate this issue.

5. monitoring 2025-12-19 01:56 UTC

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

6. resolved 2025-12-19 02:21 UTC

   Between 20:30:20 UTC on December 18th and 01:57:55 UTC on December 19th, some customers in the US region may have experienced false alerts and false loss of signal alert notifications. We have investigated and resolved this service interruption and impacted services have...

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

Affected: APM Agent : Europe, Browser Agent : Europe, Event API : Europe, Incident Intelligence API : Europe, Infrastructure Agent : Europe, Log API : Europe, Metric API : Europe, Mobile Agent : Europe, OTLP API : Europe, Trace API : Europe, Synthetics : Europe

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 2025-11-19 11:48 UTC

   We are investigating an issue with data ingest

2. identified 2025-11-19 12:16 UTC

   We have engaged our Product Management Team to assist with further investigation and are evaluating additional mitigation efforts.

3. monitoring 2025-11-19 12:19 UTC

   Some customers in the EU region have reported recovery of data ingest.

4. monitoring 2025-11-19 12:34 UTC

   Some customers in the EU region have reported recovery of data ingest.

5. resolved 2025-11-19 12:52 UTC

   Between 11:15 UTC and 12:40 UTC on November 19, some customers in the EU region may have experienced difficulties in data ingest. We have investigated and resolved this service interruption and impacted services have returned to normal operations

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

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

1. investigating 2025-11-18 12:34 UTC

   Some customers in the EU region may experience difficulty logging into New Relic accounts. If you are experiencing issues and unable to access In-App support, please reach out to our Support team through this form: https:support.newrelic.comscontact-new-relic-support-form.

2. identified 2025-11-18 14:15 UTC

   We have engaged our cloud provider to assist with further investigation and are evaluating additional mitigation efforts. Some customers in the EU region may continue experience difficulty with the New Relic UI. If you are experiencing issues and unable to access In-App support,...

3. monitoring 2025-11-18 15:23 UTC

   We have put in place mitigations for an issue with a Cloud Provider which has been causing UI issues for customers in the EU region. We will continue to monitor the situation while our Cloud Provider is working on a fix. If you continue to experience issues and are unable to...

4. resolved 2025-11-18 20:19 UTC

   Between 11:46 UTC and 15:48 UTC on November 18th, 2025, some customers in the EU region may have experienced issues loading New Relic UI. The service interruption was investigated and resolved with our cloud provider and impacted services have returned to normal operations.

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

Affected: Synthetics : US, Synthetics : Europe

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

1. identified 2025-10-20 08:40 UTC

   Some customers in the US and EU region may experience errors when sending data to New Relic using cloud or synthetics, issues in viewing data in real time, and delayed or missing data in synthetics and cloud.

2. identified 2025-10-20 08:45 UTC

   Some customers in the US and EU region may experience errors when sending data to New Relic using cloud or synthetics, issues in viewing data in real time, and delayed or missing data in synthetics and cloud.

3. identified 2025-10-20 09:14 UTC

   Some customers in the US and EU region may experience errors when sending data to New Relic using cloud or synthetics, issues in viewing data in real time, delays in Entity events appearing in customer account

4. monitoring 2025-10-20 11:56 UTC

   We have engaged our Cloud provider to assist with further investigation and have implemented additional mitigation efforts. Which should lead to full recovery in synthetics and some recovery in Cloud. However some customers may still experience some delays in entity events...

5. monitoring 2025-10-20 12:13 UTC

   We have engaged our Cloud provider to assist with further investigation and have implemented additional mitigation efforts. Which has lead to full recovery in synthetics and some recovery in Cloud. However some customers may still experience some delays in entity events...

6. monitoring 2025-10-20 17:54 UTC

   We have been able to confirm an ongoing network interruption with our cloud provider. As a result, some customers in the US and EU regions may experience intermittent irregularities for some features including synthetics, infinite tracing, cloud integrations, mobile...

7. monitoring 2025-10-20 19:57 UTC

   We are seeing signs of recovery for impacted services as our cloud provider continues to resolve the ongoing network interruption. We will continue to monitor the situation and provide updates as more information is available.

8. resolved 2025-10-20 21:33 UTC

   Affected New Relic services have returned to normal operations following the resolution of the cloud provider network interruption. Our teams preliminary investigation indicates that New Relic ingest systems continued to function as expected throughout the interruption; however,...

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

Affected: Browser : US, Browser Agent : US, Browser : US

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 2025-10-10 16:00 UTC

   A subset of customers in the US region may experience delayed Browser Monitoring data for queries, charts, and dashboards as well as delayed or missing alert notifications for related data. We are starting to see recovery, and will provide our next update when our services have...

2. investigating 2025-10-10 16:00 UTC

   We are continuing to investigate this issue.

3. investigating 2025-10-10 16:01 UTC

   A subset of customers in the US region may experience delayed Browser Monitoring data for queries, charts, and dashboards as well as delayed or missing alert notifications for related data. We are starting to see recovery, and will provide our next update when our services have...

4. identified 2025-10-10 16:43 UTC

   We have identified an issue impacting browser data in the US region. A subset of US customers may be experiencing delayed Browser Monitoring data for queries, charts, and dashboards as well as delayed or missing alert notifications for related data. We continue to see recovery,...

5. identified 2025-10-10 17:02 UTC

   We have identified an issue impacting browser data in the US region. A subset of US customers may be experiencing delayed Browser Monitoring data for queries, charts, and dashboards. We continue to see recovery and alerts were unsuppressed. We will continue to provide updates...

6. identified 2025-10-10 17:02 UTC

   We are continuing to work on a fix for this issue.

7. identified 2025-10-10 17:03 UTC

   We have identified an issue impacting browser data in the US region. A subset of US customers may be experiencing delayed Browser Monitoring data for queries, charts, and dashboards. We continue to see recovery and alerts were unsuppressed. We will continue to provide updates...

8. identified 2025-10-10 17:56 UTC

   We are continuing to investigate an issue impacting browser data and have applied alert suppression to prevent our customers from receiving a high volume of false positive alert notifications for affected data. A subset of US customers may be experiencing delayed Browser...

9. identified 2025-10-10 18:46 UTC

   We are continuing to mitigate an issue impacting browser data and have recently unsuppressed alerts due to our current recovering state. A subset of US customers may be experiencing delayed Browser Monitoring data for queries, charts, and dashboards. We will continue to provide...

10. resolved 2025-10-10 20:12 UTC

    Between 13:21 UTC and 19:09 UTC, a subset of customers in the US region may have experienced delayed browser monitoring data for queries, charts, and dashboards as well as delayed or missing alert notifications for related data when alerts were not suppressed. We have resolved...

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

Affected: APM Agent : US, Browser Agent : US, Event API : US, Incident Intelligence API : US, Infrastructure Agent : US, Log API : US, Metric API : US, Mobile Agent : US, OTLP API : US, Trace API : US, Synthetics : US

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 2025-10-07 17:04 UTC

   We are investigating a potential service interruption that may impact some customers. Please continue to monitor this page for updates.

2. investigating 2025-10-07 17:34 UTC

   Some customers in the US region may be experiencing a delay in data appearing within the New Relic UI. Alert notifications may also be delayed as a result.

3. resolved 2025-10-07 18:48 UTC

   Between 16:20 UTC and 17:28 UTC on Tuesday, October 7th, 2025, some customers in the US region may have experienced delays in data appearing within the New Relic UI. Alert notifications may have also been delayed as a result. We have investigated and resolved this service...

Excerpts are shortened. Read the full incident on New Relic'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 2025-09-26 22:42 UTC

   Between 21:48 UTC and 22:36 UTC on September 26, Friday, some customers in the US & EU region may have experienced delayed data in queries, charts, and dashboards as well as delayed or missing alert notifications for related data. We have investigated and resolved this service...

Excerpts are shortened. Read the full incident on New Relic'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 2025-09-25 16:15 UTC

   Between 15:11 UTC and 15:38 UTC on September 25th, some customers in the EU region may have experienced delayed data in queries, charts, and dashboards as well as delayed or missing alert notifications for related data. There was no impact to data ingest. We have investigated...

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

Affected: Synthetics : US

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-09-09 12:52 UTC

   We are currently investigating a service interruption impacting our Synthetics checks.

2. investigating 2025-09-09 13:14 UTC

   Our team continues to investigate the service interruption. Some customers in the US region will see impacted Synthetic checks.

3. identified 2025-09-09 14:15 UTC

   The issue has been identified and our team and working to implement a fix.

4. monitoring 2025-09-09 14:50 UTC

   The fix has now been implemented and services have returned to normal. The team are continuing to monitor the recovery

5. resolved 2025-09-09 15:15 UTC

   Between 10:47 UTC and 14:59 UTC, some customers in the US region may have experienced irregularities for Synthetics such as delays for job processing and results. We have investigated and resolved this interruption and impacted services have returned to normal operations.

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

Affected: APM Agent : US, APM : US, Browser Agent : US, Browser : US

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 2025-09-08 14:21 UTC

   We are investigating a potential service interruption that may impact some customers. Please continue to monitor this page for updates.

2. investigating 2025-09-08 14:34 UTC

   We are investigating an issue with the summary page not loading for APM and Browser for some customers. Please continue to monitor this page for updates.

3. resolved 2025-09-08 14:41 UTC

   Between 14:05 UTC and 14:25 UTC on September 8, some customers in the US region may have experienced an issue with the summary page not loading for APM and Browser. We have investigated and resolved this service interruption and impacted services have returned to normal...

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

Affected: Metric API : Europe

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

Names an upstream provider: AWS, Google Cloud.

1. investigating 2025-09-02 11:49 UTC

   We are investigating an issue with delay in data related to Metrics and Tags

2. investigating 2025-09-02 11:49 UTC

   We are investigating an issue with delay in data related to Metrics and Tags

3. investigating 2025-09-02 12:15 UTC

   We are investigating an issue with delay in data related to Metrics and Tags

4. investigating 2025-09-02 12:26 UTC

   Some customers in the EU region may experience delay in viewing Metrics and Tag Data.

5. monitoring 2025-09-02 13:06 UTC

   Some customers in the EU region have reported recovery in data related to Metrics and Tags.

6. resolved 2025-09-02 13:15 UTC

   Between 10:27 UTC and 13:12 UTC on August 2nd, some customers in the EU region may have experienced delayed in data related to Metrics and Tags. We have investigated and resolved this service interruption and impacted services have returned to normal operations.

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

Affected: Dashboards : US, Dashboards : Europe

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 2025-08-07 15:00 UTC

   We are investigating a potential service interruption that may impact some customers. Please continue to monitor this page for updates.

2. investigating 2025-08-07 15:06 UTC

   Some customers in the US and EU regions may be experiencing delayed golden signal data in queries, charts, and dashboards as well as delayed or missing alert notifications for related data.

3. identified 2025-08-07 15:17 UTC

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

4. monitoring 2025-08-07 15:25 UTC

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

5. resolved 2025-08-07 15:42 UTC

   Between 13:51 UTC and 15:20 UTC, some customers in the US and EU region may have experienced errors sending golden signal data to New Relic, issues in viewing data in real time, and delayed or missing alert notifications related to real time data.

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

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

1. investigating 2025-06-12 19:31 UTC

   Starting at 17:53 UTC, some customers in the US and EU regions may experience timeouts, irregularities, and delays in their chart data related to a global outage happening across industry cloud providers.

2. identified 2025-06-12 20:17 UTC

   We are continuing to investigate this interruption with our cloud providers. We are seeing recovery of some impacted services and are taking action to mitigate impact where possible.

3. resolved 2025-06-12 20:58 UTC

   Between 17:54 UTC and 20:22 UTC, some customers in the US and EU region may have experienced various irregularities for data availability and alert notifications. Impacted services have returned to normal operations, following the recovery of our dependent cloud provider systems.

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

Affected: APM : US, APM Agent : US, Browser : US, Browser Agent : US, Mobile : US, Mobile Agent : US

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 2025-05-25 20:52 UTC

   Beginning at 20:07 to 20:49 May 25 UTC, some customers in the US region may have experienced delayed APM, Browser, Mobile data in queries, charts, and dashboards as well as delayed or missing alert notifications for related data. We suppressed alerts from 20:36 to 20:48 May 25...

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

Affected: APM : US, APM Agent : US

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. identified 2025-05-25 01:34 UTC

   Some customers in the US region may be experiencing delayed APM data in queries, charts, and dashboards as well as delayed or missing alert notifications for related data. To prevent our customers from receiving a high volume of false positive alert notifications, we have...

2. identified 2025-05-25 02:08 UTC

   Beginning at 01:00 May 25 UTC some customers in the US region may be experiencing delayed APM data in queries, charts, and dashboards as well as delayed or missing alert notifications for related data. To prevent our customers from receiving a high volume of false positive alert...

3. identified 2025-05-25 02:19 UTC

   Beginning at 01:00 May 25 UTC some customers in the US region may be experiencing delayed APM data in queries, charts, and dashboards as well as delayed or missing alert notifications for related data. We have reduced the latency at this point and are investigating further. To...

4. resolved 2025-05-25 03:00 UTC

   Beginning at 01:00 and 02:58 May 25 UTC, some customers in the US region may have experienced delayed APM data in queries, charts, and dashboards as well as delayed or missing alert notifications for related data. We suppressed alerts from 01:32 to 02:58 May 25 UTC. We have...

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

Affected: APM Agent : US

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. identified 2025-05-24 06:09 UTC

   Some customers in the US region may be experiencing delayed APM data in dashboards.

2. investigating 2025-05-24 07:11 UTC

   Starting 04:35 May 24 UTC some customers in the US region may experience delayed APM data in dashboards. We have reduced the latency at this point and are investigating further.

3. resolved 2025-05-24 07:45 UTC

   Between 04:35 May 24 UTC and 07:34 May 24 UTC some customers in the US region may have experienced delayed APM data in dashboards. We have resolved this interruption and impacted services have returned to normal operations.

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

Affected: APM : US, Alerts : US, APM : US, Infrastructure : US, Dashboards : US, Infrastructure : US, Infrastructure Integrations : US

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 2025-04-16 13:46 UTC

   We are investigating a potential service interruption that may impact some customers. Please continue to monitor this page for updates.

2. identified 2025-04-16 13:53 UTC

   We have identified the issue and are working on a fix for the issue.

3. identified 2025-04-16 14:43 UTC

   Starting at around 13:00 UTC on the 16/04/2025, a subset of customers may be experiencing missed alerts and delayed data affecting dashboards, UI's and API queries. The primary issue triggering the incident has been identified and is in the process of being remediated.

4. identified 2025-04-16 14:58 UTC

   Some customers in the US region may be experiencing delayed data in queries, charts, and dashboards as well as delayed or missing alert notifications for related data. We are seeing recovery of some impacted services and are continuing to monitor.

5. investigating 2025-04-16 16:13 UTC

   Starting approx 13:00 UTC on the 16th of April 2025, a subset of customers may have experienced missed alerts, delayed data impacting dashboards, UIs and API queries. We have reduced the latency at this point and are monitoring recovery.

6. monitoring 2025-04-16 16:14 UTC

   Starting approx 13:00 UTC on the 16th of April 2025, a subset of customers may have experienced missed alerts, delayed data impacting dashboards, UIs and API queries. We have reduced the latency at this point and are monitoring recovery.

7. resolved 2025-04-16 16:51 UTC

   Between 12:52 UTC and 15:28 UTC on April 16th, 2025, some customers in the US may have experienced delayed data in queries, charts, and dashboards as well as delayed, missing, or false positive alert notifications for related data. We have resolved this interruption and impacted...

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

Affected: APM Agent : Europe, Browser Agent : Europe, Event API : Europe, Incident Intelligence API : Europe, Infrastructure Agent : Europe, Log API : Europe, Metric API : Europe, Mobile Agent : Europe, OTLP API : Europe, Trace API : Europe, Synthetics : Europe

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-03-18 18:50 UTC

   We are investigating an issue with data ingest for various data types. Some customers in the EU region may experience errors when sending data to New Relic, issues in viewing data in real time, and delayed or missing alert notifications related to real time data.

2. monitoring 2025-03-18 18:55 UTC

   We are investigating an issue with data ingest for various data types. Some customers in the EU region may experience errors when sending data to New Relic, issues in viewing data in real time, and delayed or missing alert notifications related to real time data.

3. investigating 2025-03-18 18:57 UTC

   We are investigating an issue with data ingest for various data types. Some customers in the EU region may experience errors when sending data to New Relic, issues in viewing data in real time, and delayed or missing alert notifications related to real time data.

4. investigating 2025-03-18 18:58 UTC

   We are continuing to investigate this issue.

5. identified 2025-03-18 19:05 UTC

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

6. resolved 2025-03-18 19:36 UTC

   Between 18:28 UTC and 18:58 UTC Tuesday March 18, 2025, some customers in the EU region may have experienced errors when sending data to New Relic, issues in viewing data in real time, and delayed or missing alert notifications related to real time data. We have investigated and...

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

Affected: Infrastructure : US, Infrastructure Agent : US, Infrastructure : US

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 2025-03-18 10:01 UTC

   We are investigating a potential service interruption that may impact some customers. Please continue to monitor this page for updates.

2. investigating 2025-03-18 10:04 UTC

   We are continuing to investigate this issue.

3. identified 2025-03-18 10:36 UTC

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

4. identified 2025-03-18 13:45 UTC

   We are continuing to work on a fix for this issue. This service interruption may impact some customers in in our US region

5. identified 2025-03-18 17:26 UTC

   We are investigating an issue affecting the reporting of infrastructure entity metadata from New Relic agents. Some customers in the US region may experience irregularities in charts, dashboards, and alert notifications for affected entities. New Relic teams have implemented a...

6. identified 2025-03-18 20:08 UTC

   Our teams are working to resolve an issue which has resulted in missing metadata for some infrastructure entities. Affected entities will be refreshed automatically through standard, automated mechanisms at various intervals; however, our teams are continuing to investigate...

7. identified 2025-03-18 23:09 UTC

   We are working to resolve the issue resulting in missing metadata for some infrastructure entities. Through standard operations, affected entities will be refreshed over the next 24 - 48 hours automatically. Additionally, our teams are continuing to investigate opportunities to...

8. identified 2025-03-19 13:58 UTC

   We are working to resolve the issue resulting in missing metadata for some infrastructure entities. We are seeing recovery of some affected entities through standard agent refresh behaviors and our teams continue to prioritize expediting recovery of remaining affected entity...

9. identified 2025-03-19 23:01 UTC

   We are seeing continued restoration of affected entity metadata through both standard agent refresh behaviors, as well as backup and recovery actions taken by our teams. Some customers in the US region may experience irregularities in charts, dashboards, and alert notifications...

10. resolved 2025-03-20 14:20 UTC

    The restoration of affected entity metadata has now been completed. Impacted services have returned to normal operations.

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

Affected: APM : Europe, Browser : Europe, Infrastructure : Europe, Logs : Europe, Mobile : Europe, NRQL : Europe, Serverless : Europe, Synthetics : Europe

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-03-08 22:17 UTC

   We are investigating a potential service interruption that may impact some customers. Please continue to monitor this page for updates.

2. identified 2025-03-08 22:21 UTC

   We are investigating a brief service interruption impacting alerts for select EU accounts. The issue has been mitigated while we investigate and no further actions are required by customers as we work to resolve this.

3. resolved 2025-03-08 22:41 UTC

   We resolved this service interruption and impacted services have returned to normal operation. Between 09:40 UTC and 09:45 UTC on March 8th, some customers in the EU region may have experienced missed/delayed alerts or false loss of signal alerts.

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

Affected: APM : US, APM Agent : US, Alerts : US, APM : US, Browser : US, Browser Agent : US, Infrastructure : US, Event API : US, Auto-Telemetry with Pixie : US, Logs : US, AWS Lambda Integration : US, Incident Intelligence API : US, Browser : US, Mobile : US, Infrastructure Agent : US, Dashboards : US, NRQL : US, Log API : US, Serverless : US, Incident Intelligence : US, Metric API : US, Synthetics : US, Infrastructure : US, Mobile Agent : US, OTLP API : US, Infrastructure Integrations : US, Logs : US, Trace API : US, Lookout : US, Synthetics : US, Mobile : US, Open Instrumentation : US, Proactive Detection : US, Serverless : US, Synthetics : US

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 2025-03-08 21:09 UTC

   We are investigating a service interruption impacting data from query responses which may be affecting some customers in the US region. No data drops have been observed at this time and no further actions are required by customers as we work to resolve this.

2. investigating 2025-03-08 21:20 UTC

   We have determined the service interruption has not impacted ingest or alerts but has to do with serving live queries. We are continuing to investigate and thank you for your patience while we work through this issue.

3. investigating 2025-03-08 21:46 UTC

   We are continuing to investigate this issue.

4. monitoring 2025-03-08 22:05 UTC

   The incident is now in recovery with data ingest and alerting unaffected.

5. resolved 2025-03-08 22:15 UTC

   We resolved this service interruption and impacted services have returned to normal operation. Between 08:27 UTC and 09:37 UTC on March 8th, some customers in the US region may have experienced missing data from live edge NRDB queries. Data ingest and alerts were not affected.

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

Affected: Mobile : US, Mobile : Europe

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 2025-03-05 07:40 UTC

   We are investigating a potential service interruption that may impact some customers. Please continue to monitor this page for updates.

2. investigating 2025-03-05 07:43 UTC

   New users are unable to login to Android application for the first time.

3. identified 2025-03-05 07:48 UTC

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

4. monitoring 2025-03-05 07:50 UTC

   A fix has been implemented and monitoring the results.

5. monitoring 2025-03-05 07:52 UTC

   We are continuing to monitor for any further issues.

6. resolved 2025-03-05 08:02 UTC

   Between 06:09 UTC and 07:43 UTC on March 5th 2025, some customers in the US and EU region may have experienced difficulties using the New Relic android application. We have investigated and resolved this service interruption and impacted services have returned to normal...

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

Affected: APM Agent : US

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 2025-03-03 12:50 UTC

   We are investigating a potential service interruption that may impact some customers. Some customers may experience Delay in APM timeslices dashboards.

2. identified 2025-03-03 12:56 UTC

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

3. resolved 2025-03-03 13:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on New Relic'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 2024-12-18 09:18 UTC

   We are investigating a potential service interruption that may impact some customers. Please continue to monitor this page for updates.

2. investigating 2024-12-18 09:24 UTC

   We are investigating a potential service interruption that may impact some customers. Please continue to monitor this page for updates.

3. investigating 2024-12-18 09:34 UTC

   Some customers in the US region may be experiencing the UI returning errors or not loading as expected. Data ingest and alert notifications are not impacted at this time. If you would like to create a support case linked to this issue please send an email to...

4. resolved 2024-12-18 09:47 UTC

   Between 9:11 UTC and 9:42 UTC on December 18th, some customers in the US regions may have experienced issues accessing the UI. We have investigated and resolved this service interruption and impacted services have returned to normal operations.

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

Affected: Dashboards : US, Dashboards : Europe

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 2024-12-10 10:50 UTC

   We are investigating a potential service interruption that may impact some customers. Please continue to monitor this page for updates.

2. investigating 2024-12-10 10:53 UTC

   We are continuing to investigate this issue.

3. investigating 2024-12-10 10:57 UTC

   We are investigating an issue that may impact the creation of new dashboards for customer accounts in the US and EU regions

4. resolved 2024-12-10 11:17 UTC

   Between 10:20 UTC and 11:00 UTC on December 10th, some customers in the US and EU regions may have experienced issues creating new dashboards. We have investigated and resolved this service interruption and impacted services have returned to normal operations.

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

Affected: APM : Europe, Browser : Europe, Infrastructure : Europe, Logs : Europe, Mobile : Europe, NRQL : Europe, Serverless : Europe, Synthetics : Europe

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 2024-12-05 23:20 UTC

   Some customers in the EU region may intermittently experience delayed alert notifications. Data ingest is not impacted at this time.

2. investigating 2024-12-05 23:25 UTC

   Some customers in the EU region may intermittently experience delayed alert notifications. Data ingest is not impacted at this time. We are continuing to investigate this issue.

3. investigating 2024-12-06 00:23 UTC

   We are continuing to investigate an issue where some customers in the EU region may experience delayed alert notifications. Data ingest is not impacted at this time.

4. identified 2024-12-06 01:35 UTC

   The issue has been identified and a fix is being implemented. Some customers in the EU region may experience delayed or missing alert notifications. Data ingest is not impacted at this time.

5. resolved 2024-12-06 02:19 UTC

   Between 22:51 UTC on Wednesday, December 5th and 02:16 UTC on December 6th, some customers in the EU region may have experienced delayed or missing alert notifications. Data processing for affected data may have been impacted. We have investigated and resolved this service...

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

Affected: APM : US

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 2024-12-05 09:38 UTC

   We are investigating a potential service interruption that may impact some customers. Please continue to monitor this page for updates.

2. investigating 2024-12-05 09:42 UTC

   We are investigating a potential service interruption that may impact some customers. Some customers may be experiencing issues with APM monitoring/tools not displaying data. Please continue to monitor this page for updates.

3. resolved 2024-12-05 10:38 UTC

   Between 07:20 UTC and 10:25 UTC on Dec 05, some customers may have experience issue with APM monitoring/tools not displaying data We have investigated and resolved this service interruption and impacted services have returned to normal operations.

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

Affected: Alerts : US

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 2024-12-02 23:00 UTC

   Some customers in the US region may experience issues creating or editing alert conditions through the New Relic UI or API. Data ingest and alert notifications are not impacted at this time. We are investigating and will continue to provide updates here as more information is...

2. resolved 2024-12-03 00:34 UTC

   Between 20:48 UTC and 22:34 UTC, some customers in the US region may have experienced issues creating or editing alert conditions through the New Relic UI or API. This issue has been resolved and impacted services have returned to normal operation. Data ingest and alert...

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

Affected: Alerts : US

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 2024-11-08 15:49 UTC

   We are investigating a potential service interruption that may impact some customers. Please continue to monitor this page for updates.

2. investigating 2024-11-08 15:53 UTC

   We are continuing to investigate this issue.

3. resolved 2024-11-08 16:25 UTC

   Between 13:56 UTC and 16:16 UTC on November 8th, some customers in the US region may have experienced a persistent error after visiting the ‘Destinations’ tab within the Alerts UI. Alert notifications were not impacted This issue has been resolved and impacted services have...

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

Affected: APM : Europe, Browser : Europe, Infrastructure : Europe, Logs : Europe, Mobile : Europe, Dashboards : Europe, NRQL : Europe, Serverless : Europe, Synthetics : Europe

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

1. investigating 2024-11-01 01:09 UTC

   Some customers in the EU region may be experiencing data visibility irregularities and delayed alert notifications for affected data. We are investigating this interruption and have escalated to our cloud provider.

2. investigating 2024-11-01 01:41 UTC

   We are continuing to investigate this interruption with our cloud provider.

3. identified 2024-11-01 02:09 UTC

   Our cloud provider has confirmed an interruption and is working to resolve the issue impacting New Relic services.

4. monitoring 2024-11-01 02:34 UTC

   We are seeing signs of recovery and will continue to monitor affected services.

5. resolved 2024-11-01 03:11 UTC

   Between 00:36 UTC and 02:35 UTC on November 1st, 2024, some customers in the EU region may have experienced data visibility irregularities and delayed alert notifications for affected data. The interruption with our cloud provider has been resolved and affected services have...

Excerpts are shortened. Read the full incident on New Relic'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 2024-10-31 07:15 UTC

   Between 07:03 UTC and 07:15 UTC on October 31st, some customers in the US region may have experienced delayed or missing alert notifications. This issue has been resolved and impacted services have returned to normal operations.

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