New Relic Outage History

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

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.

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

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

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.

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