Platform status
Updated by our team as incidents happen. Machine-readable at /api/status.
Regions
- St. Louis, USOperational
- New York area (Carlstadt), USOperational
- European UnionOperational
- Portsmouth, GBOperational
- Tokyo, JPOperational
- Navi Mumbai, INOperational
- Kansas (Lenexa), USOperational
- Boston, USOperational
- Phoenix, USOperational
- Atlanta, USOperational
- Chicago, USOperational
- Dallas, USOperational
- Fremont, USOperational
- Los Angeles, USOperational
- Miami, USOperational
- Newark, USOperational
- Seattle, USOperational
- Toronto, CAOperational
- Washington 2, USOperational
- Washington, USOperational
- Chennai, INOperational
- Jakarta, IDOperational
- Mumbai 2, INOperational
- Mumbai, INOperational
- Osaka, JPOperational
- Singapore 2, SGOperational
- Singapore, SGOperational
- Tokyo 2, JPOperational
- Tokyo 3, JPOperational
- Amsterdam, NLOperational
- Frankfurt 2, DEOperational
- Frankfurt, DEOperational
- London 2, GBOperational
- London, GBOperational
- Madrid, ESOperational
- Milan, ITOperational
- Paris 2, FROperational
- Paris, FROperational
- Stockholm, SEOperational
- Melbourne, AUOperational
- Sydney, AUOperational
- Sao Paulo, BROperational
- United StatesOperational
- United KingdomOperational
- FranceOperational
- GermanyOperational
- LithuaniaOperational
- BrazilOperational
- IndiaOperational
- IndonesiaOperational
- MalaysiaOperational
- SpainOperational
Active incidents
No active incidents.
Planned maintenance
No maintenance scheduled. Customers with a server in an affected region are emailed ahead of any planned work.
Past 30 days
Routine platform maintenance
CompletedAll regions · 12 Oct 2026, 13:00 to 12 Oct 2026, 14:00 UTC · completed 13 Oct 2026, 20:57 UTC
No customer server downtime expected.
Get status updates by email
One email when an incident opens and one when it resolves, and notice of planned maintenance. Confirm from your inbox first; every email has an unsubscribe link. Customers with a server in an affected region are told automatically and do not need this.
We publish incidents rather than an uptime percentage until we have enough operating history for the number to mean something. Something wrong that is not listed here? Tell us.