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 2 hr ago. Last stored result reached it in 189 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 12 | 0 | 0.0 | 164 ms | 0 |
| Mon 14 | 0 | 0.0 | 171 ms | 0 |
| Mon 17 | 0 | 0.0 | 201 ms | 0 |
| Mon 19 | 0 | 0.0 | 143 ms | 0 |
| Mon 21 | 0 | 0.0 | 84 ms | 0 |
| Mon 23 | 0 | 0.0 | 151 ms | 0 |
| Tue 01 | 0 | 0.0 | 211 ms | 0 |
| Tue 03 | 0 | 0.0 | 230 ms | 0 |
| Tue 05 | 0 | 0.0 | 197 ms | 0 |
| Tue 07 | 0 | 0.0 | 162 ms | 0 |
| Tue 09 | 0 | 0.0 | 255 ms | 0 |
| Tue 12 | 0 | 0.0 | 165 ms | 0 |
| Tue 14 | 0 | 0.0 | 187 ms | 0 |
| Tue 16 | 0 | 0.0 | 277 ms | 0 |
| Tue 18 | 0 | 0.0 | 82 ms | 0 |
| Tue 21 | 0 | 0.0 | 191 ms | 0 |
| Tue 23 | 0 | 0.0 | 136 ms | 0 |
| Wed 01 | 0 | 0.0 | 152 ms | 0 |
| Wed 03 | 0 | 0.0 | 254 ms | 0 |
| Wed 06 | 0 | 0.0 | 197 ms | 0 |
| Wed 08 | 0 | 0.0 | 170 ms | 0 |
| Wed 10 | 0 | 0.0 | 269 ms | 0 |
| Wed 12 | 0 | 0.0 | 181 ms | 0 |
| Wed 14 | 0 | 0.0 | 238 ms | 0 |
| Wed 16 | 0 | 0.0 | 270 ms | 0 |
| Wed 19 | 0 | 0.0 | 354 ms | 0 |
| Wed 21 | 0 | 0.0 | 220 ms | 0 |
| Wed 23 | 0 | 0.0 | 176 ms | 0 |
| Thu 01 | 0 | 0.0 | 280 ms | 0 |
| Thu 03 | 0 | 0.0 | 183 ms | 0 |
| Thu 05 | 0 | 0.0 | 126 ms | 0 |
| Thu 07 | 0 | 0.0 | 179 ms | 0 |
| Thu 10 | 0 | 0.0 | 219 ms | 0 |
| Thu 12 | 0 | 0.0 | 256 ms | 0 |
| Thu 14 | 0 | 0.0 | 216 ms | 0 |
| Thu 16 | 0 | 0.0 | 114 ms | 0 |
| Thu 18 | 0 | 0.0 | 218 ms | 0 |
| Thu 20 | 0 | 0.0 | 141 ms | 0 |
| Thu 22 | 0 | 0.0 | 195 ms | 0 |
| Fri 00 | 0 | 0.0 | 137 ms | 0 |
| Fri 02 | 0 | 0.0 | 232 ms | 0 |
| Fri 04 | 0 | 0.0 | 284 ms | 0 |
| Fri 06 | 0 | 0.0 | 182 ms | 0 |
| Fri 08 | 0 | 0.0 | 160 ms | 0 |
| Fri 10 | 0 | 0.0 | 187 ms | 0 |
| Fri 12 | 0 | 0.0 | 243 ms | 0 |
| Fri 15 | 0 | 0.0 | 164 ms | 0 |
| Fri 17 | 0 | 0.0 | 189 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for RCS Cloud 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 RCS Cloud goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send RCS Cloud alerts to Slack, Discord or a webhook — free.
We track RCS Cloud (rcsworks.com) as part of the Entertainment group. The world's largest broadcast software company. RCS powers radio automation, music scheduling, streaming, and ad management for broadcasters.
RCS Cloud publishes an official status page at status.rcsworks.com; when we can read it, its incident level is folded into the status shown here.
Common problems for entertainment services: streams buffering or not starting, playback errors, and app sign-in problems.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 188 ms average, 15–284 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public RCS Cloud incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
188 ms on average over the last 24 hours (15–284 ms).
Yes, at https://status.rcsworks.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 RCS Cloud here at once, the problem is on RCS Cloud'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 RCS Cloud. 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.