rewindex

CompaniesNew RelicIncidents

New Relic: Synthetics Ping Monitor Processing Delays in Multiple Regions

MinorStatus: resolvededitedStarted Resolved (1.8 h)4 updatesstatus.newrelic.com (opens in new tab)

Affected components: Alert Notifications : Europe - Synthetics : EuropeData Ingest : Europe - Synthetics : EuropeSynthetics : EuropeSynthetics : Europe

Timeline of updates

  1. investigating

    We are currently investigating processing delays affecting Synthetic ping monitors across several regions (ap-south-1, ca-central-1, us-east-1, eu-north-1, eu-south-1, and eu-west-3).
    As a result, users may experience dropped or delayed ping monitor execution and an overall decrease in Synthetic throughput in these specific locations. Other synthetic monitor types (scripted, browser) remain unaffected at this time.
    We will provide an update as soon as more details become available.

  2. investigating

    Our engineering teams continue to actively investigate the processing delays affecting Synthetic ping monitors in ap-south-1, ca-central-1, us-east-1, eu-north-1, eu-south-1, and eu-west-3.

  3. monitoring

    Synthetic ping monitor processing has normalized and throughput has returned to baseline levels across all affected regions (ap-south-1, ca-central-1, us-east-1, eu-north-1, eu-south-1, and eu-west-3). Our teams are actively monitoring the environment to verify sustained stability. We will provide another update once performance remains consistent.

  4. resolved

    Queue processing for Synthetic ping monitors has normalized across all affected locations, and throughput metrics have returned to baseline. Systems remain stable and the service is operating normally.

Changes Rewindex caught on this incident

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

Rewindex captured this after the last checkpoint; the next run () commits it.

Impact, status and times are the vendor’s own, as last archived. View on status.newrelic.com (opens in new tab).

New Relic profileRecent New Relic incidentsMarkdownJSON