PagerTree experienced a minor incident on May 16, 2025, lasting 345d 9h. The incident has been resolved; the full update timeline is below.
Update timeline
- monitoring May 16, 2025, 02:06 PM UTC
2025-05-16 15:22:22 UTC Operational [ Resolved ] The root cause of this issue was CPU throttling by our PaaS provider. We changed CPU configurations to prevent this in the future. 2025-05-16 14:47:10 UTC Operational [ Monitoring ] We have identified the root cause of the backup. (CPU Saturation) During the incident, critical queues were only slower than normal. Alert processing and notification delivery were delayed up to 15 minutes, but nevertheless delivered. Our search queue was backed up to 100 minutes. 2025-05-16 14:06:13 UTC Problem detected [ Investigating ] Inbound Queue Processing has been backed up since 12:45 UTC. We are investigating...