User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Entertainment
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 8 min ago. Last stored result reached it in 33 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 23 | 0 | 0.0 | 52 ms | 0 |
| Tue 01 | 0 | 0.0 | 16 ms | 0 |
| Tue 03 | 0 | 0.0 | 23 ms | 0 |
| Tue 05 | 0 | 0.0 | 23 ms | 0 |
| Tue 07 | 0 | 0.0 | 19 ms | 0 |
| Tue 10 | 0 | 0.0 | 42 ms | 0 |
| Tue 12 | 0 | 0.0 | 13 ms | 0 |
| Tue 14 | 0 | 0.0 | 13 ms | 0 |
| Tue 16 | 0 | 0.0 | 22 ms | 0 |
| Tue 18 | 0 | 0.0 | 62 ms | 0 |
| Tue 21 | 0 | 0.0 | 15 ms | 0 |
| Tue 23 | 0 | 0.0 | 77 ms | 0 |
| Wed 01 | 0 | 0.0 | 42 ms | 0 |
| Wed 03 | 0 | 0.0 | 40 ms | 0 |
| Wed 06 | 0 | 0.0 | 21 ms | 0 |
| Wed 08 | 0 | 0.0 | 22 ms | 0 |
| Wed 10 | 0 | 0.0 | 38 ms | 0 |
| Wed 12 | 0 | 0.0 | 42 ms | 0 |
| Wed 14 | 0 | 0.0 | 21 ms | 0 |
| Wed 17 | 0 | 0.0 | 60 ms | 0 |
| Wed 19 | 0 | 0.0 | 11 ms | 0 |
| Wed 21 | 0 | 0.0 | 33 ms | 0 |
| Wed 23 | 0 | 0.0 | 58 ms | 0 |
| Thu 01 | 0 | 0.0 | 64 ms | 0 |
| Thu 03 | 0 | 0.0 | 27 ms | 0 |
| Thu 05 | 0 | 0.0 | 27 ms | 0 |
| Thu 07 | 0 | 0.0 | 19 ms | 0 |
| Thu 10 | 0 | 0.0 | 11 ms | 0 |
| Thu 12 | 0 | 0.0 | 11 ms | 0 |
| Thu 14 | 0 | 0.0 | 17 ms | 0 |
| Thu 16 | 0 | 0.0 | 13 ms | 0 |
| Thu 18 | 0 | 0.0 | 11 ms | 0 |
| Thu 19 | 0 | 0.0 | 19 ms | 0 |
| Thu 21 | 0 | 0.0 | 51 ms | 0 |
| Thu 23 | 0 | 0.0 | 14 ms | 0 |
| Fri 01 | 0 | 0.0 | 25 ms | 0 |
| Fri 03 | 0 | 0.0 | 15 ms | 0 |
| Fri 05 | 0 | 0.0 | 43 ms | 0 |
| Fri 07 | 0 | 0.0 | 12 ms | 0 |
| Fri 09 | 0 | 0.0 | 17 ms | 0 |
| Fri 11 | 0 | 0.0 | 13 ms | 0 |
| Fri 12 | 0 | 0.0 | 41 ms | 0 |
| Fri 14 | 0 | 0.0 | 16 ms | 0 |
| Fri 16 | 0 | 0.0 | 20 ms | 0 |
| Fri 18 | 0 | 0.0 | 76 ms | 0 |
| Fri 19 | 0 | 0.0 | 34 ms | 0 |
| Fri 20 | 0 | 0.0 | 33 ms | 0 |
| Fri 22 | 0 | 0.0 | 37 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 Mgid 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 Mgid goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Mgid alerts to Slack, Discord or a webhook — free.
We track Mgid (mgid.com) as part of the Entertainment group. Our vision is to nurture a new stage of digital media, enabling consumers to engage with content and sponsored advertisements in an equally positive way.
Mgid publishes an official status page at status.mgid.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with entertainment services: streams buffering or not starting, playback errors, and app sign-in problems.
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: 27 ms average, 9–76 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Mgid incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
27 ms on average over the last 24 hours (9–76 ms).
Yes, at https://status.mgid.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For entertainment services, watch for streams buffering or not starting, playback errors, and app sign-in problems. If many people report Mgid here at once, the problem is on Mgid'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 Mgid. 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.