All systems operational
Uptime for every region over the last thirty days, measured by nine independent probes. Incidents are posted here before the tickets arrive.
Regional uptime
Measured every thirty seconds from all nine regions. Planned maintenance is included in these figures.
| Region | Code | 30-day uptime | Status |
|---|---|---|---|
| United Kingdom | London | LON1 | 100.00% | Operational |
| USA | San Francisco | SFO1 | 99.99% | Operational |
| Brazil | São Paulo | GRU1 | 100.00% | Operational |
| South Africa | Johannesburg | JNB1 | 99.98% | Operational |
| India | Bangalore | BLR1 | 100.00% | Operational |
| Singapore | SIN1 | 100.00% | Operational |
| Japan | Tokyo | NRT1 | 99.99% | Operational |
| Australia | Sydney | SYD1 | 100.00% | Operational |
| Canada | Toronto | YYZ1 | 100.00% | Operational |
Changelog
Platform changes worth knowing about, newest first.
HTTP/3 enabled by default
All nine regions now negotiate HTTP/3 with QUIC on every certificate we issue. No action is needed; existing sites picked it up during the rolling restart.
Terraform provider 2.4
Adds firewall rules, floating IPs and per-site team permissions as first-class resources. The 1.x provider stays supported until January.
Backups extended to 30 days
Retention on all paid plans moved from 14 days to 30 at no extra cost, and restores no longer count against the storage quota.
São Paulo capacity doubled
GRU1 moved to a second hall in Barueri, taking regional capacity from 1.5 Tbps to 3 Tbps and adding a second IX.br peering session.
Slow query log in the panel
Queries over 500ms are now listed in the panel with their calling file, so you no longer need SSH to find the one that matters.
Seeing something we are not?
Open a ticket with a traceroute and we will look immediately. Contact support ›
How the SLA works
Credits are applied automatically when we miss the target. Read the detail ›