Status
Measured, not maintained.
Nobody sets this page by hand. A probe calls the public endpoints from outside and checks a marker inside each response body — because a status code alone can come from a placeholder, a maintenance page or an entirely different service.
Current measurement
What answered, and what it answered with.
Measured from outside on 2026-08-24T21:56:49Z UTC: 6 of 6 endpoints answered with the content they are supposed to serve. A status code alone does not count here — each row checks a marker inside the response body.
This measurement is 180 hours old and the freshness limit is 24. What the table shows was true then, not necessarily now.
| Endpoint | State | What it means | Round trip |
|---|---|---|---|
| Sign-in engine | operational | The engine answers and reaches its database. | 32 ms |
| OIDC discovery | operational | A standards client can configure itself without our help. | 13 ms |
| Signing keys (JWKS) | operational | Issued tokens can be verified by anyone holding this document. | 12 ms |
| API contract | operational | The machine-readable contract is served, not just documented. | 7 ms |
| auth00.co | operational | The site itself is up and serving the current build. | 7 ms |
| Public file check | operational | Anyone can check a file without an account. | 9 ms |
The round-trip time is measured from our own network in Europe. It says something about the service and very little about what you will see from where you are.
Check it yourself
You do not have to take this page's word for it.
Every row above is a public endpoint. These four commands reproduce the whole table from your machine, which is worth more than our screenshot of it.
curl -s https://login.auth00.co/health/ready
curl -s https://login.auth00.co/.well-known/openid-configuration | head -c 400
curl -s https://login.auth00.co/jwks | head -c 200
curl -s -o /dev/null -w '%{http_code}\n' https://auth00.co/If your result disagrees with the table above, the table is wrong and we want to hear about it. That is the point of publishing the commands next to the claim.
What this page does not do
Three things we will not put here yet.
- No twelve-month availability figure. The large vendors publish one. We have not measured for twelve months, so any number here would be an estimate wearing a percent sign. When the measurement history exists, the figure appears — with its calculation next to it.
- No incident history yet. An empty incident list can mean "nothing broke" or "nobody wrote it down". Ours would currently mean the second, so it is not shown.
- No regional breakdown. There is one region: Europe. A region picker with one entry is a decoration.
There is a fourth state on this page that most status pages do not have: not measurable. If the probe cannot reach an endpoint, that is what you see — never a green tick left over from the last successful run. A status page that shows the last known state as if it were the current one is worse than no status page.
Something looks wrong from where you are?
Tell us what you measured and from where. A report with a command in it is worth ten reports without one.