User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Health
Is T-Pro down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → tpro.io—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · 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. Every report with a known place can appear on the map. Updates every minute.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 55 min ago. Last stored result reached it in 683 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 20 | 0 | 0.0 | 617 ms | 0 |
| Mon 22 | 0 | 0.0 | 652 ms | 0 |
| Tue 00 | 0 | 0.0 | 679 ms | 0 |
| Tue 02 | 0 | 0.0 | 683 ms | 0 |
| Tue 04 | 0 | 0.0 | 654 ms | 0 |
| Tue 06 | 0 | 0.0 | 618 ms | 0 |
| Tue 08 | 0 | 0.0 | 661 ms | 0 |
| Tue 10 | 0 | 0.0 | 1076 ms | 0 |
| Tue 13 | 0 | 0.0 | 681 ms | 0 |
| Tue 15 | 0 | 0.0 | 666 ms | 0 |
| Tue 17 | 0 | 0.0 | 759 ms | 0 |
| Tue 19 | 0 | 0.0 | 614 ms | 0 |
| Tue 22 | 0 | 0.0 | 590 ms | 0 |
| Wed 00 | 0 | 0.0 | 621 ms | 0 |
| Wed 02 | 0 | 0.0 | 713 ms | 0 |
| Wed 04 | 0 | 0.0 | 611 ms | 0 |
| Wed 07 | 0 | 0.0 | 651 ms | 0 |
| Wed 09 | 0 | 0.0 | 621 ms | 0 |
| Wed 11 | 0 | 0.0 | 617 ms | 0 |
| Wed 13 | 0 | 0.0 | 528 ms | 0 |
| Wed 15 | 0 | 0.0 | 885 ms | 0 |
| Wed 17 | 0 | 0.0 | 689 ms | 0 |
| Wed 20 | 0 | 0.0 | 381 ms | 0 |
| Wed 22 | 0 | 0.0 | 740 ms | 0 |
| Thu 00 | 0 | 0.0 | 599 ms | 0 |
| Thu 02 | 0 | 0.0 | 656 ms | 0 |
| Thu 04 | 0 | 0.0 | 703 ms | 0 |
| Thu 06 | 0 | 0.0 | 732 ms | 0 |
| Thu 08 | 0 | 0.0 | 642 ms | 0 |
| Thu 10 | 0 | 0.0 | 643 ms | 0 |
| Thu 12 | 0 | 0.0 | 623 ms | 0 |
| Thu 15 | 0 | 0.0 | 703 ms | 0 |
| Thu 17 | 0 | 0.0 | 660 ms | 0 |
| Thu 19 | 0 | 0.0 | 723 ms | 0 |
| Thu 21 | 0 | 0.0 | 682 ms | 0 |
| Thu 23 | 0 | 0.0 | 665 ms | 0 |
| Fri 01 | 0 | 0.0 | 640 ms | 0 |
| Fri 03 | 0 | 0.0 | 629 ms | 0 |
| Fri 05 | 0 | 0.0 | 635 ms | 0 |
| Fri 07 | 0 | 0.0 | 686 ms | 0 |
| Fri 09 | 0 | 0.0 | 570 ms | 0 |
| Fri 11 | 0 | 0.0 | 684 ms | 0 |
| Fri 12 | 0 | 0.0 | 547 ms | 0 |
| Fri 14 | 0 | 0.0 | 640 ms | 0 |
| Fri 16 | 0 | 0.0 | 691 ms | 0 |
| Fri 18 | 0 | 0.0 | 640 ms | 0 |
| Fri 19 | 0 | 0.0 | 644 ms | 0 |
| Fri 20 | 0 | 0.0 | 683 ms | 0 |
Reliability
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.
Embed this status: free live T-Pro 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 T-Pro yet. Outages of 10 minutes or more get their own page here.
Having trouble with T-Pro?
One report per service every 10 minutes from this network. No account.
Follow T-Pro
Get an email when T-Pro goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send T-Pro alerts to Slack, Discord or a webhook — free.
About T-Pro
We track T-Pro (tpro.io) as part of the Health group. T-Pro is the leading provider of mobile dictation, speech recognition and clinical correspondence software to the healthcare sector
T-Pro publishes an official status page at status.tpro.io; when we can read it, its incident level is folded into the status shown here.
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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 643 ms average, 547–691 ms range across 13 successful checks.
Questions
Is T-Pro down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was T-Pro last down?
We have not recorded a public T-Pro incident since monitoring began 7 days ago.
What is T-Pro's uptime?
From our own checks: 100% over 7 days of checks.
How fast does T-Pro respond?
643 ms on average over the last 24 hours (547–691 ms).
Does T-Pro have an official status page?
Yes, at https://status.tpro.io.
T-Pro 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 T-Pro here at once, the problem is on T-Pro'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 T-Pro. 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.