New Relic Outage History

Started Sep 25, 2026, 07:57 PM UTC· resolved Sep 25, 2026, 10:33 PM UTC

1. investigating Sep 25, 2026, 07:57 PM 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 Sep 25, 2026, 08:15 PM 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 suppressed.

3. investigating Sep 25, 2026, 08:39 PM 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 data. Affected alerts are currently being suppressed.

4. identified Sep 25, 2026, 09:27 PM 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. Alerts are no longer suppressed.

5. identified Sep 25, 2026, 10:18 PM 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 Sep 25, 2026, 10:33 PM 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 interruption and impacted services have returned to normal operations.

Read the full incident report →

Started Sep 25, 2026, 03:55 AM UTC· resolved Sep 25, 2026, 03:55 AM UTC

1. resolved Sep 25, 2026, 03:55 AM 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 have returned to normal operations.

Read the full incident report →

Started Sep 25, 2026, 02:23 AM UTC· resolved Sep 25, 2026, 06:43 AM UTC

1. investigating Sep 25, 2026, 02:23 AM UTC

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

Read the full incident report →

Started Sep 22, 2026, 08:55 AM UTC· resolved Sep 22, 2026, 08:55 AM UTC

1. investigating Sep 22, 2026, 08:55 AM UTC

   Test message - after fix

2. resolved Sep 22, 2026, 08:55 AM UTC

   Test message -resolved

Read the full incident report →

Started Sep 16, 2026, 10:08 AM UTC· resolved Sep 16, 2026, 03:40 PM UTC

1. monitoring Sep 16, 2026, 10:08 AM 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 Sep 16, 2026, 03:40 PM UTC

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

Read the full incident report →

Started Sep 16, 2026, 12:14 AM UTC· resolved Sep 16, 2026, 11:16 PM UTC

1. resolved Sep 16, 2026, 12:14 AM 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 may not be recoverable.

Read the full incident report →

Started Aug 03, 2026, 09:58 AM UTC· resolved Aug 03, 2026, 10:15 AM UTC

1. investigating Aug 03, 2026, 09:58 AM 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 Aug 03, 2026, 10:15 AM 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 re-open the Alerts page to resolve the issue.

Read the full incident report →

Started Jul 17, 2026, 10:21 AM UTC· resolved Jul 18, 2026, 10:00 AM UTC

1. resolved Jul 17, 2026, 10:21 AM 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 made to our authorization endpoints. These endpoints now require S2S authentication which has caused requests to our E2M (Events-2-Metrics) to fail. Our teams have rolled back these changes until a permanent fix can be put in place. The issue is now resolved, and the impacted services have returned to normal service.

Read the full incident report →

Started Jul 06, 2026, 07:20 AM UTC· resolved Jul 06, 2026, 08:12 AM UTC

1. resolved Jul 06, 2026, 08:23 AM 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 normal service.

Read the full incident report →

Started May 18, 2026, 10:30 AM UTC· resolved May 18, 2026, 01:32 PM UTC

1. resolved May 18, 2026, 04:25 PM 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 party cloud provider. The cloud provider resolved the service interruption and impacted services have returned to normal operations.

Read the full incident report →

Started May 15, 2026, 12:06 AM UTC· resolved May 15, 2026, 01:45 AM UTC

1. investigating May 15, 2026, 12:06 AM 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 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. investigating May 15, 2026, 12:42 AM 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, 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. monitoring May 15, 2026, 01:16 AM 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 data in queries, charts, and dashboards. Data ingest and alerts were not impacted.

4. resolved May 15, 2026, 01:45 AM 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 alerts were not impacted. We resolved this issue and the above services have returned to normal operation.

Read the full incident report →

Started Apr 13, 2026, 12:44 PM UTC· resolved Apr 13, 2026, 03:17 PM UTC

1. investigating Apr 13, 2026, 12:44 PM 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 Apr 13, 2026, 12:49 PM 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 Apr 13, 2026, 12:55 PM 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 Apr 13, 2026, 01:58 PM 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 ingest and alert notifications are not impacted by this interruption.

5. investigating Apr 13, 2026, 02:41 PM 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 more information to share, or by 3:30 PM UTC.

6. resolved Apr 13, 2026, 03:17 PM 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 operations.

Read the full incident report →

Started Apr 09, 2026, 09:51 AM UTC· resolved Apr 09, 2026, 08:46 PM UTC

1. investigating Apr 09, 2026, 09:51 AM UTC

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

2. identified Apr 09, 2026, 12:28 PM UTC

   We have identified the issue and working on a solution

