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 55 min ago. Last stored result reached it in 90 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 18 | 0 | 0.0 | 96 ms | 0 |
| Mon 21 | 0 | 0.0 | 105 ms | 0 |
| Mon 23 | 0 | 0.0 | 198 ms | 0 |
| Tue 01 | 0 | 0.0 | 97 ms | 0 |
| Tue 03 | 0 | 0.0 | 106 ms | 0 |
| Tue 05 | 0 | 0.0 | 610 ms | 0 |
| Tue 07 | 0 | 0.0 | 448 ms | 0 |
| Tue 09 | 0 | 0.0 | 613 ms | 0 |
| Tue 11 | 0 | 0.0 | 321 ms | 0 |
| Tue 14 | 0 | 0.0 | 594 ms | 0 |
| Tue 16 | 0 | 0.0 | 567 ms | 0 |
| Tue 18 | 0 | 0.0 | 616 ms | 0 |
| Tue 20 | 0 | 0.0 | 275 ms | 0 |
| Tue 23 | 0 | 0.0 | 634 ms | 0 |
| Wed 01 | 0 | 0.0 | 615 ms | 0 |
| Wed 03 | 0 | 0.0 | 727 ms | 0 |
| Wed 05 | 0 | 0.0 | 627 ms | 0 |
| Wed 08 | 0 | 0.0 | 321 ms | 0 |
| Wed 10 | 0 | 0.0 | 104 ms | 0 |
| Wed 12 | 0 | 0.0 | 550 ms | 0 |
| Wed 14 | 0 | 0.0 | 580 ms | 0 |
| Wed 16 | 0 | 0.0 | 766 ms | 0 |
| Wed 18 | 0 | 0.0 | 325 ms | 0 |
| Wed 21 | 0 | 0.0 | 534 ms | 0 |
| Wed 23 | 0 | 0.0 | 661 ms | 0 |
| Thu 01 | 0 | 0.0 | 892 ms | 0 |
| Thu 03 | 0 | 0.0 | 558 ms | 0 |
| Thu 05 | 0 | 0.0 | 597 ms | 0 |
| Thu 07 | 0 | 0.0 | 890 ms | 0 |
| Thu 09 | 0 | 0.0 | 500 ms | 0 |
| Thu 11 | 0 | 0.0 | 703 ms | 0 |
| Thu 13 | 0 | 0.0 | 595 ms | 0 |
| Thu 16 | 0 | 0.0 | 576 ms | 0 |
| Thu 18 | 0 | 0.0 | 113 ms | 0 |
| Thu 20 | 0 | 0.0 | 69 ms | 0 |
| Thu 22 | 0 | 0.0 | 701 ms | 0 |
| Fri 00 | 0 | 0.0 | 670 ms | 0 |
| Fri 02 | 0 | 0.0 | 608 ms | 0 |
| Fri 04 | 0 | 0.0 | 426 ms | 0 |
| Fri 06 | 0 | 0.0 | 503 ms | 0 |
| Fri 08 | 0 | 0.0 | 603 ms | 0 |
| Fri 10 | 0 | 0.0 | 602 ms | 0 |
| Fri 12 | 0 | 0.0 | 1012 ms | 0 |
| Fri 14 | 0 | 0.0 | 612 ms | 0 |
| Fri 16 | 0 | 0.0 | 985 ms | 0 |
| Fri 18 | 0 | 0.0 | 1005 ms | 0 |
| Fri 19 | 0 | 0.0 | 595 ms | 0 |
| Fri 21 | 0 | 0.0 | 90 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 6 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Relu 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 Relu goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Relu alerts to Slack, Discord or a webhook — free.
Relu, at relu.ai, is one of the Health services we monitor. Supercharge your CAD team. Scale your lab with consistent results and faster turnaround, with Relu designing the repeatable work to your standard.
Relu publishes an official status page at status.relu.ai; when we can read it, its incident level is folded into the status shown here.
Typical issues 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 6 days of checks. No public incidents logged since monitoring began 6 days ago.
Response time over the last 24 hours: 631 ms average, 90–1012 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Relu incident since monitoring began 6 days ago.
From our own checks: 100% over 6 days of checks.
631 ms on average over the last 24 hours (90–1012 ms).
Yes, at https://status.relu.ai.
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 Relu here at once, the problem is on Relu'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 Relu. 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.