Historial de interrupciones de New Relic

1. August 3, 2026 at 9:58 AM UTCinvestigating

   Estamos investigando un problema donde algunos clientes de las regiones de la UE y EE.UU. pueden experimentar retrasos o errores al ver las alertas y la página de actividad.

2. August 3, 2026 at 10:15 AM UTCresolved

   Entre las 08:13 y las 9:30 UTC el 3 de agosto, los clientes de la UE y las regiones de Estados Unidos pueden haber experimentado un problema al intentar cargar la página Alertas y Problemas en la Nueva UI Reliquia. La cuestión se resuelve ahora y los servicios afectados han regresado al servicio normal. Por favor, cierre y vuelva a abrir la página Alertas para resolver el problema.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 17, 2026 at 10:21 AM UTCresolved

   Entre las 15:00 UTC los días 14 y 10 de julio UTC el 17 de julio, experimentamos un problema en el que algunos clientes experimentaron problemas de autorización al intentar crear, leer o actualizar reglas E2M (Events-2-Metrics) en las regiones de EE.UU., UE y JP. Esto se debió a un cambio reciente que hemos hecho a nuestros puntos finales de autorización. Estos endpoints requieren ahora la autenticación S2S que ha causado a nuestro E2M (Events-2-Metrics) fracasar. Nuestros equipos han retrocedido estos cambios hasta que se pueda establecer una solución permanente. La cuestión se resuelve ahora y los servicios afectados han regresado al servicio normal.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 6, 2026 at 8:23 AM UTCresolved

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

1. May 18, 2026 at 4:25 PM UTCresolved

   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 party cloud provider. The cloud provider resolved the service interruption and impacted services have returned to normal operations.

1. May 15, 2026 at 12:06 AM UTCinvestigating

   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 missing alert notifications for related data. 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. May 15, 2026 at 12:42 AM UTCinvestigating

   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, Alerts were not impacted. 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.

3. May 15, 2026 at 1:16 AM UTCmonitoring

   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 data in queries, charts, and dashboards. Data ingest and alerts were not impacted.

4. May 15, 2026 at 1:45 AM UTCresolved

   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 alerts were not impacted. We resolved this issue and the above services have returned to normal operation.

1. April 13, 2026 at 12:55 PM UTCinvestigating

   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. April 13, 2026 at 1:58 PM UTCinvestigating

   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 ingest and alert notifications are not impacted by this interruption.

3. April 13, 2026 at 2:41 PM UTCinvestigating

   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 more information to share, or by 3:30 PM UTC.

4. April 13, 2026 at 3:17 PM UTCresolved

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

1. April 9, 2026 at 9:51 AM UTCinvestigating

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

2. April 9, 2026 at 12:28 PM UTCidentified

   We have identified the issue and working on a solution

3. April 9, 2026 at 2:05 PM UTCmonitoring

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

4. April 9, 2026 at 4:48 PM UTCmonitoring

   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 interruption and impacted services have returned to normal operations.

5. April 9, 2026 at 8:46 PM UTCresolved

   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 interruption and impacted services have returned to normal operations.

1. March 24, 2026 at 5:22 AM UTCinvestigating

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

2. March 24, 2026 at 6:02 AM UTCinvestigating

   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. March 24, 2026 at 10:31 AM UTCresolved

   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 have returned to normal operations.

1. March 20, 2026 at 3:53 PM UTCinvestigating

   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 data may not be recoverable.

2. March 20, 2026 at 3:59 PM UTCinvestigating

   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. Impacted data may not be recoverable.

3. March 20, 2026 at 4:10 PM UTCresolved

   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 time, and delayed or missing alert notifications related to real time data. Impacted data may not be recoverable.

1. March 3, 2026 at 12:21 AM UTCinvestigating

   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. March 3, 2026 at 12:36 AM UTCinvestigating

   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.

3. March 3, 2026 at 1:02 AM UTCinvestigating

   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 provide updates until services are restored to normal operations.

4. March 3, 2026 at 2:28 AM UTCmonitoring

   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 services return to normal operations.

5. March 3, 2026 at 2:59 AM UTCresolved

   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 notifications for impacted data.

1. March 2, 2026 at 7:06 AM UTCinvestigating

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

2. March 2, 2026 at 7:35 AM UTCinvestigating

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

3. March 2, 2026 at 9:42 AM UTCresolved

   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

1. February 18, 2026 at 10:06 AM UTCresolved

   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.

