User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is Logto down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → logto.io—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Live outage map
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
What's broken
Recent reports
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
Our checks
Reaching it
Last checked 11 min ago. Last stored result reached it in 50 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 20 | 0 | 0.0 | 98 ms | 0 |
| Mon 22 | 0 | 0.0 | 143 ms | 0 |
| Tue 00 | 0 | 0.0 | 42 ms | 0 |
| Tue 02 | 0 | 0.0 | 85 ms | 0 |
| Tue 04 | 0 | 0.0 | 57 ms | 0 |
| Tue 06 | 0 | 0.0 | 34 ms | 0 |
| Tue 08 | 0 | 0.0 | 45 ms | 0 |
| Tue 11 | 0 | 0.0 | 35 ms | 0 |
| Tue 13 | 0 | 0.0 | 40 ms | 0 |
| Tue 15 | 0 | 0.0 | 165 ms | 0 |
| Tue 17 | 0 | 0.0 | 51 ms | 0 |
| Tue 19 | 0 | 0.0 | 128 ms | 0 |
| Tue 22 | 0 | 0.0 | 35 ms | 0 |
| Wed 00 | 0 | 0.0 | 74 ms | 0 |
| Wed 02 | 0 | 0.0 | 53 ms | 0 |
| Wed 04 | 0 | 0.0 | 25 ms | 0 |
| Wed 07 | 0 | 0.0 | 165 ms | 0 |
| Wed 09 | 0 | 0.0 | 33 ms | 0 |
| Wed 11 | 0 | 0.0 | 31 ms | 0 |
| Wed 13 | 0 | 0.0 | 49 ms | 0 |
| Wed 15 | 0 | 0.0 | 63 ms | 0 |
| Wed 17 | 0 | 0.0 | 81 ms | 0 |
| Wed 20 | 0 | 0.0 | 67 ms | 0 |
| Wed 22 | 0 | 0.0 | 41 ms | 0 |
| Thu 00 | 0 | 0.0 | 52 ms | 0 |
| Thu 02 | 0 | 0.0 | 127 ms | 0 |
| Thu 04 | 0 | 0.0 | 47 ms | 0 |
| Thu 06 | 0 | 0.0 | 30 ms | 0 |
| Thu 08 | 0 | 0.0 | 31 ms | 0 |
| Thu 10 | 0 | 0.0 | 55 ms | 0 |
| Thu 13 | 0 | 0.0 | 56 ms | 0 |
| Thu 15 | 0 | 0.0 | 60 ms | 0 |
| Thu 17 | 0 | 0.0 | 59 ms | 0 |
| Thu 19 | 0 | 0.0 | 38 ms | 0 |
| Thu 20 | 0 | 0.0 | 70 ms | 0 |
| Thu 22 | 0 | 0.0 | 79 ms | 0 |
| Fri 00 | 0 | 0.0 | 22 ms | 0 |
| Fri 02 | 0 | 0.0 | 117 ms | 0 |
| Fri 03 | 0 | 0.0 | 41 ms | 0 |
| Fri 06 | 0 | 0.0 | 27 ms | 0 |
| Fri 08 | 0 | 0.0 | 25 ms | 0 |
| Fri 10 | 0 | 0.0 | 31 ms | 0 |
| Fri 11 | 0 | 0.0 | 31 ms | 0 |
| Fri 12 | 0 | 0.0 | 26 ms | 0 |
| Fri 14 | 0 | 0.0 | 26 ms | 0 |
| Fri 16 | 0 | 0.0 | 80 ms | 0 |
| Fri 17 | 0 | 0.0 | 50 ms | 0 |
| Fri 18 | 0 | 0.0 | 73 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 7 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Logto badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Logto yet. Outages of 10 minutes or more get their own page here.
Having trouble with Logto?
One report per service every 10 minutes from this network. No account.
Follow Logto
Get an email when Logto goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Logto alerts to Slack, Discord or a webhook — free.
About Logto
Logto is listed in our AI category and checked at logto.io. Logto adds multi-tenancy, enterprise SSO, and RBAC to your SaaS or AI apps. All with OIDC and OAuth 2.1 made simple, fast, and developer-friendly.
Logto publishes an official status page at status.logto.io; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 49 ms average, 22–117 ms range across 15 successful checks.
Questions
Is Logto down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Logto last down?
We have not recorded a public Logto incident since monitoring began 7 days ago.
What is Logto's uptime?
From our own checks: 100% over 7 days of checks.
How fast does Logto respond?
49 ms on average over the last 24 hours (22–117 ms).
Does Logto have an official status page?
Yes, at https://status.logto.io.
Logto not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Logto here at once, the problem is on Logto's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Logto. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.