User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
dbdtwitch.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 45 min ago. Last stored result reached it in 175 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 20 | 0 | 0.0 | 470 ms | 0 |
| Mon 23 | 0 | 0.0 | 100 ms | 0 |
| Tue 01 | 0 | 0.0 | 486 ms | 0 |
| Tue 03 | 0 | 0.0 | 193 ms | 0 |
| Tue 05 | 0 | 0.0 | 160 ms | 0 |
| Tue 07 | 0 | 0.0 | 589 ms | 0 |
| Tue 09 | 0 | 0.0 | 175 ms | 0 |
| Tue 11 | 0 | 0.0 | 174 ms | 0 |
| Tue 13 | 0 | 0.0 | 350 ms | 0 |
| Tue 16 | 0 | 0.0 | 131 ms | 0 |
| Tue 18 | 0 | 0.0 | 37 ms | 0 |
| Tue 20 | 0 | 0.0 | 191 ms | 0 |
| Tue 22 | 0 | 0.0 | 170 ms | 0 |
| Wed 01 | 0 | 0.0 | 405 ms | 0 |
| Wed 03 | 0 | 0.0 | 188 ms | 0 |
| Wed 05 | 0 | 0.0 | 347 ms | 0 |
| Wed 07 | 0 | 0.0 | 212 ms | 0 |
| Wed 10 | 0 | 0.0 | 356 ms | 0 |
| Wed 12 | 0 | 0.0 | 160 ms | 0 |
| Wed 14 | 0 | 0.0 | 160 ms | 0 |
| Wed 16 | 0 | 0.0 | 429 ms | 0 |
| Wed 18 | 0 | 0.0 | 217 ms | 0 |
| Wed 20 | 0 | 0.0 | 301 ms | 0 |
| Wed 23 | 0 | 0.0 | 181 ms | 0 |
| Thu 01 | 0 | 0.0 | 350 ms | 0 |
| Thu 03 | 0 | 0.0 | 174 ms | 0 |
| Thu 05 | 0 | 0.0 | 680 ms | 0 |
| Thu 07 | 0 | 0.0 | 406 ms | 0 |
| Thu 09 | 0 | 0.0 | 367 ms | 0 |
| Thu 11 | 0 | 0.0 | 98 ms | 0 |
| Thu 13 | 0 | 0.0 | 333 ms | 0 |
| Thu 15 | 0 | 0.0 | 250 ms | 0 |
| Thu 17 | 0 | 0.0 | 192 ms | 0 |
| Thu 19 | 0 | 0.0 | 409 ms | 0 |
| Thu 21 | 0 | 0.0 | 195 ms | 0 |
| Thu 23 | 0 | 0.0 | 429 ms | 0 |
| Fri 00 | 0 | 0.0 | 157 ms | 0 |
| Fri 02 | 0 | 0.0 | 317 ms | 0 |
| Fri 05 | 0 | 0.0 | 392 ms | 0 |
| Fri 07 | 0 | 0.0 | 149 ms | 0 |
| Fri 09 | 0 | 0.0 | 98 ms | 0 |
| Fri 11 | 0 | 0.0 | 349 ms | 0 |
| Fri 13 | 0 | 0.0 | 378 ms | 0 |
| Fri 15 | 0 | 0.0 | 152 ms | 0 |
| Fri 17 | 0 | 0.0 | 184 ms | 0 |
| Fri 18 | 0 | 0.0 | 172 ms | 0 |
| Fri 19 | 0 | 0.0 | 396 ms | 0 |
| Fri 21 | 0 | 0.0 | 175 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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Dbdtwitch 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 Dbdtwitch goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Dbdtwitch alerts to Slack, Discord or a webhook — free.
We track Dbdtwitch (dbdtwitch.com) as part of the Cloud & developer group. Twitch perks overlay for Dead by Daylight
Dbdtwitch publishes an official status page at status.dbdtwitch.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 258 ms average, 98–429 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 Dbdtwitch incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
258 ms on average over the last 24 hours (98–429 ms).
Yes, at https://status.dbdtwitch.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 Dbdtwitch here at once, the problem is on Dbdtwitch'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 Dbdtwitch. 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.