Where does this status come from?

From Modal's own status page API at https://status.modal.com. UpButler reads it once for everyone (not once per visitor) every 300 seconds with conditional requests, and shows it unchanged: incident titles and component names are Modal's words.

How can my agent or app check Modal status?

Fetch https://upbutler.com/status/modal/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"modal"}, on https://upbutler.com/mcp/public.

How do I know whether an outage is mine or Modal's?

Add "modal" to the dependencies of your UpButler workspace. When one of your monitors fails while Modal has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Is Modal down?

Right now

No. Modal is operational.

No incidents reported.

Read from status.modal.com 8 s ago · every 300s

For agents

proceed

Proceed.

GET upbutler.com/status/modal/status.agent.json

MCP: upstream_status {"service":"modal"}

Serverless GPUs and sandboxes for model inference and batch jobs.

What Modal reports

Operational

Taken as is from Modal's own status page API. Incident titles and component names below are theirs.

Open status.modal.com

UpButler's independent probe

There is no keyless endpoint of Modal that says anything useful, so UpButler does not probe it. To check your own Modal account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

Modal components

13 operational

Applications

DeploymentOperational
FunctionsOperational
SandboxesOperational
Web FunctionsOperational
ServersOperational

Web services

DashboardOperational

Storage

VolumesOperational
DictsOperational
QueuesOperational
SecretsOperational

Endpoints

Dedicated EndpointsOperational
Kimi K3 Shared EndpointOperational
Inkling Shared EndpointOperational

Modal incidents, last 90 days

1 finished incident seen since UpButler started tracking on 2026-10-10.

Started (UTC)	Incident	Impact	Lasted
2026-10-05 23:02	Function and Sandbox execution degraded	minor	7 min

Tell your outage from Modal's

Declare that your project depends on Modal. When one of your monitors fails while Modal has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start free How it works

upbutler.yaml

# upbutler.yaml
dependencies:
  - modal

Ask before you retry

curl -s https://upbutler.com/status/modal/status.agent.json

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "modal",
  "verdict": "proceed",
  "status": "operational",
  "reason": "No incidents reported",
  "retryAfterSec": null,
  "incident": null,
  "probe": null
}

Questions

Is Modal down right now?: No. As of 2026-10-10 05:11 UTC, Modal is operational. This page reads the status again every 5 minutes.
Where does this status come from?: From Modal's own status page API at https://status.modal.com. UpButler reads it once for everyone (not once per visitor) every 300 seconds with conditional requests, and shows it unchanged: incident titles and component names are Modal's words.
How can my agent or app check Modal status?: Fetch https://upbutler.com/status/modal/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"modal"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Modal's?: Add "modal" to the dependencies of your UpButler workspace. When one of your monitors fails while Modal has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

More in hosting and compute

UpButler is not affiliated with Modal. Status and incident text belong to Modal and are read from their public status source; the probe result is UpButler's own measurement.