New Relic Status

Data Ingest : US Operational

Alert Notifications : US Operational

UI : US Operational

Data Ingest : Europe Operational

Alert Notifications : Europe Operational

UI : Europe Operational

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

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

Update - 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
Mar 24, 06:02 UTC

Investigating - Some customers in the US and EU regions may experience discrepancies in NRComputeusage and NRConsumption usage values
Mar 24, 05:22 UTC

Resolved - 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.
Mar 20, 16:10 UTC

Update - 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.
Mar 20, 15:59 UTC

Update - 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.
Mar 20, 15:53 UTC

Investigating - 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.
Mar 20, 15:52 UTC

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 12, 00: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