Is Auth0 down?
Right now
We cannot tell from here. Auth0 publishes no status we can read.
No machine-readable official status; see their status page.
No official machine-readable status
For agents
proceed
Proceed.
GET upbutler.com/status/auth0/status.agent.json
MCP: upstream_status {"service":"auth0"}
Hosted login and identity. Status is per region and environment on its own page.
What Auth0 reports
status.auth0.com has no public JSON API or feed (a script-rendered page only), and tenants live on per-customer hosts, so there is nothing to probe without a key.
Their status page: status.auth0.comUpButler's independent probe
There is no keyless endpoint of Auth0 that says anything useful, so UpButler does not probe it. To check your own Auth0 account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.
Auth0 incidents, last 90 days
Without a machine-readable source there is no incident history to show. Auth0 keeps its own at status.auth0.com.
Tell your outage from Auth0's
Declare that your project depends on Auth0. When one of your monitors fails while Auth0 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.
# upbutler.yaml
dependencies:
- auth0curl -s https://upbutler.com/status/auth0/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "auth0",
"verdict": "proceed",
"status": "unknown",
"reason": "No machine-readable official status; see their status page",
"retryAfterSec": null,
"incident": null,
"probe": null
}Questions
- Is Auth0 down right now?
- We cannot tell. status.auth0.com has no public JSON API or feed (a script-rendered page only), and tenants live on per-customer hosts, so there is nothing to probe without a key. Their own status page is at https://status.auth0.com.
- Where does this status come from?
- status.auth0.com has no public JSON API or feed (a script-rendered page only), and tenants live on per-customer hosts, so there is nothing to probe without a key.
- How can my agent or app check Auth0 status?
- Fetch https://upbutler.com/status/auth0/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":"auth0"}, on https://upbutler.com/mcp/public.
- How do I know whether an outage is mine or Auth0's?
- Add "auth0" to the dependencies of your UpButler workspace. When one of your monitors fails while Auth0 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 authentication
UpButler is not affiliated with Auth0. Status and incident text belong to Auth0 and are read from their public status source; the probe result is UpButler's own measurement.