Upstash incident
Region ap-northeast-1 outage on Upstash Global
Affected components
Update timeline
- investigating Mar 06, 2026, 01:50 PM UTC
We are currently investigating this issue.
- monitoring Mar 06, 2026, 02:08 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Mar 06, 2026, 02:49 PM UTC
This incident has been resolved.
- postmortem Mar 09, 2026, 10:07 AM UTC
On March 6, between approximately 13:44–14:07 UTC, some databases experienced elevated latency and connection errors in the Tokyo \(ap-northeast-1\) region. The issue was caused by a sudden spike in traffic that significantly increased network utilization and connection load on a subset of nodes. Our team mitigated the incident by scaling up capacity in the region and redistributing load across additional nodes. Service recovered once the additional capacity was brought online. Resolution We have increased the number of machines in the Tokyo region to provide additional headroom and reduce the likelihood of similar incidents during traffic spikes. Next Steps We are continuing to review capacity safeguards and connection-handling limits to improve resilience against sudden traffic surges.
Looking to track Upstash downtime and outages?
Pingoru polls Upstash's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when Upstash reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track Upstash alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required