PagerTree incident

Degraded Performance and Intermittent Errors to 3rd party notification services.

Minor Resolved View vendor source →

PagerTree experienced a minor incident on October 20, 2025, lasting 188d 12h. The incident has been resolved; the full update timeline is below.

Started
Oct 20, 2025, 10:50 AM UTC
Resolved
Apr 26, 2026, 11:25 PM UTC
Duration
188d 12h
Detected by Pingoru
Oct 20, 2025, 10:50 AM UTC

Update timeline

  1. monitoring Oct 20, 2025, 10:50 AM UTC

    2025-10-21 12:24:05 UTC Operational [ Resolved ] 2025-10-20 13:14:25 UTC Operational [ Monitoring ] We continue to monitor the multi service outage. At this moment, most services have recovered. https://health.aws.amazon.com/health/status https://status.twilio.com/incidents/2mjg0mr2pf29 https://status.flyio.net/ 2025-10-20 11:08:31 UTC Degraded performance [ Monitoring ] We are also seeing some errors in upstream providers for many services (Twilio, OneSignal) due to an upstream AWS outage. You might see notifications like SMS, Voice, and Push are delayed or are in the error state. https://status.twilio.com/incidents/2mjg0mr2pf29 https://health.aws.amazon.com/health/status 2025-10-20 10:55:52 UTC Degraded performance [ Monitoring ] We are continuing to monitor the incident with the upstream provider. The majority of the intermittent connectivity loss could be seen between 10/19 23:30 and 10/20 02:20 2025-10-20 07:20:00 UTC Degraded performance [ Identified ] Our PaaS provider is experiencing IPv6 connectivity issues (due to a faulty network switch), which can cause problems while connecting to the PagerTree services. https://status.flyio.net/ 2025-10-20 06:30:00 UTC Problem detected [ Identified ]