User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Utilities
The site answers but blocks automated checks, so we rely on user reports and the official status. User reports are near the baseline.
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.
Our checks can't reach Tidbyt right now
Tidbyt is blocking or timing out our automated checks, so we can't test it directly. We still count user reports and watch the official status page.
Last checked 2 hr ago. Last stored result reached it in 19 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 07 | 0 | 0.0 | 23 ms | 0 |
| Tue 09 | 0 | 0.0 | 19 ms | 0 |
| Tue 11 | 0 | 0.0 | 11 ms | 0 |
| Tue 13 | 0 | 0.0 | 120 ms | 0 |
| Tue 15 | 0 | 0.0 | 218 ms | 0 |
| Tue 18 | 0 | 0.0 | 11 ms | 0 |
| Tue 20 | 0 | 0.0 | 201 ms | 0 |
| Tue 22 | 0 | 0.0 | 52 ms | 0 |
| Wed 00 | 0 | 0.0 | 9 ms | 0 |
| Wed 03 | 0 | 0.0 | 13 ms | 0 |
| Wed 05 | 0 | 0.0 | 16 ms | 0 |
| Wed 07 | 0 | 0.0 | 12 ms | 0 |
| Wed 09 | 0 | 0.0 | 12 ms | 0 |
| Wed 12 | 0 | 0.0 | 7 ms | 0 |
| Wed 14 | 0 | 0.0 | 17 ms | 0 |
| Wed 16 | 0 | 0.0 | 143 ms | 0 |
| Wed 18 | 0 | 0.0 | 202 ms | 0 |
| Wed 20 | 0 | 0.0 | 144 ms | 0 |
| Wed 22 | 0 | 0.0 | 29 ms | 0 |
| Thu 01 | 0 | 0.0 | 13 ms | 0 |
| Thu 03 | 0 | 0.0 | 33 ms | 0 |
| Thu 05 | 0 | 0.0 | 25 ms | 0 |
| Thu 07 | 0 | 0.0 | 17 ms | 0 |
| Thu 09 | 0 | 0.0 | 107 ms | 0 |
| Thu 11 | 0 | 0.0 | 14 ms | 0 |
| Thu 13 | 0 | 0.0 | 14 ms | 0 |
| Thu 15 | 0 | 0.0 | 145 ms | 0 |
| Thu 17 | 0 | 0.0 | 194 ms | 0 |
| Thu 19 | 0 | 0.0 | 4167 ms | 0 |
| Thu 21 | 0 | 0.0 | 111 ms | 0 |
| Thu 23 | 0 | 0.0 | 119 ms | 0 |
| Fri 01 | 0 | 0.0 | 194 ms | 0 |
| Fri 04 | 0 | 0.0 | 19 ms | 0 |
| Fri 06 | 0 | 0.0 | 14 ms | 0 |
| Fri 08 | 0 | 0.0 | 101 ms | 0 |
| Fri 10 | 0 | 0.0 | 12 ms | 0 |
| Fri 12 | 0 | 0.0 | 104 ms | 0 |
| Fri 14 | 0 | 0.0 | 17 ms | 0 |
| Fri 16 | 0 | 0.0 | 19 ms | 0 |
| Fri 18 | 0 | 0.0 | 42 ms | 0 |
| Fri 20 | 0 | 0.0 | 245 ms | 0 |
| Fri 22 | 0 | 0.0 | 60 ms | 0 |
| Sat 00 | 0 | 0.0 | 28 ms | 0 |
| Sat 02 | 0 | 0.0 | 13 ms | 0 |
| Sat 03 | 0 | 0.0 | 164 ms | 0 |
| Sat 05 | 0 | 0.0 | 41 ms | 0 |
| Sat 07 | 0 | 0.0 | 13 ms | 0 |
| Sat 08 | 0 | 0.0 | 19 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 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Tidbyt 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 Tidbyt goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Tidbyt alerts to Slack, Discord or a webhook — free.
Tidbyt is listed in our Utilities category and checked at tidbyt.com. Tidbyt keeps you updated on transit, weather and more. Leave your phone in your pocket.
Tidbyt publishes an official status page at status.tidbyt.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with utilities services: outage maps and bill-pay pages slowing or failing during storms and peak demand, and account sign-in problems.
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: 70 ms average, 11–245 ms range across 16 successful checks.
The site answers but blocks automated checks, so we rely on user reports and the official status. User reports are near the baseline.
We have not recorded a public Tidbyt incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
70 ms on average over the last 24 hours (11–245 ms).
Yes, at https://status.tidbyt.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For utilities services, watch for outage maps and bill-pay pages slowing or failing during storms and peak demand, and account sign-in problems. If many people report Tidbyt here at once, the problem is on Tidbyt'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 Tidbyt. 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.