3. monitoring Apr 09, 2026, 02:05 PM UTC

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

4. monitoring Apr 09, 2026, 04:48 PM 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 interruption and impacted services have returned to normal operations.

5. resolved Apr 09, 2026, 08:46 PM 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 interruption and impacted services have returned to normal operations.

Read the full incident report →

Started Mar 24, 2026, 05:22 AM UTC· resolved Mar 24, 2026, 10:31 AM UTC

1. investigating Mar 24, 2026, 05:22 AM UTC

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

2. investigating Mar 24, 2026, 06:02 AM 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 Mar 24, 2026, 10:31 AM 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 have returned to normal operations.

Read the full incident report →

Started Mar 20, 2026, 03:52 PM UTC· resolved Mar 20, 2026, 04:10 PM UTC

1. investigating Mar 20, 2026, 03:52 PM 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 data may not be recoverable.

2. investigating Mar 20, 2026, 03:53 PM 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 data may not be recoverable.

3. investigating Mar 20, 2026, 03:59 PM 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. Impacted data may not be recoverable.

4. resolved Mar 20, 2026, 04:10 PM 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 time, and delayed or missing alert notifications related to real time data. Impacted data may not be recoverable.

Read the full incident report →

Started Mar 18, 2026, 05:54 PM UTC· resolved Apr 09, 2026, 01:52 AM UTC

1. monitoring Apr 09, 2026, 01:52 AM UTC

   Apr 9, 01:52 UTC Completed - The scheduled maintenance has been completed and all relevant New Relic endpoints have been transitioned to the DigiCert Global Root G2 certificate. For further details, see https://support.newrelic.com/s/hubtopic/aAXPh000000HVSPOA4/action-required-root-certificate-update-on-april-1-2026. Apr 9, 01:12 UTC Verifying - The scheduled update to our digital security certificates (SSL) is now complete. We have successfully transitioned all relevant New Relic endpoints to the DigiCert Global Root G2 certificate. We are currently monitoring platform stability and will provide a final update once the window is officially closed. Apr 9, 00:00 UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Apr 1, 17:11 UTC Update - Permanent G2 Certificate Transition Postponed to April 09, 2026 To allow customers additional time to update legacy environments and avoid data drops, New Relic is postponing the permanent transition to the DigiCert Global Root G2 certificate by one week. The final cutover is now scheduled for 00:00 UTC on April 09, 2026. Please note: This is the final postponement. Because the industry-wide deadline for G1 distrust is April 15th, we cannot delay this change any further without risking a total service interruption for all New Relic customers. Systems not updated by April 9th will lose the ability to send telemetry data to New Relic. Any further updates will be posted on status.newrelic.com, as well as our forum: https://support.newrelic.com/s/hubtopic/aAXPh000000HVSPOA4/action-required-root-certificate-update-on-april-1-2026 Mar 18, 17:54 UTC Scheduled - On April 2nd at 00:00 UTC, New Relic will permanently transition to the DigiCert G2 root certificate for all endpoints. This aligns with an industry-wide security change. On April 15th, 2026, major browser trust stores and security authorities will officially distrust the legacy DigiCert G1 Root Certificate. To maintain its strong continued security posture, New Relic is updating its infrastructure to utilize modern root certificates prior to this deadline. Most modern systems and agents are designed to handle this change automatically. If your systems do not recognize and trust these newer root certificates when the update is applied, the secure handshake will fail and would result in a telemetry data drop, meaning your metrics, events, traces, and logs may stop reporting to the New Relic platform. This risk is primarily associated with legacy Java agents (older than v6.4.2), certain Docker images, and systems using pinned certificates. Any further updates will be posted on status.newrelic.com, as well as our forum: https://support.newrelic.com/s/hubtopic/aAXPh000000HVSPOA4/action-required-root-certificate-update-on-april-1-2026

Read the full incident report →

Started Mar 03, 2026, 04:28 PM UTC· resolved Mar 12, 2026, 02:21 AM UTC

