User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Health
regence.com · Health
Checks are succeeding and user reports are near the baseline.
Live diagnosis
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what 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, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 1803 ms · 7 min ago.
No status feed
Regence does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 12:30 | 0 | 0.0 | 1355 ms | 0 |
| 12:45 | 0 | 0.0 | 1676 ms | 0 |
| 13:00 | 0 | 0.0 | 1896 ms | 0 |
| 13:15 | 0 | 0.0 | 1499 ms | 0 |
| 13:30 | 0 | 0.0 | 1606 ms | 0 |
| 13:45 | 0 | 0.0 | 1492 ms | 0 |
| 14:00 | 0 | 0.0 | 1189 ms | 0 |
| 14:15 | 0 | 0.0 | 1426 ms | 0 |
| 14:30 | 0 | 0.0 | 1281 ms | 0 |
| 14:45 | 0 | 0.0 | 1785 ms | 0 |
| 15:00 | 0 | 0.0 | 1705 ms | 0 |
| 15:15 | 0 | 0.0 | 1827 ms | 0 |
| 15:30 | 0 | 0.0 | 1824 ms | 0 |
| 15:45 | 0 | 0.0 | 1418 ms | 0 |
| 16:00 | 0 | 0.0 | 1200 ms | 0 |
| 16:15 | 0 | 0.0 | 1283 ms | 0 |
| 16:30 | 0 | 0.0 | 1732 ms | 0 |
| 16:45 | 0 | 0.0 | 2027 ms | 0 |
| 17:00 | 0 | 0.0 | 1628 ms | 0 |
| 17:15 | 0 | 0.0 | 1901 ms | 0 |
| 17:30 | 0 | 0.0 | 1572 ms | 0 |
| 17:45 | 0 | 0.0 | 2074 ms | 0 |
| 18:00 | 0 | 0.0 | 2131 ms | 0 |
| 18:15 | 0 | 0.0 | 1492 ms | 0 |
| 18:30 | 0 | 0.0 | 789 ms | 0 |
| 18:45 | 0 | 0.0 | 1588 ms | 0 |
| 19:00 | 0 | 0.0 | 1272 ms | 0 |
| 19:15 | 0 | 0.0 | 2233 ms | 0 |
| 19:30 | 0 | 0.0 | 1700 ms | 0 |
| 19:45 | 0 | 0.0 | 1794 ms | 1 |
| 20:00 | 0 | 0.0 | 1846 ms | 0 |
| 20:15 | 0 | 0.0 | 1411 ms | 0 |
| 20:30 | 0 | 0.0 | 954 ms | 0 |
| 20:45 | 0 | 0.0 | 1439 ms | 0 |
| 21:00 | 0 | 0.0 | 1354 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Regence 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 Regence goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Regence alerts to Slack, Discord or a webhook — free.
Regence, at regence.com, is one of the Health services we monitor. Live checks and user reports.
Regence has no official status feed we can read, so this page relies on our own checks and user reports.
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: 98.31% over 1 day of checks. No public incidents logged since monitoring began 1 day ago.
Response time over the last 24 hours: 1610 ms average, 719–2836 ms range across 65 successful checks.
Checks are succeeding and user reports are near the baseline.
We have not recorded a public Regence incident since monitoring began 1 day ago.
From our own checks: 98.31% over 1 day of checks.
1610 ms on average over the last 24 hours (719–2836 ms).
Not one we can read. This page uses independent checks of regence.com and user reports.
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 Regence here at once, the problem is on Regence's side.