User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
timusnetworks.com · Cloud & developer
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 1498 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 11 | 0 | 0.0 | 1384 ms | 0 |
| Mon 13 | 0 | 0.0 | 1475 ms | 0 |
| Mon 15 | 0 | 0.0 | 1268 ms | 0 |
| Mon 18 | 0 | 0.0 | 1460 ms | 0 |
| Mon 20 | 0 | 0.0 | 1422 ms | 0 |
| Mon 22 | 0 | 0.0 | 1464 ms | 0 |
| Tue 00 | 0 | 0.0 | 1450 ms | 0 |
| Tue 02 | 0 | 0.0 | 1318 ms | 0 |
| Tue 04 | 0 | 0.0 | 1361 ms | 0 |
| Tue 06 | 0 | 0.0 | 1447 ms | 0 |
| Tue 08 | 0 | 0.0 | 1271 ms | 0 |
| Tue 10 | 0 | 0.0 | 1470 ms | 0 |
| Tue 13 | 0 | 0.0 | 1444 ms | 0 |
| Tue 15 | 0 | 0.0 | 1356 ms | 0 |
| Tue 17 | 0 | 0.0 | 1369 ms | 0 |
| Tue 19 | 0 | 0.0 | 1632 ms | 0 |
| Tue 22 | 0 | 0.0 | 1535 ms | 0 |
| Wed 00 | 0 | 0.0 | 1330 ms | 0 |
| Wed 02 | 0 | 0.0 | 1393 ms | 0 |
| Wed 04 | 0 | 0.0 | 1356 ms | 0 |
| Wed 07 | 0 | 0.0 | 1378 ms | 0 |
| Wed 09 | 0 | 0.0 | 1435 ms | 0 |
| Wed 11 | 0 | 0.0 | 1264 ms | 0 |
| Wed 13 | 0 | 0.0 | 1454 ms | 0 |
| Wed 15 | 0 | 0.0 | 1430 ms | 0 |
| Wed 17 | 0 | 0.0 | 1439 ms | 0 |
| Wed 20 | 0 | 0.0 | 1344 ms | 0 |
| Wed 22 | 0 | 0.0 | 1314 ms | 0 |
| Thu 00 | 0 | 0.0 | 1286 ms | 0 |
| Thu 02 | 0 | 0.0 | 1417 ms | 0 |
| Thu 04 | 0 | 0.0 | 1433 ms | 0 |
| Thu 06 | 0 | 0.0 | 1386 ms | 0 |
| Thu 08 | 0 | 0.0 | 1341 ms | 0 |
| Thu 10 | 0 | 0.0 | 1407 ms | 0 |
| Thu 12 | 0 | 0.0 | 1494 ms | 0 |
| Thu 15 | 0 | 0.0 | 1413 ms | 0 |
| Thu 17 | 0 | 0.0 | 1452 ms | 0 |
| Thu 19 | 0 | 0.0 | 1444 ms | 0 |
| Thu 21 | 0 | 0.0 | 1425 ms | 0 |
| Thu 23 | 0 | 0.0 | 1466 ms | 0 |
| Fri 01 | 0 | 0.0 | 1373 ms | 0 |
| Fri 03 | 0 | 0.0 | 1374 ms | 0 |
| Fri 05 | 0 | 0.0 | 1278 ms | 0 |
| Fri 07 | 0 | 0.0 | 1559 ms | 0 |
| Fri 09 | 0 | 0.0 | 1458 ms | 0 |
| Fri 11 | 0 | 0.0 | 1422 ms | 0 |
| Fri 13 | 0 | 0.0 | 1293 ms | 0 |
| Fri 15 | 0 | 0.0 | 1498 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 Timus 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 Timus goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Timus alerts to Slack, Discord or a webhook — free.
We track Timus (timusnetworks.com) as part of the Cloud & developer group. Are you looking for a trusted SASE platform built for MSPs? Timus Networks delivers secure, scalable, and simple network solutions for modern businesses.
Timus publishes an official status page at status.timusnetworks.com; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
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: 1417 ms average, 1278–1559 ms range across 11 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Timus incident since monitoring began 6 days ago.
From our own checks: 100% over 6 days of checks.
1417 ms on average over the last 24 hours (1278–1559 ms).
Yes, at https://status.timusnetworks.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Timus here at once, the problem is on Timus'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 Timus. 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.