User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Health
Is Wibbi (formerly Physiotec) 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 → wibbi.com—
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 1 hr ago. Last stored result reached it in 332 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 |
|---|---|---|---|---|
| Tue 14 | 0 | 0.0 | 335 ms | 0 |
| Tue 16 | 0 | 0.0 | 273 ms | 0 |
| Tue 18 | 0 | 0.0 | 356 ms | 0 |
| Tue 21 | 0 | 0.0 | 394 ms | 0 |
| Tue 23 | 0 | 0.0 | 393 ms | 0 |
| Wed 01 | 0 | 0.0 | 185 ms | 0 |
| Wed 03 | 0 | 0.0 | 372 ms | 0 |
| Wed 06 | 0 | 0.0 | 184 ms | 0 |
| Wed 08 | 0 | 0.0 | 256 ms | 0 |
| Wed 10 | 0 | 0.0 | 332 ms | 0 |
| Wed 12 | 0 | 0.0 | 382 ms | 0 |
| Wed 14 | 0 | 0.0 | 477 ms | 0 |
| Wed 16 | 0 | 0.0 | 161 ms | 0 |
| Wed 19 | 0 | 0.0 | 233 ms | 0 |
| Wed 21 | 0 | 0.0 | 316 ms | 0 |
| Wed 23 | 0 | 0.0 | 190 ms | 0 |
| Thu 00 | 0 | 0.0 | 340 ms | 0 |
| Thu 02 | 0 | 0.0 | 396 ms | 0 |
| Thu 04 | 0 | 0.0 | 374 ms | 0 |
| Thu 06 | 0 | 0.0 | 398 ms | 0 |
| Thu 08 | 0 | 0.0 | 359 ms | 0 |
| Thu 10 | 0 | 0.0 | 308 ms | 0 |
| Thu 12 | 0 | 0.0 | 302 ms | 0 |
| Thu 15 | 0 | 0.0 | 382 ms | 0 |
| Thu 17 | 0 | 0.0 | 213 ms | 0 |
| Thu 19 | 0 | 0.0 | 136 ms | 0 |
| Thu 21 | 0 | 0.0 | 343 ms | 0 |
| Thu 23 | 0 | 0.0 | 345 ms | 0 |
| Fri 01 | 0 | 0.0 | 368 ms | 0 |
| Fri 03 | 0 | 0.0 | 460 ms | 0 |
| Fri 05 | 0 | 0.0 | 187 ms | 0 |
| Fri 07 | 0 | 0.0 | 347 ms | 0 |
| Fri 08 | 0 | 0.0 | 182 ms | 0 |
| Fri 10 | 0 | 0.0 | 228 ms | 0 |
| Fri 11 | 0 | 0.0 | 342 ms | 0 |
| Fri 13 | 0 | 0.0 | 334 ms | 0 |
| Fri 15 | 0 | 0.0 | 439 ms | 0 |
| Fri 17 | 0 | 0.0 | 368 ms | 0 |
| Fri 19 | 0 | 0.0 | 337 ms | 0 |
| Fri 21 | 0 | 0.0 | 250 ms | 0 |
| Fri 23 | 0 | 0.0 | 368 ms | 0 |
| Sat 01 | 0 | 0.0 | 286 ms | 0 |
| Sat 02 | 0 | 0.0 | 338 ms | 0 |
| Sat 04 | 0 | 0.0 | 315 ms | 0 |
| Sat 06 | 0 | 0.0 | 347 ms | 0 |
| Sat 08 | 0 | 0.0 | 181 ms | 0 |
| Sat 10 | 0 | 0.0 | 342 ms | 0 |
| Sat 12 | 0 | 0.0 | 332 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 9 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Wibbi (formerly Physiotec) 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 Wibbi (formerly Physiotec) yet. Outages of 10 minutes or more get their own page here.
All Wibbi (formerly Physiotec) outages · Every recent outage
Having trouble with Wibbi (formerly Physiotec)?
One report per service every 10 minutes from this network. No account.
Follow Wibbi (formerly Physiotec)
Get an email when Wibbi (formerly Physiotec) goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Wibbi (formerly Physiotec) alerts to Slack, Discord or a webhook — free.
About Wibbi (formerly Physiotec)
Wibbi (formerly Physiotec), at wibbi.com, is one of the Health services we monitor. Care platform that keeps treatment going between visits. Home exercise programs, RTM, patient engagement and outcomes in one place.
Wibbi (formerly Physiotec) publishes an official status page at status.wibbi.com; 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 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 321 ms average, 178–439 ms range across 14 successful checks.
Questions
Is Wibbi (formerly Physiotec) down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Wibbi (formerly Physiotec) last down?
We have not recorded a public Wibbi (formerly Physiotec) incident since monitoring began 9 days ago.
What is Wibbi (formerly Physiotec)'s uptime?
From our own checks: 100% over 9 days of checks.
How fast does Wibbi (formerly Physiotec) respond?
321 ms on average over the last 24 hours (178–439 ms).
Does Wibbi (formerly Physiotec) have an official status page?
Yes, at https://status.wibbi.com.
Wibbi (formerly Physiotec) 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 Wibbi (formerly Physiotec) here at once, the problem is on Wibbi (formerly Physiotec)'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 Wibbi (formerly Physiotec). 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.