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 52 min ago. Last stored result reached it in 1342 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 23 | 0 | 0.0 | 608 ms | 0 |
| Tue 01 | 0 | 0.0 | 606 ms | 0 |
| Tue 03 | 0 | 0.0 | 1371 ms | 0 |
| Tue 05 | 0 | 0.0 | 1027 ms | 0 |
| Tue 07 | 0 | 0.0 | 677 ms | 0 |
| Tue 09 | 0 | 0.0 | 1041 ms | 0 |
| Tue 11 | 0 | 0.0 | 740 ms | 0 |
| Tue 13 | 0 | 0.0 | 1223 ms | 0 |
| Tue 16 | 0 | 0.0 | 1116 ms | 0 |
| Tue 18 | 0 | 0.0 | 368 ms | 0 |
| Tue 20 | 0 | 0.0 | 1045 ms | 0 |
| Tue 22 | 0 | 0.0 | 718 ms | 0 |
| Wed 01 | 0 | 0.0 | 766 ms | 0 |
| Wed 03 | 0 | 0.0 | 1359 ms | 0 |
| Wed 05 | 0 | 0.0 | 1030 ms | 0 |
| Wed 07 | 0 | 0.0 | 2638 ms | 0 |
| Wed 10 | 0 | 0.0 | 2804 ms | 0 |
| Wed 12 | 0 | 0.0 | 1026 ms | 0 |
| Wed 14 | 0 | 0.0 | 707 ms | 0 |
| Wed 16 | 0 | 0.0 | 767 ms | 0 |
| Wed 18 | 0 | 0.0 | 711 ms | 0 |
| Wed 20 | 0 | 0.0 | 1470 ms | 0 |
| Wed 23 | 0 | 0.0 | 917 ms | 0 |
| Thu 01 | 0 | 0.0 | 1055 ms | 0 |
| Thu 03 | 0 | 0.0 | 380 ms | 0 |
| Thu 04 | 0 | 0.0 | 1051 ms | 0 |
| Thu 06 | 0 | 0.0 | 1048 ms | 0 |
| Thu 08 | 0 | 0.0 | 1020 ms | 0 |
| Thu 11 | 0 | 0.0 | 993 ms | 0 |
| Thu 13 | 0 | 0.0 | 1282 ms | 0 |
| Thu 15 | 0 | 0.0 | 1176 ms | 0 |
| Thu 17 | 0 | 0.0 | 772 ms | 0 |
| Thu 19 | 0 | 0.0 | 759 ms | 0 |
| Thu 21 | 0 | 0.0 | 1085 ms | 0 |
| Thu 23 | 0 | 0.0 | 876 ms | 0 |
| Fri 01 | 0 | 0.0 | 658 ms | 0 |
| Fri 03 | 0 | 0.0 | 1697 ms | 0 |
| Fri 05 | 0 | 0.0 | 921 ms | 0 |
| Fri 07 | 0 | 0.0 | 809 ms | 0 |
| Fri 09 | 0 | 0.0 | 696 ms | 0 |
| Fri 10 | 0 | 0.0 | 671 ms | 0 |
| Fri 11 | 0 | 0.0 | 643 ms | 0 |
| Fri 12 | 0 | 0.0 | 602 ms | 0 |
| Fri 14 | 0 | 0.0 | 974 ms | 0 |
| Fri 16 | 0 | 0.0 | 1482 ms | 0 |
| Fri 17 | 0 | 0.0 | 1330 ms | 0 |
| Fri 19 | 0 | 0.0 | 834 ms | 0 |
| Fri 20 | 0 | 0.0 | 1342 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 FPS.ms 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 FPS.ms goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send FPS.ms alerts to Slack, Discord or a webhook — free.
FPS.ms is listed in our Gaming category and checked at fps.ms. Free server hosting for Minecraft, Terraria and Hytale servers, Discord and Telegram bots, apps and websites on our Always Free plans. Upgrade any time.
FPS.ms publishes an official status page at status.fps.ms; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with gaming services: login and matchmaking failures, server disconnects, and store or download errors.
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: 967 ms average, 602–1697 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 FPS.ms incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
967 ms on average over the last 24 hours (602–1697 ms).
Yes, at https://status.fps.ms.
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 FPS.ms here at once, the problem is on FPS.ms'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 FPS.ms. 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.