User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
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 41 min ago. Last stored result reached it in 614 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 20 | 0 | 0.0 | 412 ms | 0 |
| Mon 22 | 0 | 0.0 | 283 ms | 0 |
| Tue 00 | 0 | 0.0 | 348 ms | 0 |
| Tue 02 | 0 | 0.0 | 640 ms | 0 |
| Tue 04 | 0 | 0.0 | 641 ms | 0 |
| Tue 07 | 0 | 0.0 | 670 ms | 0 |
| Tue 09 | 0 | 0.0 | 585 ms | 0 |
| Tue 11 | 0 | 0.0 | 578 ms | 0 |
| Tue 13 | 0 | 0.0 | 595 ms | 0 |
| Tue 15 | 0 | 0.0 | 379 ms | 0 |
| Tue 18 | 0 | 0.0 | 584 ms | 0 |
| Tue 20 | 0 | 0.0 | 501 ms | 0 |
| Tue 22 | 0 | 0.0 | 616 ms | 0 |
| Wed 00 | 0 | 0.0 | 611 ms | 0 |
| Wed 03 | 0 | 0.0 | 290 ms | 0 |
| Wed 05 | 0 | 0.0 | 638 ms | 0 |
| Wed 07 | 0 | 0.0 | 598 ms | 0 |
| Wed 09 | 0 | 0.0 | 584 ms | 0 |
| Wed 12 | 0 | 0.0 | 574 ms | 0 |
| Wed 14 | 0 | 0.0 | 602 ms | 0 |
| Wed 16 | 0 | 0.0 | 589 ms | 0 |
| Wed 18 | 0 | 0.0 | 930 ms | 0 |
| Wed 20 | 0 | 0.0 | 571 ms | 0 |
| Wed 22 | 0 | 0.0 | 608 ms | 0 |
| Thu 01 | 0 | 0.0 | 474 ms | 0 |
| Thu 03 | 0 | 0.0 | 628 ms | 0 |
| Thu 05 | 0 | 0.0 | 325 ms | 0 |
| Thu 07 | 0 | 0.0 | 608 ms | 0 |
| Thu 09 | 0 | 0.0 | 326 ms | 0 |
| Thu 11 | 0 | 0.0 | 593 ms | 0 |
| Thu 13 | 0 | 0.0 | 241 ms | 0 |
| Thu 15 | 0 | 0.0 | 537 ms | 0 |
| Thu 17 | 0 | 0.0 | 601 ms | 0 |
| Thu 19 | 0 | 0.0 | 625 ms | 0 |
| Thu 21 | 0 | 0.0 | 669 ms | 0 |
| Thu 23 | 0 | 0.0 | 302 ms | 0 |
| Fri 01 | 0 | 0.0 | 466 ms | 0 |
| Fri 03 | 0 | 0.0 | 313 ms | 0 |
| Fri 05 | 0 | 0.0 | 591 ms | 0 |
| Fri 07 | 0 | 0.0 | 490 ms | 0 |
| Fri 08 | 0 | 0.0 | 287 ms | 0 |
| Fri 10 | 0 | 0.0 | 620 ms | 0 |
| Fri 11 | 0 | 0.0 | 585 ms | 0 |
| Fri 13 | 0 | 0.0 | 605 ms | 0 |
| Fri 15 | 0 | 0.0 | 602 ms | 0 |
| Fri 17 | 0 | 0.0 | 581 ms | 0 |
| Fri 18 | 0 | 0.0 | 611 ms | 0 |
| Fri 19 | 0 | 0.0 | 614 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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Yoti 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 Yoti goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Yoti alerts to Slack, Discord or a webhook — free.
Yoti, at yoti.com, is one of the Cloud & developer services we monitor. Our comprehensive suite of customer verification tools make it easy for businesses to be compliant and safe for people to prove who they are.
Yoti publishes an official status page at status.yoti.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 524 ms average, 287–669 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 Yoti incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
524 ms on average over the last 24 hours (287–669 ms).
Yes, at https://status.yoti.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Yoti here at once, the problem is on Yoti'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 Yoti. 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.