Previous incidents
Increased database errors
Resolved Jul 27, 2026 at 9:10am UTC
We’ve identified the issue and resolved it fully. Services have returned to normal, and our team will continue the investigation to prevent root cause in the future.
1 previous update
Investigating - DNS Resolution Errors Affecting Custom Domains
Resolved Jul 22, 2026 at 6:59am UTC
We have identified the root cause of the DNS resolution errors affecting custom domains and have deployed a patch that restores service. Custom domains are now operating normally.
Our team will continue to monitor the platform closely while we work on a permanent fix to fully address the underlying issue and prevent it from recurring.
Thank you for your patience while we resolved this incident.
1 previous update
Elevated errors on Functions & Sites in NYC
Resolved Jun 17, 2026 at 5:41pm UTC
We've identified the issue and have observed recovery. Please reach out to support if you encounter further issues.
1 previous update
Elevated errors on FRA region
Resolved Jun 11, 2026 at 4:06pm UTC
All services are fully available for all customers. Our team will share an incident report in the the next few days with actions items we will take to prevent such incidents happening again. Thank you for you support and patience.
2 previous updates
Elevated errors on NYC region
Resolved May 20, 2026 at 1:48am UTC
Our upstream cloud infrastructure vendor has confirmed that the issue has been resolved. From our side, we can confirm that all affected services are now fully operational and available again.
We will continue working closely with the vendor to complete a full investigation into the incident, better understand the root cause, and identify additional measures that can help prevent similar issues in the future. We appreciate everyone’s patience while this incident was being addressed.
3 previous updates
Elevated build and functions errors
Resolved May 10, 2026 at 7:29pm UTC
Our engineering team identified an issue with the components responsible for downsizing cluster capacity in our FRA edge location. This issue prevented new runtimes from being created, but did not affect existing workloads.
We have disabled the affected component, and runtime creation success rates are now back to 100% in this location. Service should be stable now.
We’re starting a follow-up investigation to identify the root cause and address it properly. Once ready, we’ll share the incid...