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 51 min ago. Last stored result reached it in 774 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 11 | 0 | 0.0 | 821 ms | 0 |
| Mon 13 | 0 | 0.0 | 817 ms | 0 |
| Mon 15 | 0 | 0.0 | 936 ms | 0 |
| Mon 17 | 0 | 0.0 | 829 ms | 0 |
| Mon 19 | 0 | 0.0 | 1048 ms | 0 |
| Mon 21 | 0 | 0.0 | 910 ms | 0 |
| Mon 23 | 0 | 0.0 | 792 ms | 0 |
| Tue 01 | 0 | 0.0 | 963 ms | 0 |
| Tue 04 | 0 | 0.0 | 932 ms | 0 |
| Tue 06 | 0 | 0.0 | 829 ms | 0 |
| Tue 08 | 0 | 0.0 | 972 ms | 0 |
| Tue 10 | 0 | 0.0 | 937 ms | 0 |
| Tue 12 | 0 | 0.0 | 1652 ms | 0 |
| Tue 14 | 0 | 0.0 | 910 ms | 0 |
| Tue 17 | 0 | 0.0 | 788 ms | 0 |
| Tue 19 | 0 | 0.0 | 746 ms | 0 |
| Tue 21 | 0 | 0.0 | 1119 ms | 0 |
| Tue 23 | 0 | 0.0 | 984 ms | 0 |
| Wed 02 | 0 | 0.0 | 951 ms | 0 |
| Wed 04 | 0 | 0.0 | 914 ms | 0 |
| Wed 06 | 0 | 0.0 | 828 ms | 0 |
| Wed 08 | 0 | 0.0 | 828 ms | 0 |
| Wed 11 | 0 | 0.0 | 604 ms | 0 |
| Wed 13 | 0 | 0.0 | 819 ms | 0 |
| Wed 15 | 0 | 0.0 | 866 ms | 0 |
| Wed 17 | 0 | 0.0 | 806 ms | 0 |
| Wed 19 | 0 | 0.0 | 802 ms | 0 |
| Wed 21 | 0 | 0.0 | 863 ms | 0 |
| Thu 00 | 0 | 0.0 | 883 ms | 0 |
| Thu 02 | 0 | 0.0 | 629 ms | 0 |
| Thu 04 | 0 | 0.0 | 943 ms | 0 |
| Thu 06 | 0 | 0.0 | 806 ms | 0 |
| Thu 08 | 0 | 0.0 | 780 ms | 0 |
| Thu 10 | 0 | 0.0 | 989 ms | 0 |
| Thu 12 | 0 | 0.0 | 715 ms | 0 |
| Thu 14 | 0 | 0.0 | 809 ms | 0 |
| Thu 16 | 0 | 0.0 | 1010 ms | 0 |
| Thu 18 | 0 | 0.0 | 944 ms | 0 |
| Thu 20 | 0 | 0.0 | 841 ms | 0 |
| Thu 22 | 0 | 0.0 | 949 ms | 0 |
| Fri 00 | 0 | 0.0 | 974 ms | 0 |
| Fri 02 | 0 | 0.0 | 733 ms | 0 |
| Fri 04 | 0 | 0.0 | 1114 ms | 0 |
| Fri 06 | 0 | 0.0 | 895 ms | 0 |
| Fri 09 | 0 | 0.0 | 497 ms | 0 |
| Fri 11 | 0 | 0.0 | 809 ms | 0 |
| Fri 13 | 0 | 0.0 | 955 ms | 0 |
| Fri 15 | 0 | 0.0 | 774 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 6 days of data so far, so the 90-day numbers fill in over time.
No outages on record for UNDRCTRL 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 UNDRCTRL goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send UNDRCTRL alerts to Slack, Discord or a webhook — free.
UNDRCTRL is listed in our Entertainment category and checked at undrctrl.id. UNDRCTRL membantu meningkatkan engagement rate akun bisnis Anda di media sosial serta kredibitas dan jangkauan konten secara organik melalui layanan SMM panel.
UNDRCTRL publishes an official status page at status.undrctrl.id; when we can read it, its incident level is folded into the status shown here.
Typical issues with entertainment services: streams buffering or not starting, playback errors, and app sign-in problems.
Measured uptime from our checks: 100% over 6 days of checks. No public incidents logged since monitoring began 6 days ago.
Response time over the last 24 hours: 846 ms average, 195–1256 ms range across 16 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public UNDRCTRL incident since monitoring began 6 days ago.
From our own checks: 100% over 6 days of checks.
846 ms on average over the last 24 hours (195–1256 ms).
Yes, at https://status.undrctrl.id.
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 UNDRCTRL here at once, the problem is on UNDRCTRL'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 UNDRCTRL. 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.