Requesting the current observation, the aggregated windows and the incident history from the measurement API. No figure is drawn until it has been read - this page never shows a placeholder value.
External dependency intelligence. RELIASTRA observes Auth0's public auth endpoint from 2 regions and publishes the measurements without reference to any status page the vendor operates.
No observations
No completed observation has been recorded for this dependency yet, so no state can be reported.
Last observationno observation
Observation cadenceno observation
No observation has been recorded yet, so there is no elapsed time to count and no interval to measure against.
No observation has been recorded for this dependency.
Category
auth
Observed endpoint
status.auth0.com
Observation regions
eu-west · us-east
Measured by
RELIASTRA probes
Summary of this record
Auth0 is a auth dependency under continuous observation by RELIASTRA. Requests are issued to its public endpoints from eu-west, us-east, and every response is stored with its latency, status code and timestamp. The last observation recorded was no observation.
Over the last 24 hours RELIASTRA recorded 0 observations, an availability of insufficient data and a mean response of no data ms; over 30 days, insufficient data. No incident has been opened against this dependency. Availability, latency and incident history below are measured, not reported by the vendor.
01
Current observation
The most recent completed observation in each region RELIASTRA runs against this dependency. These are individual measurements, not averages: one request, one response, one timestamp.
us-eastEastern United Statesno datano datano observationno observation
02
Observed state and availability
The state at the top of this record is derived from observations, not from an announcement. No completed observation has been recorded for this dependency yet, so no state can be reported. Availability is the share of observations in a window that returned a status code with no transport error; a window with no observations reads as insufficient data rather than as 100%.
No observationsLast check no observation2 regions observed
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
Region
Initialising observation series…
Requesting aggregated observations from the measurement API. No values are shown until they arrive.
Geography is part of the measurement. A dependency that answers in 180 ms from Dublin and fails from Mumbai has a regional fault, and only a record that says where it was observed from can show that. These are the regions RELIASTRA schedules checks in for this dependency.
Equirectangular projection, 76° N to 56° S. 2 of 2 observation regions could be placed from its published coordinates; all regions returned by the API are shown.
An incident is opened when at least two observation regions fail against Auth0 inside the same 60-second window, and closed when consecutive successful observations return from at least two regions. Single-region failures are recorded as observations but never published here as an incident.
0 recordsPublished evidence: rolling 90 days
No incidents observed
RELIASTRA has not opened an incident against this dependency. That means no qualifying multi-region failure has been observed - it is not a statement about failures the vendor may have had in components RELIASTRA does not observe.
06
Evidence records
An evidence record is the signed artifact behind an incident: the observations that triggered it, the regions they came from, the timestamps, and the checksum that makes the file verifiable after the fact. Published records are released to a named requester rather than served from an open link.
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.
This section describes what the system actually does. Anything RELIASTRA does not measure is listed as a limit rather than left for a reader to assume.
Scheduled workers issue real requests to Auth0's public endpoints from eu-west, us-east. Nothing on this page is read from a vendor status page, a third-party aggregator, or a customer's own logs.
How often
The observation interval could not be derived from the current window. The interval is set per endpoint and is not exposed publicly, so this record reports the cadence measured from the data rather than a schedule it cannot verify.
What counts as a failure
An observation fails when no HTTP status code is recorded or a transport error is returned. A slow but valid response is recorded as latency, not as downtime - which is why a dependency can show high latency and full availability in the same window.
When an incident is opened
At least two distinct regions must record a failure inside the same 60-second window. A single region failing is treated as a fault in the observation path until a second region confirms it, which is the rule that keeps a probe's bad minute out of a vendor's public record.
When an incident is closed
Consecutive successful observations must return from at least two regions before the incident resolves. Flapping successes inside the window keep it open.
08
RELIASTRA observation is not official vendor status
The distinction matters most in the hour it is least convenient, so it is stated here rather than in a footnote.
RELIASTRA observation
An independent measurement of what Auth0's public endpoints returned to a request from a specific region at a specific second. It can disagree with the vendor's own status page, and a regional failure the vendor does not classify as an outage still appears here as observed failures.
Official vendor status
A statement published by Auth0 about its own services. RELIASTRA does not ingest, mirror or reconcile it, so no comparison between the two is shown on this page. If the vendor publishes a status page, read it alongside this record rather than instead of it.
09
Dependency information
The configuration this record was produced from, exactly as the measurement API reports it.
RELIASTRA observes the specific external services your product calls - including the ones no public index tracks - attributes your incidents to the dependency that caused them, and produces the evidence record you need when a vendor disputes it.
A region reporting no response is not automatically an outage: RELIASTRA opens an incident only when at least two regions fail inside the same 60-second window.
24 hours
0
insufficient data
no data
no data
7 days0insufficient datano datano data
30 days0insufficient datano datano data
90 days0insufficient datano datano data
1 hour
insufficient data
Observations
0
Mean latency
no data
95th percentile
no data
6 hours
insufficient data
Observations
0
Mean latency
no data
95th percentile
no data
24 hours
insufficient data
Observations
0
Mean latency
no data
95th percentile
no data
7 days
insufficient data
Observations
0
Mean latency
no data
95th percentile
no data
30 days
insufficient data
Observations
0
Mean latency
no data
95th percentile
no data
90 days
insufficient data
Observations
0
Mean latency
no data
95th percentile
no data
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.
eu-westWestern Europe53.35° N, 6.26° Wno datano data
us-eastEastern United States38.95° N, 77.45° Wno datano data
eu-west
no data
Location
Western Europe
Coordinate
53.35° N, 6.26° W
Observed cadence
no data
us-east
no data
Location
Eastern United States
Coordinate
38.95° N, 77.45° W
Observed cadence
no data
Cadence is measured from the density 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.
How availability is calculated
Observations that returned a status code with no transport error, divided by all observations in the window. Availability is always published with the number of observations behind it, and a window with no observations is reported as insufficient data - never as 100%.
How latency is reported
Mean and 95th percentile of observed response times in the window, in milliseconds, across every region. The telemetry chart plots the mean of each bucket at the resolution the API aggregates to and breaks the line wherever a bucket contains no successful response.
Freshness
This page is rendered on the server and revalidated every 60 seconds; the observation counter updates in the browser and requests fresh data when the expected interval has passed. Every timestamp on this page is UTC.
Limits
These measurements describe the endpoints listed in the dependency information below, observed from the regions listed above. They are not a statement about every service the vendor operates, about a private or regional endpoint RELIASTRA does not observe, or about your specific integration with them.
RELIASTRA has not recorded a completed observation for this dependency over the last 24 hours from eu-west. Nothing is drawn here rather than a flat line, because a flat line would assert an availability that was never measured. Once observations begin, each bucket appears here at the resolution the API aggregates to, and any failure or incident window is marked on the same axis.
Observations · 24 hours0Completed checks aggregated into this window
Availabilityinsufficient dataResponses with a status code and no transport error
Mean latencyno dataArithmetic mean across all regions
95th percentileno dataDrawn as the dashed threshold above
Window
07 Sep 2026 01:20:49 UTC → 08 Sep 2026 01:20:49 UTC