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 1 hr ago. Last stored result reached it in 178 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 01 | 0 | 0.0 | 478 ms | 0 |
| Tue 03 | 0 | 0.0 | 94 ms | 0 |
| Tue 05 | 0 | 0.0 | 50 ms | 0 |
| Tue 07 | 0 | 0.0 | 333 ms | 0 |
| Tue 09 | 0 | 0.0 | 199 ms | 0 |
| Tue 11 | 0 | 0.0 | 600 ms | 0 |
| Tue 14 | 0 | 0.0 | 399 ms | 0 |
| Tue 16 | 0 | 0.0 | 210 ms | 0 |
| Tue 18 | 0 | 0.0 | 474 ms | 0 |
| Tue 20 | 0 | 0.0 | 436 ms | 0 |
| Tue 23 | 0 | 0.0 | 197 ms | 0 |
| Wed 01 | 0 | 0.0 | 468 ms | 0 |
| Wed 03 | 0 | 0.0 | 328 ms | 0 |
| Wed 05 | 0 | 0.0 | 466 ms | 0 |
| Wed 08 | 0 | 0.0 | 511 ms | 0 |
| Wed 10 | 0 | 0.0 | 894 ms | 0 |
| Wed 12 | 0 | 0.0 | 327 ms | 0 |
| Wed 14 | 0 | 0.0 | 321 ms | 0 |
| Wed 16 | 0 | 0.0 | 234 ms | 0 |
| Wed 19 | 0 | 0.0 | 366 ms | 0 |
| Wed 21 | 0 | 0.0 | 491 ms | 0 |
| Wed 23 | 0 | 0.0 | 686 ms | 0 |
| Thu 01 | 0 | 0.0 | 246 ms | 0 |
| Thu 03 | 0 | 0.0 | 434 ms | 0 |
| Thu 05 | 0 | 0.0 | 515 ms | 0 |
| Thu 07 | 0 | 0.0 | 466 ms | 0 |
| Thu 09 | 0 | 0.0 | 61 ms | 0 |
| Thu 11 | 0 | 0.0 | 564 ms | 0 |
| Thu 14 | 0 | 0.0 | 337 ms | 0 |
| Thu 16 | 0 | 0.0 | 320 ms | 0 |
| Thu 18 | 0 | 0.0 | 159 ms | 0 |
| Thu 20 | 0 | 0.0 | 416 ms | 0 |
| Thu 22 | 0 | 0.0 | 583 ms | 0 |
| Fri 00 | 0 | 0.0 | 767 ms | 0 |
| Fri 01 | 0 | 0.0 | 492 ms | 0 |
| Fri 03 | 0 | 0.0 | 904 ms | 0 |
| Fri 05 | 0 | 0.0 | 247 ms | 0 |
| Fri 07 | 0 | 0.0 | 256 ms | 0 |
| Fri 08 | 0 | 0.0 | 534 ms | 0 |
| Fri 10 | 0 | 0.0 | 525 ms | 0 |
| Fri 12 | 0 | 0.0 | 52 ms | 0 |
| Fri 14 | 0 | 0.0 | 144 ms | 0 |
| Fri 16 | 0 | 0.0 | 478 ms | 0 |
| Fri 18 | 0 | 0.0 | 505 ms | 0 |
| Fri 19 | 0 | 0.0 | 785 ms | 0 |
| Fri 21 | 0 | 0.0 | 116 ms | 0 |
| Fri 23 | 0 | 0.0 | 172 ms | 0 |
| Sat 01 | 0 | 0.0 | 178 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 VetRec 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 VetRec goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send VetRec alerts to Slack, Discord or a webhook — free.
VetRec, at vetrec.io, is one of the Health services we monitor. VetRec is the #1 AI-powered veterinary scribe. Automate SOAP notes, medical records, and clinical documentation. Try free for 14 days.
VetRec publishes an official status page at status.vetrec.io; 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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 378 ms average, 52–904 ms range across 16 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public VetRec incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
378 ms on average over the last 24 hours (52–904 ms).
Yes, at https://status.vetrec.io.
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 VetRec here at once, the problem is on VetRec'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 VetRec. 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.