1. monitoring Mar 12, 2026, 02:21 AM UTC

   Mar 12, 02:21 UTC Completed - We have concluded our proactive testing window. Please see our post for more details: https://support.newrelic.com/s/hubtopic/aAXPh000000HVSPOA4/action-required-root-certificate-update-on-april-1-2026 Mar 12, 00:28 UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Mar 3, 16:28 UTC Scheduled - On March 12th at 00:00 UTC, New Relic will initiate a proactive testing window where endpoints will temporarily transition to the DigiCert G2 root certificate. This event is designed to support customers in proactively identifying impacted systems ahead of the permanent root certificate update scheduled for April 2nd (UTC). This aligns with an industry-wide security change. On April 15th, 2026, major browser trust stores and security authorities will officially distrust the legacy DigiCert G1 Root Certificate. To maintain its strong continued security posture, New Relic is updating its infrastructure to utilize modern root certificates prior to this deadline. Most modern systems and agents are designed to handle this change automatically. If your systems do not recognize and trust these newer root certificates when the update is applied, the secure handshake will fail and would result in a telemetry data drop, meaning your metrics, events, traces, and logs may stop reporting to the New Relic platform. This risk is primarily associated with legacy Java agents (older than v6.4.2), certain Docker images, and systems using pinned certificates. Any further updates will be posted on status.newrelic.com, as well as our forum: https://support.newrelic.com/s/hubtopic/aAXPh000000HVSPOA4/action-required-root-certificate-update-on-april-1-2026

Read the full incident report →

Started Mar 03, 2026, 12:19 AM UTC· resolved Mar 03, 2026, 02:59 AM UTC

1. investigating Mar 03, 2026, 12:19 AM 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 Mar 03, 2026, 12:21 AM 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 Mar 03, 2026, 12:36 AM 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 Mar 03, 2026, 01:02 AM 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 provide updates until services are restored to normal operations.

5. monitoring Mar 03, 2026, 02:28 AM 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 services return to normal operations.

6. resolved Mar 03, 2026, 02:59 AM 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 notifications for impacted data.

Read the full incident report →

Started Mar 02, 2026, 07:06 AM UTC· resolved Mar 02, 2026, 09:42 AM UTC

1. investigating Mar 02, 2026, 07:06 AM UTC

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

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

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

3. resolved Mar 02, 2026, 09:42 AM 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

Read the full incident report →

Started Feb 18, 2026, 10:06 AM UTC· resolved Feb 18, 2026, 10:06 AM UTC

1. monitoring Feb 18, 2026, 10:06 AM UTC

   Feb 18, 10:06 UTC Resolved - 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.

Read the full incident report →

Started Feb 05, 2026, 04:20 PM UTC· resolved Feb 05, 2026, 05:22 PM UTC

1. investigating Feb 05, 2026, 04:20 PM UTC

   We are currently investigating an issue causing errors with Distributed Tracing

2. monitoring Feb 05, 2026, 04:40 PM UTC

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

3. resolved Feb 05, 2026, 05:22 PM UTC

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

Read the full incident report →

Started Jan 21, 2026, 10:23 PM UTC· resolved Jan 22, 2026, 12:46 AM UTC

1. investigating Jan 21, 2026, 10:23 PM 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 Jan 21, 2026, 10:53 PM 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 Jan 22, 2026, 12:00 AM 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 Jan 22, 2026, 12:46 AM 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 including delayed alert notifications.

Read the full incident report →

Started Jan 12, 2026, 03:21 PM UTC· resolved Jan 12, 2026, 06:10 PM UTC

1. investigating Jan 12, 2026, 03:21 PM UTC

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

2. investigating Jan 12, 2026, 03:22 PM UTC

   We are continuing to investigate this issue.

3. investigating Jan 12, 2026, 03:53 PM UTC

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

4. identified Jan 12, 2026, 05:36 PM 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 updates until services have been restored to normal operation.

5. resolved Jan 12, 2026, 06:10 PM 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, 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.

Read the full incident report →

Started Dec 18, 2025, 11:30 PM UTC· resolved Dec 19, 2025, 02:21 AM UTC

1. investigating Dec 18, 2025, 11:30 PM UTC

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

2. investigating Dec 18, 2025, 11:52 PM UTC

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

3. investigating Dec 19, 2025, 12:23 AM UTC

   We are continuing to investigate this issue.

4. investigating Dec 19, 2025, 01:00 AM UTC

   We are continuing to investigate this issue.

5. monitoring Dec 19, 2025, 01:56 AM UTC

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

6. resolved Dec 19, 2025, 02:21 AM 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 returned to normal operations.

Read the full incident report →

Started Nov 19, 2025, 11:48 AM UTC· resolved Nov 19, 2025, 12:52 PM UTC

1. investigating Nov 19, 2025, 11:48 AM UTC

   We are investigating an issue with data ingest

2. identified Nov 19, 2025, 12:16 PM UTC

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

3. monitoring Nov 19, 2025, 12:19 PM UTC

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

4. monitoring Nov 19, 2025, 12:34 PM UTC

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

5. resolved Nov 19, 2025, 12:52 PM 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

Read the full incident report →