User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
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 39 min ago. Last stored result reached it in 791 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 20 | 0 | 0.0 | 360 ms | 0 |
| Mon 22 | 0 | 0.0 | 893 ms | 0 |
| Tue 00 | 0 | 0.0 | 807 ms | 0 |
| Tue 02 | 0 | 0.0 | 140 ms | 0 |
| Tue 04 | 0 | 0.0 | 110 ms | 0 |
| Tue 06 | 0 | 0.0 | 291 ms | 0 |
| Tue 08 | 0 | 0.0 | 119 ms | 0 |
| Tue 11 | 0 | 0.0 | 141 ms | 0 |
| Tue 13 | 0 | 0.0 | 783 ms | 0 |
| Tue 15 | 0 | 0.0 | 125 ms | 0 |
| Tue 17 | 0 | 0.0 | 800 ms | 0 |
| Tue 20 | 0 | 0.0 | 259 ms | 0 |
| Tue 22 | 0 | 0.0 | 325 ms | 0 |
| Wed 00 | 0 | 0.0 | 834 ms | 0 |
| Wed 02 | 0 | 0.0 | 96 ms | 0 |
| Wed 03 | 0 | 0.0 | 187 ms | 0 |
| Wed 05 | 0 | 0.0 | 219 ms | 0 |
| Wed 08 | 0 | 0.0 | 128 ms | 0 |
| Wed 10 | 0 | 0.0 | 793 ms | 0 |
| Wed 12 | 0 | 0.0 | 716 ms | 0 |
| Wed 14 | 0 | 0.0 | 169 ms | 0 |
| Wed 16 | 0 | 0.0 | 834 ms | 0 |
| Wed 18 | 0 | 0.0 | 930 ms | 0 |
| Wed 21 | 0 | 0.0 | 747 ms | 0 |
| Wed 23 | 0 | 0.0 | 163 ms | 0 |
| Thu 01 | 0 | 0.0 | 141 ms | 0 |
| Thu 03 | 0 | 0.0 | 215 ms | 0 |
| Thu 05 | 0 | 0.0 | 203 ms | 0 |
| Thu 07 | 0 | 0.0 | 719 ms | 0 |
| Thu 09 | 0 | 0.0 | 823 ms | 0 |
| Thu 11 | 0 | 0.0 | 133 ms | 0 |
| Thu 13 | 0 | 0.0 | 100 ms | 0 |
| Thu 15 | 0 | 0.0 | 165 ms | 0 |
| Thu 18 | 0 | 0.0 | 180 ms | 0 |
| Thu 20 | 0 | 0.0 | 162 ms | 0 |
| Thu 22 | 0 | 0.0 | 798 ms | 0 |
| Fri 00 | 0 | 0.0 | 990 ms | 0 |
| Fri 02 | 0 | 0.0 | 349 ms | 0 |
| Fri 04 | 0 | 0.0 | 356 ms | 0 |
| Fri 06 | 0 | 0.0 | 479 ms | 0 |
| Fri 08 | 0 | 0.0 | 104 ms | 0 |
| Fri 10 | 0 | 0.0 | 132 ms | 0 |
| Fri 12 | 0 | 0.0 | 691 ms | 0 |
| Fri 14 | 0 | 0.0 | 199 ms | 0 |
| Fri 16 | 0 | 0.0 | 148 ms | 0 |
| Fri 17 | 0 | 0.0 | 790 ms | 0 |
| Fri 18 | 0 | 0.0 | 273 ms | 0 |
| Fri 20 | 0 | 0.0 | 791 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 Metaplay 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 Metaplay goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Metaplay alerts to Slack, Discord or a webhook — free.
Metaplay, at metaplay.io, is one of the AI services we monitor. Build and scale live service games on Metaplay — server-authoritative C#, full source code, modern LiveOps, and AI built in for your team and their agents.
Metaplay publishes an official status page at status.metaplay.io; when we can read it, its incident level is folded into the status shown here.
Common problems for AI services: slow or failed responses, rate-limit errors, and API timeouts.
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: 492 ms average, 104–990 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 Metaplay incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
492 ms on average over the last 24 hours (104–990 ms).
Yes, at https://status.metaplay.io.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Metaplay here at once, the problem is on Metaplay'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 Metaplay. 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.