1. February 5, 2026 at 4:20 PM UTCinvestigating

   We are currently investigating an issue causing errors with Distributed Tracing

2. February 5, 2026 at 4:40 PM UTCmonitoring

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

3. February 5, 2026 at 5:22 PM UTCresolved

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

1. January 21, 2026 at 10:23 PM UTCinvestigating

   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. January 21, 2026 at 10:53 PM UTCinvestigating

   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. January 22, 2026 at 12:00 AM UTCidentified

   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. January 22, 2026 at 12:46 AM UTCresolved

   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 including delayed alert notifications.

1. January 12, 2026 at 3:21 PM UTCinvestigating

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

2. January 12, 2026 at 3:22 PM UTCinvestigating

   We are continuing to investigate this issue.

3. January 12, 2026 at 3:53 PM UTCinvestigating

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

4. January 12, 2026 at 5:36 PM UTCidentified

   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 updates until services have been restored to normal operation.

5. January 12, 2026 at 6:10 PM UTCresolved

   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, restoring affected query performance at 17:29 UTC. Separately, a subset of customers in the US and EU regions may have experienced errors when sending data to New Relic. This interruption could have resulted in potential data drops for data sent during this timeframe, depending on client-side retry settings, and may have generated false alert notifications regarding host reporting status. This interruption appears related to a disruption with a New Relic third-party edge service provider. To remediate, our teams have shifted traffic to an alternate cloud provider and have seen recovery of impacted services.

1. December 18, 2025 at 11:30 PM UTCinvestigating

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

2. December 18, 2025 at 11:52 PM UTCinvestigating

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

3. December 19, 2025 at 1:00 AM UTCinvestigating

   We are continuing to investigate this issue.

4. December 19, 2025 at 1:56 AM UTCmonitoring

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

5. December 19, 2025 at 2:21 AM UTCresolved

   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 returned to normal operations.

1. November 19, 2025 at 11:48 AM UTCinvestigating

   We are investigating an issue with data ingest

2. November 19, 2025 at 12:16 PM UTCidentified

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

3. November 19, 2025 at 12:34 PM UTCmonitoring

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

4. November 19, 2025 at 12:52 PM UTCresolved

   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

1. November 18, 2025 at 12:34 PM UTCinvestigating

   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. November 18, 2025 at 2:15 PM UTCidentified

   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, please reach out to our Support team through this form: https:support.newrelic.comscontact-new-relic-support-form.

3. November 18, 2025 at 3:23 PM UTCmonitoring

   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 access In-App support, please reach out to our Support team through this form: https:support.newrelic.comscontact-new-relic-support-form.

4. November 18, 2025 at 8:19 PM UTCresolved

   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.

1. October 20, 2025 at 8:45 AM UTCidentified

   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. October 20, 2025 at 9:14 AM UTCidentified

   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

3. October 20, 2025 at 11:56 AM UTCmonitoring

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

4. October 20, 2025 at 12:13 PM UTCmonitoring

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

5. October 20, 2025 at 5:54 PM UTCmonitoring

   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 symbolication and crash events, and entity relationships. We will provide our next update at 20:00 UTC or upon significant change.

6. October 20, 2025 at 7:57 PM UTCmonitoring

   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.

7. October 20, 2025 at 9:33 PM UTCresolved

   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, data availability may differ depending on the configuration of each customer environment and their dependency on affected cloud provider services.

1. October 10, 2025 at 4:00 PM UTCinvestigating

   We are continuing to investigate this issue.

2. October 10, 2025 at 4:01 PM UTCinvestigating

   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 returned to normal operation. To prevent our customers from receiving a high volume of false positive alert notifications, we have temporarily suppressed notifications for affected data.

3. October 10, 2025 at 4:43 PM UTCidentified

   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, and will provide an update when our services have returned to normal operation. To prevent our customers from receiving a high volume of false positive alert notifications, we have temporarily suppressed notifications for affected data.

4. October 10, 2025 at 5:02 PM UTCidentified

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

5. October 10, 2025 at 5:03 PM UTCidentified

   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 until our services have returned to normal operation.

6. October 10, 2025 at 5:56 PM UTCidentified

   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 Monitoring data for queries, charts, and dashboards as well as delayed or missing alert notifications for related data. We will provide an update when our services have returned to normal operation.

7. October 10, 2025 at 6:46 PM UTCidentified

   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 updates until our services have returned to normal operation.

8. October 10, 2025 at 8:12 PM UTCresolved

   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 this interruption and services have returned to normal operations.