Previous incidents
Database I/O load
Resolved Apr 22, 2024 at 3:41pm UTC
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 7, 2024 at 6:52pm UTC
GPU functions on OCI recovered.
1 previous update
False alerts for downtime
Resolved Apr 7, 2024 at 4:50pm UTC
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, 2024 at 12:55pm UTC
GPU functions on GCP recovered.
1 previous update
CPU functions on GCP is down
Resolved Mar 21, 2024 at 11:45pm UTC
CPU functions on GCP recovered.
3 previous updates
GPU functions on GCP is down
Resolved Mar 20, 2024 at 12:05pm UTC
GPU functions on GCP recovered.
3 previous updates
CPU functions on GCP is down
Resolved Mar 15, 2024 at 12:56pm UTC
CPU functions on GCP recovered.
1 previous update
Web endpoints is down
Resolved Mar 7, 2024 at 4:02am UTC
Web endpoints recovered.
1 previous update
GPU functions on GCP is down
Resolved Mar 5, 2024 at 12:15pm UTC
GPU functions on GCP recovered.
1 previous update
GPU functions on OCI is down
Resolved Mar 4, 2024 at 9:05pm UTC
GPU functions on OCI recovered.
3 previous updates
GPU functions on GCP is down
Resolved Mar 1, 2024 at 12:24pm UTC
GPU functions on GCP recovered.
1 previous update
Web endpoints is down
Resolved Feb 27, 2024 at 12:39am UTC
Web endpoints recovered.
1 previous update
GPU functions on OCI is down
Resolved Feb 26, 2024 at 11:37am UTC
GPU functions on OCI recovered.
1 previous update
GPU functions on OCI is down
Resolved Feb 20, 2024 at 5:45pm UTC
GPU functions on OCI recovered.
3 previous updates
GPU functions on OCI is down
Resolved Feb 18, 2024 at 3:57pm UTC
GPU functions on OCI recovered.
1 previous update
DNS issues causing website downtime and degradation of the service
Resolved Feb 14, 2024 at 12:20pm UTC
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).