Sandbox v1 scheduling degraded
We've remediated the issue and latency has recovered.
The latest update from Modal.
State
Resolved
Started
Lasted
10 min
Worst impact
Degraded
Timeline
2 updatesDegraded
10 min 100%
Updates
Times in UTCAs posted by Modal
We've remediated the issue and latency has recovered.
p90 latency is elevated for scheduling v1 sandboxes
Affected components
1Modal in the last 90 days
Full historyIncidents in 90 days
13
Days with an incident
11
Median duration
12 min
This incident
17% shorter than the median
Other Modal incidents
All incidentsModal·Datadog integrations disrupted
Modal Datadog metric and log forwarding for the Dashboard component is disrupted. Modal reports that the incident is resolved and that exports to the affected Datadog integrations are restored. The outage lasted 124 minutes.
Modal·Container startup was degraded
Modal had degraded startup of new containers. The problem affected Functions, Web Functions, Sandboxes, and Servers. Modal reports that the issue is resolved, and it lasted about 5 minutes.
Modal·Major outage
Modal reports a major outage that affects Volumes. Modal says that the outage is resolved. The outage lasted 12 minutes, from 08:27 to 08:39 UTC on 12 November 2026.
Modal·Some Sandboxes experiencing creation failures
Modal reports that some V2 Sandboxes failed to start for 24 minutes. Modal identified a change and rolled it back. The incident is resolved.
Modal·Major outage
Modal reports a major outage that affects Volumes. Modal says the outage is resolved. The outage lasted 33 minutes.
Follow Modal
Your coding agent knows when Modal is down, and tells you when a failure is theirs, not yours. You can also get Modal incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "modal" and tell me if Modal has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=modal/feed subscribe https://outages.live/feed.xml?providers=modalFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane