Skip to content
RELIASTRAObservatory
Monitor your dependencies

Public infrastructure observatoryRecord auth0

Auth0

Auth0 is observed by probing its public https://status.auth0.com from 1 observation region. RELIASTRA measures the HTTP behaviour of the listed endpoint - its state is not a statement about every service Auth0 operates.

Responding

The five most recent observations each received the expected response from this endpoint within its deadline.

Last observation15:41:09 UTC19 Sep 2026
Observation cadencemeasuring

Observations have been arriving about every 5.0m in this window. The bar advances against that interval.

Elapsed time since the last observation is being measured.
Last hour · us-east11 observations · 0 failed
−60 minnow

Is Auth0 down?

No sign of it right now: the five most recent RELIASTRA observations of status.auth0.com all received the expected response. This measures the endpoint, not all of Auth0 - the scope is stated below.

  • Latest observation: 19 Sep 2026 15:41:09 UTC - HTTP 200 in 149 ms from us-east.
  • Last 24 hours: 276 observations, availability 100.00%, mean response 195 ms. Checks arrive about every 300 seconds per region.

This record measures the HTTP behaviour of status.auth0.com - the endpoint RELIASTRA probes for Auth0. It is not a statement that every Auth0 service is operational, and an operational endpoint is not a statement about your own integration, your traffic path, or your API key.

Vendor-reported status is separate: RELIASTRA does not ingest, mirror or reconcile Auth0’s own status reporting, so the two records can legitimately disagree. Read both; only one of them is independent of Auth0.

measurement methodology

Category
auth
Observed endpoint
status.auth0.com
Observation regions
us-east
Measured by
RELIASTRA probes

Summary of this record

Auth0 is observed by RELIASTRA as an auth dependency under continuous observation. Requests are issued to https://status.auth0.com from us-east, about every 300 seconds per region. Each observation records the response latency, the HTTP status code or transport error, and a UTC timestamp. The last observation recorded was 19 Sep 2026 15:41:09 UTC.

Over the last 24 hours RELIASTRA recorded 276 observations, an availability of 100.00% and a mean response of 195 ms; over 30 days, 100.00%. RELIASTRA currently lists no public incident records for this dependency; that is an absence of published records, not proof that no outage occurred. Availability, latency and incident history on this page are measured by RELIASTRA probes, not reported by the vendor, and describe the observed endpoints rather than every service Auth0 operates.

Current observation

The most recent completed observation per region label. One request, one response, one timestamp.
1 region · region-scoped
us-eastEastern United States
Responded
Latency
149ms
Status
200
Observed (UTC)
19 Sep 15:41:09

These observations come from a single observation point, so they can show that the endpoint answered or did not - they cannot corroborate a vendor-wide outage. A region reporting no response is a fact about this path, at this minute.

Observed state and availability

An observation counts as successful when the probe received the response its target expects - for these public records, HTTP 200 within a 15-second deadline. Timeouts, transport errors and other status codes count as failures. No observations reads as insufficient data, never 100%.
RespondingLast check 19 Sep 2026 15:41:09 UTC1 region observed
1 hour
100.00%
Observations
11
Mean latency
163ms
95th percentile
198ms
6 hours
100.00%
Observations
68
Mean latency
181ms
95th percentile
395ms
24 hours
100.00%
Observations
276
Mean latency
195ms
95th percentile
411ms
7 days
100.00%
Observations
1,925
Mean latency
195ms
95th percentile
411ms
30 days
100.00%
Observations
2,617
Mean latency
200ms
95th percentile
422ms
90 days
100.00%
Observations
2,617
Mean latency
200ms
95th percentile
422ms

Every window is computed by the measurement API over stored observations at read time. Latency figures are milliseconds; a mean of zero means no successful response was recorded in the window and is printed as no data.

Historical telemetry

Every point is the mean latency of the observations inside one bucket, at the resolution the measurement API aggregates to for the selected range. Failed buckets break the line; incident windows are shaded. Ranges are limited to the windows the API can aggregate.
Range

Initialising observation series…

Requesting aggregated observations from the measurement API. No values are shown until they arrive.

Viewing 7 days from us-east. Other ranges: 24 hours, 30 days, 90 days.

Observation network

The observation regions scheduled for this dependency, and the interval actually observed per region label. With one observation point deployed, a region label names the worker that ran the probe rather than a second vantage point.
us-east
149ms
Observed cadence
300s

Cadence is estimated from the spacing of observations in the last hour, not read from a configured schedule: the public API does not expose the check interval, so this record reports the interval it can verify. An interval longer than the chart resolution is read from the gap between observations, not from their density.

Observed incidents

Public incident records for Auth0 are published when the account holding the monitoring releases an evidence record. The public probing pipeline itself stores endpoint observations; it does not open incident records, and this record is observed from a single observation point, so an empty list here is a statement about the public incident channel - never a claim that no outage occurred.
0 recordsPublished evidence: rolling 90 days

No public incident records

RELIASTRA holds no public incident record for Auth0 in the rolling 90-day published-evidence window. That is an absence of published records, not evidence of an absence of outages: endpoint-level failures that did not produce a released evidence report never enter this channel. Use the observations above for what was measured.

Evidence records

The checksummed artifact behind an incident: the observations, the detection record, the attribution result and their timestamps. Released to a named requester, not an open link.
What an evidence record contains

No published evidence for this dependency

Evidence records appear here when an organization monitoring auth0 on RELIASTRA publishes the report for an incident. Until then the incident history above is the public record, and the underlying observations remain in the accounts that collected them.

How evidence is used in an SLA claim

How RELIASTRA knows this

What is measured, and what is not.
Full methodology
Source
Scheduled workers issue real HTTP requests to the endpoints listed at the bottom of this record, from us-east. Where a listed endpoint is Auth0's public status site, the probe measures that site's own availability and response time as an HTTP service; the status text it publishes is not read, parsed, ingested or reconciled.
Interval
About every 300 seconds, measured from the spacing of observations in the last hour. The configured interval is not exposed publicly.
Success
The probe records a success when the endpoint returns the response it is configured to expect - HTTP 200 for every public record, within a 15-second deadline, following at most five redirect hops. A slow but correct response is latency, not downtime.
Failure
A timeout, a transport error, a redirect the security policy blocks, or any status code other than the expected one. Each is stored with its error type so the causes stay distinguishable.
Incident opens
For public records like this one, nothing: the public pipeline stores observations and does not open incidents. Customer monitoring under the deployed single-origin topology opens an incident after two consecutive failed checks from one observation point; with a genuine multi-origin fleet, two or more independent points must agree inside a 60-second window. Two labels from one worker never count as agreement.
Incident closes
Two consecutive successful observations from the same observation point - or, under a multi-origin fleet, from at least two points - so flapping does not open and close a record repeatedly.
Availability
Successful observations divided by all observations in the window. A window with no observations is insufficient data, never 100%.
Latency
Mean and 95th percentile of response times in the window, in milliseconds, across every observation in it. The chart breaks the line where a bucket has no successful response.
Freshness
Rendered on the server and revalidated every 60 seconds. An observation older than 15 minutes marks the record stale rather than healthy or down. All timestamps are UTC.
Not vendor status
Auth0's own status reporting is not ingested, mirrored or reconciled. The two can disagree - a measured endpoint can be up while services are degraded, and vice versa. Read both.
Limits
These figures describe the listed endpoints, observed from the listed region labels. They are not a statement about every service the vendor operates, about specific API routes or models, or about your integration.

This is not a status page

What this record is, and what it deliberately is not.
Endpoint vs service
The endpoint observed here (status.auth0.com) is Auth0's public status site. This record measures that endpoint's HTTP behaviour - whether it answers, how fast, with what status. A status site can be perfectly reachable while the services it reports on are degraded, and unreachable while they are healthy. This record answers neither question; it answers the first one exactly.
Official vendor status
This is not Auth0's official vendor status page, and it is not affiliated with or endorsed by them. It is an independent measurement of the endpoints listed in this record.
Vendor-reported state
RELIASTRA does not ingest, mirror or reconcile vendor-reported state. Nothing here is copied from a status page, an aggregator or a vendor API. Every figure is derived from observations RELIASTRA issued itself.
Why that matters
A status page is written by the party whose reliability it describes, and is updated when that party decides to update it. An independent record is written by the observer. Where the two disagree, both are worth reading - but only one of them is yours to keep.
Scope
These observations describe the listed endpoints from the listed region labels. They are not a statement about every service Auth0 operates, or about your specific integration.

Dependency information

The configuration this record was produced from, as the measurement API reports it.
Observed endpointhttps://status.auth0.comHTTPS · host status.auth0.com · path /
Regions
us-east
Active
yes
Endpoint state
operational
Record identifier
auth0
Category
auth
Record opened
15 Aug 2026
Visibility
public
Other dependencies under observation.

Dependencies under observation

Method and reference

Your own record

Auth0 is one dependency. Your product has a list.

Observe the services your product calls. Attribute incidents. Keep the record.

Start observingPricing