User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
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 13 min ago. Last stored result reached it in 370 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 | 307 ms | 0 |
| Mon 22 | 0 | 0.0 | 133 ms | 0 |
| Tue 00 | 0 | 0.0 | 258 ms | 0 |
| Tue 02 | 0 | 0.0 | 233 ms | 0 |
| Tue 04 | 0 | 0.0 | 442 ms | 0 |
| Tue 06 | 0 | 0.0 | 470 ms | 0 |
| Tue 08 | 0 | 0.0 | 401 ms | 0 |
| Tue 11 | 0 | 0.0 | 328 ms | 0 |
| Tue 13 | 0 | 0.0 | 303 ms | 0 |
| Tue 15 | 0 | 0.0 | 164 ms | 0 |
| Tue 17 | 0 | 0.0 | 382 ms | 0 |
| Tue 20 | 0 | 0.0 | 340 ms | 0 |
| Tue 22 | 0 | 0.0 | 585 ms | 0 |
| Wed 00 | 0 | 0.0 | 208 ms | 0 |
| Wed 02 | 0 | 0.0 | 254 ms | 0 |
| Wed 05 | 0 | 0.0 | 236 ms | 0 |
| Wed 07 | 0 | 0.0 | 612 ms | 0 |
| Wed 09 | 0 | 0.0 | 251 ms | 0 |
| Wed 11 | 0 | 0.0 | 126 ms | 0 |
| Wed 13 | 0 | 0.0 | 355 ms | 0 |
| Wed 15 | 0 | 0.0 | 272 ms | 0 |
| Wed 17 | 0 | 0.0 | 286 ms | 0 |
| Wed 20 | 0 | 0.0 | 603 ms | 0 |
| Wed 22 | 0 | 0.0 | 445 ms | 0 |
| Thu 00 | 0 | 0.0 | 344 ms | 0 |
| Thu 02 | 0 | 0.0 | 335 ms | 0 |
| Thu 03 | 0 | 0.0 | 363 ms | 0 |
| Thu 05 | 0 | 0.0 | 642 ms | 0 |
| Thu 07 | 0 | 0.0 | 193 ms | 0 |
| Thu 09 | 0 | 0.0 | 422 ms | 0 |
| Thu 11 | 0 | 0.0 | 306 ms | 0 |
| Thu 13 | 0 | 0.0 | 291 ms | 0 |
| Thu 15 | 0 | 0.0 | 557 ms | 0 |
| Thu 17 | 0 | 0.0 | 396 ms | 0 |
| Thu 19 | 0 | 0.0 | 352 ms | 0 |
| Thu 21 | 0 | 0.0 | 242 ms | 0 |
| Thu 23 | 0 | 0.0 | 187 ms | 0 |
| Fri 01 | 0 | 0.0 | 162 ms | 0 |
| Fri 03 | 0 | 0.0 | 406 ms | 0 |
| Fri 05 | 0 | 0.0 | 258 ms | 0 |
| Fri 08 | 0 | 0.0 | 187 ms | 0 |
| Fri 09 | 0 | 0.0 | 384 ms | 0 |
| Fri 11 | 0 | 0.0 | 335 ms | 0 |
| Fri 13 | 0 | 0.0 | 222 ms | 0 |
| Fri 15 | 0 | 0.0 | 255 ms | 0 |
| Fri 17 | 0 | 0.0 | 301 ms | 0 |
| Fri 19 | 0 | 0.0 | 443 ms | 0 |
| Fri 21 | 0 | 0.0 | 341 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Driftrock 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 Driftrock goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Driftrock alerts to Slack, Discord or a webhook — free.
Driftrock is listed in our Productivity category and checked at driftrock.com. For automotive marketers seeking a cost-effective way to increase lead volume, improve lead quality, and measure results, Driftrock is an all-in-one lead generation platform that drives more higher-quality leads and boosts vehicle sales.
Driftrock publishes an official status page at status.driftrock.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with productivity services: files not syncing, editors not loading, and sign-in problems.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 286 ms average, 76–443 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Driftrock incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
286 ms on average over the last 24 hours (76–443 ms).
Yes, at https://status.driftrock.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For productivity services, watch for files not syncing, editors not loading, and sign-in problems. If many people report Driftrock here at once, the problem is on Driftrock'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 Driftrock. 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.