rewindex

CompaniesPingdomIncidents

Pingdom: Emergency Changes to the Pingdom Public API

MinorStatus: resolvedStarted Resolved (1.0 h)1 updatestatus.pingdom.com (opens in new tab)

CVEs mentioned

Only CVEs the vendor’s text names by id, or that its notice says it is not affected by. A mention is not a statement that the vulnerability caused this incident.

Timeline of updates

  1. resolved

    As part of our emergency mitigation for the recently discovered PHP vulnerabilities (CVE-2026-109618 and CVE-2026-109619), the Pingdom API now requires requests to include a User-Agent header. Please update your integration to include a descriptive value, such as:

    User-Agent: MyCompany-PingdomIntegration/1.0 (Replace MyCompany with your company name or the name/use of your integration)

    We apologize that we were unable to communicate this change in advance. Please contact us if you have any questions, issues, or concerns.

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. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

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

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

Pingdom profileRecent Pingdom incidentsMarkdownJSON