Previous incidents
Database I/O load
Resolved Apr 22 at 11:41am EDT
We have resolved the issue. Thank you for your patience!
We are continuing to monitor.
3 previous updates
GPU functions on OCI is down
Resolved Apr 07 at 02:52pm EDT
GPU functions on OCI recovered.
1 previous update
False alerts for downtime
Resolved Apr 07 at 12:50pm EDT
We hit a limit on our internal workspace used to run synthetic monitors, which caused our downtime alerts to fire inaccurately. We have raised the limits now.
No users were affected. We're sorry for all the spam for status page subscribers!
GPU functions on GCP is down
Resolved Mar 27 at 08:55am EDT
GPU functions on GCP recovered.
1 previous update
CPU functions on GCP is down
Resolved Mar 21 at 07:45pm EDT
CPU functions on GCP recovered.
3 previous updates
GPU functions on GCP is down
Resolved Mar 20 at 08:05am EDT
GPU functions on GCP recovered.
3 previous updates
CPU functions on GCP is down
Resolved Mar 15 at 08:56am EDT
CPU functions on GCP recovered.
1 previous update
Web endpoints is down
Resolved Mar 06 at 11:02pm EST
Web endpoints recovered.
1 previous update
GPU functions on GCP is down
Resolved Mar 05 at 07:15am EST
GPU functions on GCP recovered.
1 previous update
GPU functions on OCI is down
Resolved Mar 04 at 04:05pm EST
GPU functions on OCI recovered.
3 previous updates
GPU functions on GCP is down
Resolved Mar 01 at 07:24am EST
GPU functions on GCP recovered.
1 previous update
Web endpoints is down
Resolved Feb 26 at 07:39pm EST
Web endpoints recovered.
1 previous update
GPU functions on OCI is down
Resolved Feb 26 at 06:37am EST
GPU functions on OCI recovered.
1 previous update
GPU functions on OCI is down
Resolved Feb 20 at 12:45pm EST
GPU functions on OCI recovered.
3 previous updates
GPU functions on OCI is down
Resolved Feb 18 at 10:57am EST
GPU functions on OCI recovered.
1 previous update
DNS issues causing website downtime and degradation of the service
Resolved Feb 14 at 07:20am EST
We experienced a problem with our DNS records for modal.com and modal.run, meaning that the website and webpoints were unreachable for a period, unless DNS records were cached by your local resolver.
This also affected workloads running on modal to some degree, as some workloads were failing to communicate with our API server.
The issue has been resolved but there might be lingering effects due to negative DNS caches in your local DNS resolver (e.g. your ISP resolvers).