User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Health
uclahealth.org · Health
Is UCLA Health down?
Checks are succeeding and user reports are near the baseline.
Live diagnosis
Is it just me?
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.
Your browser → uclahealth.org—
Your browser → us—
Our checksReaching it
Official · ReportsNo status feed · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Our checks
Reaching it
Last check reached it in 130 ms · 7 min ago.
Official status
No status feed
UCLA Health does not publish a status feed we can read.
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 12:30 | 0 | 0.0 | 264 ms | 0 |
| 12:45 | 0 | 0.0 | 89 ms | 0 |
| 13:00 | 0 | 0.0 | 81 ms | 0 |
| 13:15 | 0 | 0.0 | 67 ms | 0 |
| 13:30 | 0 | 0.0 | 50 ms | 0 |
| 13:45 | 0 | 0.0 | 77 ms | 0 |
| 14:00 | 0 | 0.0 | 61 ms | 0 |
| 14:15 | 0 | 0.0 | 436 ms | 0 |
| 14:30 | 0 | 0.0 | 115 ms | 0 |
| 14:45 | 0 | 0.0 | 141 ms | 0 |
| 15:00 | 0 | 0.0 | 318 ms | 0 |
| 15:15 | 0 | 0.0 | 118 ms | 0 |
| 15:30 | 0 | 0.0 | 106 ms | 0 |
| 15:45 | 0 | 0.0 | 57 ms | 0 |
| 16:00 | 0 | 0.0 | 126 ms | 0 |
| 16:15 | 0 | 0.0 | 144 ms | 0 |
| 16:30 | 0 | 0.0 | 51 ms | 0 |
| 16:45 | 0 | 0.0 | 402 ms | 0 |
| 17:00 | 0 | 0.0 | 193 ms | 0 |
| 17:15 | 0 | 0.0 | 76 ms | 0 |
| 17:30 | 0 | 0.0 | 53 ms | 0 |
| 17:45 | 0 | 0.0 | 41 ms | 0 |
| 18:00 | 0 | 0.0 | 829 ms | 0 |
| 18:15 | 0 | 0.0 | 77 ms | 0 |
| 18:30 | 0 | 0.0 | 160 ms | 0 |
| 18:45 | 0 | 0.0 | 74 ms | 0 |
| 19:00 | 0 | 0.0 | 92 ms | 0 |
| 19:15 | 0 | 0.0 | 465 ms | 0 |
| 19:30 | 0 | 0.0 | 88 ms | 0 |
| 19:45 | 0 | 0.0 | 130 ms | 0 |
| 20:00 | 0 | 0.0 | 204 ms | 0 |
| 20:15 | 0 | 0.0 | 82 ms | 0 |
| 20:30 | 0 | 0.0 | 114 ms | 0 |
| 20:45 | 0 | 0.0 | 130 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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.
Embed this status: free live UCLA Health badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for UCLA Health yet. Outages of 10 minutes or more get their own page here.
Having trouble with UCLA Health?
One report per service every 10 minutes from this network. No account.
Follow UCLA Health
Get an email when UCLA Health goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send UCLA Health alerts to Slack, Discord or a webhook — free.
About UCLA Health
UCLA Health is listed in our Health category and checked at uclahealth.org. Live checks and user reports.
UCLA Health has no official status feed we can read, so this page relies on our own checks and user reports.
What usually goes wrong with 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 1 day of checks. No public incidents logged since monitoring began 1 day ago.
Response time over the last 24 hours: 152 ms average, 18–868 ms range across 62 successful checks.
Questions
Is UCLA Health down right now?
Checks are succeeding and user reports are near the baseline.
When was UCLA Health last down?
We have not recorded a public UCLA Health incident since monitoring began 1 day ago.
What is UCLA Health's uptime?
From our own checks: 100% over 1 day of checks.
How fast does UCLA Health respond?
152 ms on average over the last 24 hours (18–868 ms).
Does UCLA Health have an official status page?
Not one we can read. This page uses independent checks of uclahealth.org and user reports.
UCLA Health not working for me but the status is fine. What now?
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 UCLA Health here at once, the problem is on UCLA Health's side.