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 2052 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 12 | 0 | 0.0 | 1658 ms | 0 |
| Mon 14 | 0 | 0.0 | 1816 ms | 0 |
| Mon 16 | 0 | 0.0 | 1630 ms | 0 |
| Mon 19 | 0 | 0.0 | 1735 ms | 0 |
| Mon 21 | 0 | 0.0 | 1614 ms | 0 |
| Mon 23 | 0 | 0.0 | 1588 ms | 0 |
| Tue 01 | 0 | 0.0 | 1597 ms | 0 |
| Tue 03 | 0 | 0.0 | 1387 ms | 0 |
| Tue 05 | 0 | 0.0 | 1792 ms | 0 |
| Tue 07 | 0 | 0.0 | 1488 ms | 0 |
| Tue 09 | 0 | 0.0 | 1678 ms | 0 |
| Tue 11 | 0 | 0.0 | 1579 ms | 0 |
| Tue 14 | 0 | 0.0 | 1398 ms | 0 |
| Tue 16 | 0 | 0.0 | 1695 ms | 0 |
| Tue 18 | 0 | 0.0 | 1660 ms | 0 |
| Tue 20 | 0 | 0.0 | 1483 ms | 0 |
| Tue 23 | 0 | 0.0 | 1580 ms | 0 |
| Wed 01 | 0 | 0.0 | 1577 ms | 0 |
| Wed 03 | 0 | 0.0 | 1630 ms | 0 |
| Wed 05 | 0 | 0.0 | 1652 ms | 0 |
| Wed 08 | 0 | 0.0 | 1582 ms | 0 |
| Wed 10 | 0 | 0.0 | 1706 ms | 0 |
| Wed 12 | 0 | 0.0 | 1574 ms | 0 |
| Wed 14 | 0 | 0.0 | 1622 ms | 0 |
| Wed 16 | 0 | 0.0 | 1881 ms | 0 |
| Wed 19 | 0 | 0.0 | 1730 ms | 0 |
| Wed 21 | 0 | 0.0 | 1629 ms | 0 |
| Wed 23 | 0 | 0.0 | 2091 ms | 0 |
| Thu 01 | 0 | 0.0 | 1599 ms | 0 |
| Thu 03 | 0 | 0.0 | 1554 ms | 0 |
| Thu 05 | 0 | 0.0 | 1419 ms | 0 |
| Thu 07 | 0 | 0.0 | 1707 ms | 0 |
| Thu 09 | 0 | 0.0 | 1629 ms | 0 |
| Thu 11 | 0 | 0.0 | 1791 ms | 0 |
| Thu 13 | 0 | 0.0 | 1497 ms | 0 |
| Thu 16 | 0 | 0.0 | 1563 ms | 0 |
| Thu 18 | 0 | 0.0 | 1662 ms | 0 |
| Thu 20 | 0 | 0.0 | 1475 ms | 0 |
| Thu 22 | 0 | 0.0 | 1624 ms | 0 |
| Fri 00 | 0 | 0.0 | 1654 ms | 0 |
| Fri 02 | 0 | 0.0 | 1637 ms | 0 |
| Fri 04 | 0 | 0.0 | 1507 ms | 0 |
| Fri 06 | 0 | 0.0 | 1451 ms | 0 |
| Fri 08 | 0 | 0.0 | 1411 ms | 0 |
| Fri 11 | 0 | 0.0 | 1719 ms | 0 |
| Fri 13 | 0 | 0.0 | 2122 ms | 0 |
| Fri 15 | 0 | 0.0 | 1602 ms | 0 |
| Fri 17 | 0 | 0.0 | 2052 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 timp 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 timp goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send timp alerts to Slack, Discord or a webhook — free.
timp is listed in our Health category and checked at timp.pro. Software de gestión, app de reservas y agenda digital. Programa para gestionar las reservas de tu centro de yoga, pilates, fisioterapia, entrenamiento, fitness, salud, academia de idiomas, baile...
timp publishes an official status page at status.timp.pro; 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: 1655 ms average, 1411–2122 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public timp incident since monitoring began 6 days ago.
From our own checks: 100% over 6 days of checks.
1655 ms on average over the last 24 hours (1411–2122 ms).
Yes, at https://status.timp.pro.
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 timp here at once, the problem is on timp'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 timp. 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.