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 44 min ago. Last stored result reached it in 516 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 14 | 0 | 0.0 | 505 ms | 0 |
| Mon 16 | 0 | 0.0 | 511 ms | 0 |
| Mon 18 | 0 | 0.0 | 498 ms | 0 |
| Mon 20 | 0 | 0.0 | 513 ms | 0 |
| Mon 23 | 0 | 0.0 | 367 ms | 0 |
| Tue 01 | 0 | 0.0 | 499 ms | 0 |
| Tue 03 | 0 | 0.0 | 325 ms | 0 |
| Tue 05 | 0 | 0.0 | 308 ms | 0 |
| Tue 07 | 0 | 0.0 | 474 ms | 0 |
| Tue 09 | 0 | 0.0 | 358 ms | 0 |
| Tue 11 | 0 | 0.0 | 413 ms | 0 |
| Tue 13 | 0 | 0.0 | 393 ms | 0 |
| Tue 16 | 0 | 0.0 | 407 ms | 0 |
| Tue 18 | 0 | 0.0 | 333 ms | 0 |
| Tue 20 | 0 | 0.0 | 294 ms | 0 |
| Tue 22 | 0 | 0.0 | 403 ms | 0 |
| Wed 01 | 0 | 0.0 | 517 ms | 0 |
| Wed 03 | 0 | 0.0 | 377 ms | 0 |
| Wed 05 | 0 | 0.0 | 492 ms | 0 |
| Wed 07 | 0 | 0.0 | 492 ms | 0 |
| Wed 10 | 0 | 0.0 | 422 ms | 0 |
| Wed 12 | 0 | 0.0 | 327 ms | 0 |
| Wed 14 | 0 | 0.0 | 540 ms | 0 |
| Wed 16 | 0 | 0.0 | 522 ms | 0 |
| Wed 18 | 0 | 0.0 | 570 ms | 0 |
| Wed 20 | 0 | 0.0 | 468 ms | 0 |
| Wed 23 | 0 | 0.0 | 507 ms | 0 |
| Thu 01 | 0 | 0.0 | 549 ms | 0 |
| Thu 03 | 0 | 0.0 | 333 ms | 0 |
| Thu 05 | 0 | 0.0 | 529 ms | 0 |
| Thu 07 | 0 | 0.0 | 367 ms | 0 |
| Thu 09 | 0 | 0.0 | 487 ms | 0 |
| Thu 11 | 0 | 0.0 | 504 ms | 0 |
| Thu 13 | 0 | 0.0 | 461 ms | 0 |
| Thu 15 | 0 | 0.0 | 365 ms | 0 |
| Thu 17 | 0 | 0.0 | 443 ms | 0 |
| Thu 19 | 0 | 0.0 | 317 ms | 0 |
| Thu 21 | 0 | 0.0 | 514 ms | 0 |
| Thu 23 | 0 | 0.0 | 296 ms | 0 |
| Fri 01 | 0 | 0.0 | 417 ms | 0 |
| Fri 03 | 0 | 0.0 | 457 ms | 0 |
| Fri 05 | 0 | 0.0 | 418 ms | 0 |
| Fri 07 | 0 | 0.0 | 352 ms | 0 |
| Fri 09 | 0 | 0.0 | 342 ms | 0 |
| Fri 11 | 0 | 0.0 | 319 ms | 0 |
| Fri 12 | 0 | 0.0 | 434 ms | 0 |
| Fri 14 | 0 | 0.0 | 362 ms | 0 |
| Fri 16 | 0 | 0.0 | 516 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 ETR 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 ETR goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send ETR alerts to Slack, Discord or a webhook — free.
ETR is listed in our Health category and checked at etr.org. ETR is a behavioral health non-profit devoted to providing science-based programs and services, driven by our mission to advance health and opportunities for youth and families.
ETR publishes an official status page at status.etr.org; 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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 400 ms average, 296–516 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 ETR incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
400 ms on average over the last 24 hours (296–516 ms).
Yes, at https://status.etr.org.
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 ETR here at once, the problem is on ETR'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 ETR. 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.