User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Social
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
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.
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.
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.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 2 hr ago. Last stored result reached it in 121 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 445 ms | 0 |
| Mon 17 | 0 | 0.0 | 170 ms | 0 |
| Mon 19 | 0 | 0.0 | 207 ms | 0 |
| Mon 21 | 0 | 0.0 | 95 ms | 0 |
| Mon 23 | 0 | 0.0 | 225 ms | 0 |
| Tue 01 | 0 | 0.0 | 213 ms | 0 |
| Tue 03 | 0 | 0.0 | 243 ms | 0 |
| Tue 06 | 0 | 0.0 | 210 ms | 0 |
| Tue 08 | 0 | 0.0 | 350 ms | 0 |
| Tue 10 | 0 | 0.0 | 150 ms | 0 |
| Tue 12 | 0 | 0.0 | 195 ms | 0 |
| Tue 14 | 0 | 0.0 | 199 ms | 0 |
| Tue 16 | 0 | 0.0 | 233 ms | 0 |
| Tue 19 | 0 | 0.0 | 219 ms | 0 |
| Tue 21 | 0 | 0.0 | 227 ms | 0 |
| Tue 23 | 0 | 0.0 | 279 ms | 0 |
| Wed 01 | 0 | 0.0 | 217 ms | 0 |
| Wed 04 | 0 | 0.0 | 349 ms | 0 |
| Wed 06 | 0 | 0.0 | 190 ms | 0 |
| Wed 08 | 0 | 0.0 | 102 ms | 0 |
| Wed 10 | 0 | 0.0 | 126 ms | 0 |
| Wed 13 | 0 | 0.0 | 208 ms | 0 |
| Wed 15 | 0 | 0.0 | 277 ms | 0 |
| Wed 17 | 0 | 0.0 | 335 ms | 0 |
| Wed 19 | 0 | 0.0 | 337 ms | 0 |
| Wed 21 | 0 | 0.0 | 289 ms | 0 |
| Wed 23 | 0 | 0.0 | 272 ms | 0 |
| Thu 02 | 0 | 0.0 | 652 ms | 0 |
| Thu 04 | 0 | 0.0 | 246 ms | 0 |
| Thu 06 | 0 | 0.0 | 187 ms | 0 |
| Thu 08 | 0 | 0.0 | 254 ms | 0 |
| Thu 10 | 0 | 0.0 | 124 ms | 0 |
| Thu 12 | 0 | 0.0 | 200 ms | 0 |
| Thu 14 | 0 | 0.0 | 157 ms | 0 |
| Thu 16 | 0 | 0.0 | 119 ms | 0 |
| Thu 18 | 0 | 0.0 | 167 ms | 0 |
| Thu 20 | 0 | 0.0 | 224 ms | 0 |
| Thu 21 | 0 | 0.0 | 228 ms | 0 |
| Thu 23 | 0 | 0.0 | 250 ms | 0 |
| Fri 01 | 0 | 0.0 | 554 ms | 0 |
| Fri 03 | 0 | 0.0 | 100 ms | 0 |
| Fri 05 | 0 | 0.0 | 102 ms | 0 |
| Fri 07 | 0 | 0.0 | 151 ms | 0 |
| Fri 09 | 0 | 0.0 | 174 ms | 0 |
| Fri 10 | 0 | 0.0 | 135 ms | 0 |
| Fri 11 | 0 | 0.0 | 243 ms | 0 |
| Fri 13 | 0 | 0.0 | 147 ms | 0 |
| Fri 15 | 0 | 0.0 | 121 ms | 0 |
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.
No outages on record for MojoAuth yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when MojoAuth goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send MojoAuth alerts to Slack, Discord or a webhook — free.
MojoAuth, at mojoauth.com, is one of the Social services we monitor. Passwordless authentication for consumer apps, load tested at 25,000 logins/sec. Passkeys, magic links, OTP and social login on one API. Free up to 25,000 MAU.
MojoAuth publishes an official status page at status.mojoauth.com; when we can read it, its incident level is folded into the status shown here.
Common problems for social services: feeds not loading, posts or messages not sending, and login loops.
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: 193 ms average, 94–554 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public MojoAuth incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
193 ms on average over the last 24 hours (94–554 ms).
Yes, at https://status.mojoauth.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For social services, watch for feeds not loading, posts or messages not sending, and login loops. If many people report MojoAuth here at once, the problem is on MojoAuth'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 MojoAuth. 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.