User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Health
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 37 min ago. Last stored result reached it in 460 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 14 | 0 | 0.0 | 496 ms | 0 |
| Tue 16 | 0 | 0.0 | 116 ms | 0 |
| Tue 18 | 0 | 0.0 | 87 ms | 0 |
| Tue 20 | 0 | 0.0 | 147 ms | 0 |
| Tue 23 | 0 | 0.0 | 400 ms | 0 |
| Wed 01 | 0 | 0.0 | 90 ms | 0 |
| Wed 03 | 0 | 0.0 | 80 ms | 0 |
| Wed 05 | 0 | 0.0 | 349 ms | 0 |
| Wed 08 | 0 | 0.0 | 347 ms | 0 |
| Wed 10 | 0 | 0.0 | 89 ms | 0 |
| Wed 12 | 0 | 0.0 | 433 ms | 0 |
| Wed 14 | 0 | 0.0 | 136 ms | 0 |
| Wed 16 | 0 | 0.0 | 476 ms | 0 |
| Wed 18 | 0 | 0.0 | 192 ms | 0 |
| Wed 21 | 0 | 0.0 | 195 ms | 0 |
| Wed 23 | 0 | 0.0 | 120 ms | 0 |
| Thu 01 | 0 | 0.0 | 158 ms | 0 |
| Thu 03 | 0 | 0.0 | 187 ms | 0 |
| Thu 05 | 0 | 0.0 | 183 ms | 0 |
| Thu 07 | 0 | 0.0 | 163 ms | 0 |
| Thu 09 | 0 | 0.0 | 383 ms | 0 |
| Thu 11 | 0 | 0.0 | 535 ms | 0 |
| Thu 13 | 0 | 0.0 | 200 ms | 0 |
| Thu 16 | 0 | 0.0 | 158 ms | 0 |
| Thu 18 | 0 | 0.0 | 190 ms | 0 |
| Thu 20 | 0 | 0.0 | 179 ms | 0 |
| Thu 22 | 0 | 0.0 | 96 ms | 0 |
| Fri 00 | 0 | 0.0 | 278 ms | 0 |
| Fri 02 | 0 | 0.0 | 88 ms | 0 |
| Fri 04 | 0 | 0.0 | 108 ms | 0 |
| Fri 06 | 0 | 0.0 | 181 ms | 0 |
| Fri 08 | 0 | 0.0 | 141 ms | 0 |
| Fri 10 | 0 | 0.0 | 75 ms | 0 |
| Fri 12 | 0 | 0.0 | 80 ms | 0 |
| Fri 14 | 0 | 0.0 | 110 ms | 0 |
| Fri 16 | 0 | 0.0 | 146 ms | 0 |
| Fri 17 | 0 | 0.0 | 76 ms | 0 |
| Fri 18 | 0 | 0.0 | 248 ms | 0 |
| Fri 20 | 0 | 0.0 | 424 ms | 0 |
| Fri 23 | 0 | 0.0 | 103 ms | 0 |
| Sat 01 | 0 | 0.0 | 77 ms | 0 |
| Sat 02 | 0 | 0.0 | 99 ms | 0 |
| Sat 04 | 0 | 0.0 | 72 ms | 0 |
| Sat 06 | 0 | 0.0 | 285 ms | 0 |
| Sat 07 | 0 | 0.0 | 511 ms | 0 |
| Sat 09 | 0 | 0.0 | 129 ms | 0 |
| Sat 11 | 0 | 0.0 | 427 ms | 0 |
| Sat 13 | 0 | 0.0 | 460 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 Swell CX 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 Swell CX goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Swell CX alerts to Slack, Discord or a webhook — free.
We track Swell CX (swellcx.com) as part of the Health group. AI-powered reputation management for multi-location MSOs, DSOs, and specialty healthcare groups. The Swell agent gives operators real-time visibility.
Swell CX publishes an official status page at status.swellcx.com; when we can read it, its incident level is folded into the status shown here.
Common problems for health services: patient portal and member sign-in failures, prescription refills or appointment booking not going through, and app errors.
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: 230 ms average, 72–511 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 Swell CX incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
230 ms on average over the last 24 hours (72–511 ms).
Yes, at https://status.swellcx.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For health services, watch for patient portal and member sign-in failures, prescription refills or appointment booking not going through, and app errors. If many people report Swell CX here at once, the problem is on Swell CX'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 Swell CX. 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.