User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Gaming
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 1 hr ago. Last stored result reached it in 717 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 21 | 0 | 0.0 | 747 ms | 0 |
| Tue 00 | 0 | 0.0 | 729 ms | 0 |
| Tue 02 | 0 | 0.0 | 821 ms | 0 |
| Tue 04 | 0 | 0.0 | 1135 ms | 0 |
| Tue 06 | 0 | 0.0 | 994 ms | 0 |
| Tue 08 | 0 | 0.0 | 700 ms | 0 |
| Tue 10 | 0 | 0.0 | 716 ms | 0 |
| Tue 12 | 0 | 0.0 | 3434 ms | 0 |
| Tue 15 | 0 | 0.0 | 472 ms | 0 |
| Tue 17 | 0 | 0.0 | 963 ms | 0 |
| Tue 19 | 0 | 0.0 | 780 ms | 0 |
| Tue 21 | 0 | 0.0 | 722 ms | 0 |
| Wed 00 | 0 | 0.0 | 696 ms | 0 |
| Wed 02 | 0 | 0.0 | 1666 ms | 0 |
| Wed 04 | 0 | 0.0 | 734 ms | 0 |
| Wed 06 | 0 | 0.0 | 707 ms | 0 |
| Wed 09 | 0 | 0.0 | 748 ms | 0 |
| Wed 11 | 0 | 0.0 | 742 ms | 0 |
| Wed 13 | 0 | 0.0 | 879 ms | 0 |
| Wed 15 | 0 | 0.0 | 720 ms | 0 |
| Wed 17 | 0 | 0.0 | 933 ms | 0 |
| Wed 20 | 0 | 0.0 | 1171 ms | 0 |
| Wed 22 | 0 | 0.0 | 813 ms | 0 |
| Thu 00 | 0 | 0.0 | 708 ms | 0 |
| Thu 02 | 0 | 0.0 | 3322 ms | 0 |
| Thu 04 | 0 | 0.0 | 1637 ms | 0 |
| Thu 06 | 0 | 0.0 | 1567 ms | 0 |
| Thu 08 | 0 | 0.0 | 5644 ms | 0 |
| Thu 10 | 0 | 0.0 | 735 ms | 0 |
| Thu 12 | 0 | 0.0 | 2664 ms | 0 |
| Thu 14 | 0 | 0.0 | 5886 ms | 0 |
| Thu 17 | 0 | 0.0 | 873 ms | 0 |
| Thu 19 | 0 | 0.0 | 802 ms | 0 |
| Thu 21 | 0 | 0.0 | 860 ms | 0 |
| Thu 23 | 0 | 0.0 | 773 ms | 0 |
| Fri 01 | 0 | 0.0 | 767 ms | 0 |
| Fri 03 | 0 | 0.0 | 687 ms | 0 |
| Fri 05 | 0 | 0.0 | 678 ms | 0 |
| Fri 07 | 0 | 0.0 | 707 ms | 0 |
| Fri 08 | 0 | 0.0 | 687 ms | 0 |
| Fri 10 | 0 | 0.0 | 827 ms | 0 |
| Fri 12 | 0 | 0.0 | 2957 ms | 0 |
| Fri 14 | 0 | 0.0 | 735 ms | 0 |
| Fri 16 | 0 | 0.0 | 1685 ms | 0 |
| Fri 18 | 0 | 0.0 | 732 ms | 0 |
| Fri 20 | 0 | 0.0 | 765 ms | 0 |
| Fri 22 | 0 | 0.0 | 719 ms | 0 |
| Sat 00 | 0 | 0.0 | 717 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 YuruVerse 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 YuruVerse goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send YuruVerse alerts to Slack, Discord or a webhook — free.
YuruVerse is listed in our Gaming category and checked at funami.tech. Matrix chat, Mastodon (YuruYuri Glitch), Lemmy and Minecraft, all from one house. Linux mirrors in the cloud. Enjoy!
YuruVerse publishes an official status page at status.funami.tech; when we can read it, its incident level is folded into the status shown here.
Typical issues with gaming services: login and matchmaking failures, server disconnects, and store or download errors.
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: 979 ms average, 678–2957 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public YuruVerse incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
979 ms on average over the last 24 hours (678–2957 ms).
Yes, at https://status.funami.tech.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For gaming services, watch for login and matchmaking failures, server disconnects, and store or download errors. If many people report YuruVerse here at once, the problem is on YuruVerse'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 YuruVerse. 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.