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 398 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 | 776 ms | 0 |
| Mon 17 | 0 | 0.0 | 723 ms | 0 |
| Mon 19 | 0 | 0.0 | 764 ms | 0 |
| Mon 21 | 0 | 0.0 | 704 ms | 0 |
| Mon 23 | 0 | 0.0 | 647 ms | 0 |
| Tue 01 | 0 | 0.0 | 778 ms | 0 |
| Tue 03 | 0 | 0.0 | 695 ms | 0 |
| Tue 05 | 0 | 0.0 | 736 ms | 0 |
| Tue 07 | 0 | 0.0 | 719 ms | 0 |
| Tue 10 | 0 | 0.0 | 700 ms | 0 |
| Tue 12 | 0 | 0.0 | 729 ms | 0 |
| Tue 14 | 0 | 0.0 | 711 ms | 0 |
| Tue 16 | 0 | 0.0 | 742 ms | 0 |
| Tue 18 | 0 | 0.0 | 601 ms | 0 |
| Tue 21 | 0 | 0.0 | 695 ms | 0 |
| Tue 23 | 0 | 0.0 | 479 ms | 0 |
| Wed 01 | 0 | 0.0 | 709 ms | 0 |
| Wed 03 | 0 | 0.0 | 306 ms | 0 |
| Wed 06 | 0 | 0.0 | 274 ms | 0 |
| Wed 08 | 0 | 0.0 | 690 ms | 0 |
| Wed 10 | 0 | 0.0 | 414 ms | 0 |
| Wed 12 | 0 | 0.0 | 704 ms | 0 |
| Wed 14 | 0 | 0.0 | 768 ms | 0 |
| Wed 16 | 0 | 0.0 | 614 ms | 0 |
| Wed 19 | 0 | 0.0 | 601 ms | 0 |
| Wed 21 | 0 | 0.0 | 837 ms | 0 |
| Wed 23 | 0 | 0.0 | 734 ms | 0 |
| Thu 01 | 0 | 0.0 | 773 ms | 0 |
| Thu 03 | 0 | 0.0 | 804 ms | 0 |
| Thu 05 | 0 | 0.0 | 750 ms | 0 |
| Thu 07 | 0 | 0.0 | 515 ms | 0 |
| Thu 09 | 0 | 0.0 | 789 ms | 0 |
| Thu 11 | 0 | 0.0 | 701 ms | 0 |
| Thu 13 | 0 | 0.0 | 551 ms | 0 |
| Thu 16 | 0 | 0.0 | 536 ms | 0 |
| Thu 18 | 0 | 0.0 | 733 ms | 0 |
| Thu 20 | 0 | 0.0 | 756 ms | 0 |
| Thu 22 | 0 | 0.0 | 702 ms | 0 |
| Fri 00 | 0 | 0.0 | 611 ms | 0 |
| Fri 02 | 0 | 0.0 | 755 ms | 0 |
| Fri 04 | 0 | 0.0 | 713 ms | 0 |
| Fri 06 | 0 | 0.0 | 606 ms | 0 |
| Fri 07 | 0 | 0.0 | 713 ms | 0 |
| Fri 10 | 0 | 0.0 | 728 ms | 0 |
| Fri 11 | 0 | 0.0 | 749 ms | 0 |
| Fri 13 | 0 | 0.0 | 746 ms | 0 |
| Fri 15 | 0 | 0.0 | 559 ms | 0 |
| Fri 17 | 0 | 0.0 | 398 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 Fivemanage 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 Fivemanage goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Fivemanage alerts to Slack, Discord or a webhook — free.
We track Fivemanage (fivemanage.com) as part of the Gaming group. Manage games with Fivemanage: fast CDN and easy logging in just a few lines.
Fivemanage publishes an official status page at status.fivemanage.com; 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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 676 ms average, 398–756 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 Fivemanage incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
676 ms on average over the last 24 hours (398–756 ms).
Yes, at https://status.fivemanage.com.
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 Fivemanage here at once, the problem is on Fivemanage'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 Fivemanage. 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.