Pearch incident
API partial outages — historical monitoring correction (8–14 September)
Resolved on September 14, 2026.
Retrospective correction based on scheduled fast end-to-end API checks from 8–14 September 2026. Downtime is counted only for segments with at least two consecutive failed checks, five minutes apart. Each failure within a qualifying segment contributes five minutes; isolated failures and gaps are excluded. This yields seven partial-outage periods totaling 90 minutes. GCP checks are used through 12 September and Azure checks from 13 September. These impact windows supersede the longer alert-lifetime downtime estimates for the same monitoring issues. All affected periods have ended.
Update timeline
- resolved Sep 14, 2026, 04:00 PM UTC
Retrospective correction based on scheduled fast end-to-end API checks from 8–14 September 2026. Downtime is counted only for segments with at least two consecutive failed checks, five minutes apart. Each failure within a qualifying segment contributes five minutes; isolated failures and gaps are excluded. This yields seven partial-outage periods totaling 90 minutes. GCP checks are used through 12 September and Azure checks from 13 September. These impact windows supersede the longer alert-lifetime downtime estimates for the same monitoring issues. All affected periods have ended.
Your product runs on more than Pearch
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services