Proactive Testing Window for Upcoming Root Certificate Update - March 12th at 00:00 UTC

Update timeline

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