United States - Notification Service - Degraded
Final update
## Customer impact Between November 13, 2026 at approximately 2:00 pm UTC and November 14, 2026 at 6:09 pm UTC, customers in the US region experienced delayed in-app and email notifications. - Between 7:00 pm UTC on November 13 and 9:40 am UTC on November 14, some requests to send new notifications were slow or failed. - Delayed notifications were delivered once service was restored, so some customers received notifications several hours after the original event. ## Root cause - On November 13, 2026 at 1:31 pm UTC, a configuration change reduced the baseline processing capacity of the notification service. - The service's automatic scaling did not respond to the growing number of pending notifications, so a backlog built up. - Notifications that could not be processed in time accumulated until the service reached its storage limit at about 7:00 pm UTC. After that, new notifications could not be accepted. ## Detection Notification delays began on November 13, 2026 at approximately 2:00 pm UTC. The issue was identified internally on November 14, 2026 at 6:49 am UTC. Existing alerting did not cover growth in pending notifications or notification delays. ## Response - We increased the
Timeline
- Postmortem · Nov 20, 14:53 UTC
## Customer impact Between November 13, 2026 at approximately 2:00 pm UTC and November 14, 2026 at 6:09 pm UTC, customers in the US region experienced delayed in-app and email notifications. - Between 7:00 pm UTC on November 13 and 9:40 am UTC on November 14, some requests to send new notifications were slow or failed. - Delayed notifications were delivered once service was restored, so some customers received notifications several hours after the original event. ## Root cause - On November 13, 2026 at 1:31 pm UTC, a configuration change reduced the baseline processing capacity of the notification service. - The service's automatic scaling did not respond to the growing number of pending notifications, so a backlog built up. - Notifications that could not be processed in time accumulated until the service reached its storage limit at about 7:00 pm UTC. After that, new notifications could not be accepted. ## Detection Notification delays began on November 13, 2026 at approximately 2:00 pm UTC. The issue was identified internally on November 14, 2026 at 6:49 am UTC. Existing alerting did not cover growth in pending notifications or notification delays. ## Response - We increased the notification service's processing and storage capacity. Real-time notification delivery was restored on November 14, 2026 at approximately 9:40 am UTC. - From 3:01 pm UTC on November 14, 2026, we reprocessed the delayed notifications. All delayed notifications were processed by 6:09 pm UTC on Novemb
- Resolved · Nov 14, 18:41 UTC
All notifications that were delayed in the United States region have now been delivered, and Notification Service is operating normally. No action is needed from customers. We apologize for the disruption.
- Identified · Nov 14, 14:01 UTC
Notification Service performance in the United States region has been restored. We are working on delivering the notifications that were delayed.
- Identified · Nov 14, 13:04 UTC
Notification Service performance in the United States region has been restored. We are working on delivering the notifications that were delayed.
- Identified · Nov 14, 12:01 UTC
Notification Service performance in the United States region has been restored. We are working on delivering the notifications that were delayed.
- Identified · Nov 14, 11:49 UTC
We have identified the cause of the degraded Notification Service performance in the United States region and are working on a fix.
- Identified · Nov 14, 10:33 UTC
We have identified the cause of the degraded Notification Service performance in the United States region and are working on a fix.