User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Entertainment
rundowncreator.com · 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 1 hr ago. Last stored result reached it in 84 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 15 | 0 | 0.0 | 148 ms | 0 |
| Tue 18 | 0 | 0.0 | 181 ms | 0 |
| Tue 20 | 0 | 0.0 | 89 ms | 0 |
| Tue 22 | 0 | 0.0 | 184 ms | 0 |
| Wed 00 | 0 | 0.0 | 106 ms | 0 |
| Wed 03 | 0 | 0.0 | 79 ms | 0 |
| Wed 05 | 0 | 0.0 | 179 ms | 0 |
| Wed 07 | 0 | 0.0 | 91 ms | 0 |
| Wed 09 | 0 | 0.0 | 153 ms | 0 |
| Wed 12 | 0 | 0.0 | 144 ms | 0 |
| Wed 14 | 0 | 0.0 | 94 ms | 0 |
| Wed 16 | 0 | 0.0 | 127 ms | 0 |
| Wed 18 | 0 | 0.0 | 112 ms | 0 |
| Wed 20 | 0 | 0.0 | 112 ms | 0 |
| Wed 22 | 0 | 0.0 | 38 ms | 0 |
| Thu 01 | 0 | 0.0 | 153 ms | 0 |
| Thu 03 | 0 | 0.0 | 170 ms | 0 |
| Thu 05 | 0 | 0.0 | 35 ms | 0 |
| Thu 07 | 0 | 0.0 | 96 ms | 0 |
| Thu 09 | 0 | 0.0 | 98 ms | 0 |
| Thu 11 | 0 | 0.0 | 85 ms | 0 |
| Thu 13 | 0 | 0.0 | 98 ms | 0 |
| Thu 15 | 0 | 0.0 | 64 ms | 0 |
| Thu 17 | 0 | 0.0 | 153 ms | 0 |
| Thu 19 | 0 | 0.0 | 87 ms | 0 |
| Thu 21 | 0 | 0.0 | 114 ms | 0 |
| Thu 23 | 0 | 0.0 | 44 ms | 0 |
| Fri 01 | 0 | 0.0 | 158 ms | 0 |
| Fri 03 | 0 | 0.0 | 92 ms | 0 |
| Fri 06 | 0 | 0.0 | 141 ms | 0 |
| Fri 08 | 0 | 0.0 | 75 ms | 0 |
| Fri 10 | 0 | 0.0 | 142 ms | 0 |
| Fri 12 | 0 | 0.0 | 102 ms | 0 |
| Fri 14 | 0 | 0.0 | 92 ms | 0 |
| Fri 15 | 0 | 0.0 | 148 ms | 0 |
| Fri 17 | 0 | 0.0 | 103 ms | 0 |
| Fri 18 | 0 | 0.0 | 160 ms | 0 |
| Fri 20 | 0 | 0.0 | 123 ms | 0 |
| Fri 22 | 0 | 0.0 | 104 ms | 0 |
| Sat 00 | 0 | 0.0 | 151 ms | 0 |
| Sat 02 | 0 | 0.0 | 178 ms | 0 |
| Sat 03 | 0 | 0.0 | 43 ms | 0 |
| Sat 04 | 0 | 0.0 | 103 ms | 0 |
| Sat 06 | 0 | 0.0 | 99 ms | 0 |
| Sat 07 | 0 | 0.0 | 110 ms | 0 |
| Sat 08 | 0 | 0.0 | 89 ms | 0 |
| Sat 10 | 0 | 0.0 | 130 ms | 0 |
| Sat 12 | 0 | 0.0 | 84 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 Rundown Creator 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 Rundown Creator goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Rundown Creator alerts to Slack, Discord or a webhook — free.
Rundown Creator is listed in our Entertainment category and checked at rundowncreator.com. Collaborative, web-based rundown software and teleprompter software for broadcast TV/radio, live streaming and live events
Rundown Creator publishes an official status page at status.rundowncreator.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: 114 ms average, 43–178 ms range across 17 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Rundown Creator incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
114 ms on average over the last 24 hours (43–178 ms).
Yes, at https://status.rundowncreator.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 Rundown Creator here at once, the problem is on Rundown Creator'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 Rundown Creator. 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.