User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
coveragebook.com · 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 5 min ago. Last stored result reached it in 39 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 17 | 0 | 0.0 | 66 ms | 0 |
| Mon 19 | 0 | 0.0 | 182 ms | 0 |
| Mon 22 | 0 | 0.0 | 66 ms | 0 |
| Tue 00 | 0 | 0.0 | 241 ms | 0 |
| Tue 02 | 0 | 0.0 | 81 ms | 0 |
| Tue 04 | 0 | 0.0 | 42 ms | 0 |
| Tue 06 | 0 | 0.0 | 132 ms | 0 |
| Tue 08 | 0 | 0.0 | 180 ms | 0 |
| Tue 10 | 0 | 0.0 | 109 ms | 0 |
| Tue 12 | 0 | 0.0 | 191 ms | 0 |
| Tue 15 | 0 | 0.0 | 218 ms | 0 |
| Tue 17 | 0 | 0.0 | 150 ms | 0 |
| Tue 19 | 0 | 0.0 | 194 ms | 0 |
| Tue 21 | 0 | 0.0 | 91 ms | 0 |
| Wed 00 | 0 | 0.0 | 30 ms | 0 |
| Wed 02 | 0 | 0.0 | 197 ms | 0 |
| Wed 04 | 0 | 0.0 | 60 ms | 0 |
| Wed 06 | 0 | 0.0 | 236 ms | 0 |
| Wed 08 | 0 | 0.0 | 202 ms | 0 |
| Wed 11 | 0 | 0.0 | 70 ms | 0 |
| Wed 13 | 0 | 0.0 | 336 ms | 0 |
| Wed 15 | 0 | 0.0 | 124 ms | 0 |
| Wed 17 | 0 | 0.0 | 102 ms | 0 |
| Wed 19 | 0 | 0.0 | 197 ms | 0 |
| Wed 21 | 0 | 0.0 | 137 ms | 0 |
| Wed 23 | 0 | 0.0 | 164 ms | 0 |
| Thu 02 | 0 | 0.0 | 125 ms | 0 |
| Thu 04 | 0 | 0.0 | 50 ms | 0 |
| Thu 06 | 0 | 0.0 | 226 ms | 0 |
| Thu 08 | 0 | 0.0 | 270 ms | 0 |
| Thu 10 | 0 | 0.0 | 110 ms | 0 |
| Thu 12 | 0 | 0.0 | 210 ms | 0 |
| Thu 14 | 0 | 0.0 | 103 ms | 0 |
| Thu 16 | 0 | 0.0 | 202 ms | 0 |
| Thu 18 | 0 | 0.0 | 34 ms | 0 |
| Thu 20 | 0 | 0.0 | 47 ms | 0 |
| Thu 22 | 0 | 0.0 | 170 ms | 0 |
| Fri 00 | 0 | 0.0 | 160 ms | 0 |
| Fri 02 | 0 | 0.0 | 229 ms | 0 |
| Fri 04 | 0 | 0.0 | 63 ms | 0 |
| Fri 06 | 0 | 0.0 | 201 ms | 0 |
| Fri 07 | 0 | 0.0 | 172 ms | 0 |
| Fri 09 | 0 | 0.0 | 135 ms | 0 |
| Fri 10 | 0 | 0.0 | 92 ms | 0 |
| Fri 11 | 0 | 0.0 | 145 ms | 0 |
| Fri 13 | 0 | 0.0 | 166 ms | 0 |
| Fri 15 | 0 | 0.0 | 75 ms | 0 |
| Fri 17 | 0 | 0.0 | 39 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 CoverageBook 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 CoverageBook goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send CoverageBook alerts to Slack, Discord or a webhook — free.
CoverageBook, at coveragebook.com, is one of the Productivity services we monitor. Over 18,753 PR professionals in 3,000 PR teams use CoverageBook reports to showcase and measure the impact of their work. In style. Sign up for a free trial.
CoverageBook publishes an official status page at status.coveragebook.com; when we can read it, its incident level is folded into the status shown here.
Common problems for 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: 124 ms average, 34–229 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public CoverageBook incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
124 ms on average over the last 24 hours (34–229 ms).
Yes, at https://status.coveragebook.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 CoverageBook here at once, the problem is on CoverageBook'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 CoverageBook. 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.