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 1 hr ago. Last stored result reached it in 63 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 | 61 ms | 0 |
| Mon 22 | 0 | 0.0 | 250 ms | 0 |
| Tue 00 | 0 | 0.0 | 70 ms | 0 |
| Tue 02 | 0 | 0.0 | 133 ms | 0 |
| Tue 04 | 0 | 0.0 | 103 ms | 0 |
| Tue 06 | 0 | 0.0 | 182 ms | 0 |
| Tue 09 | 0 | 0.0 | 78 ms | 0 |
| Tue 11 | 0 | 0.0 | 53 ms | 0 |
| Tue 13 | 0 | 0.0 | 110 ms | 0 |
| Tue 15 | 0 | 0.0 | 114 ms | 0 |
| Tue 17 | 0 | 0.0 | 271 ms | 0 |
| Tue 20 | 0 | 0.0 | 109 ms | 0 |
| Tue 22 | 0 | 0.0 | 71 ms | 0 |
| Wed 00 | 0 | 0.0 | 293 ms | 0 |
| Wed 02 | 0 | 0.0 | 116 ms | 0 |
| Wed 05 | 0 | 0.0 | 84 ms | 0 |
| Wed 07 | 0 | 0.0 | 86 ms | 0 |
| Wed 09 | 0 | 0.0 | 80 ms | 0 |
| Wed 11 | 0 | 0.0 | 225 ms | 0 |
| Wed 14 | 0 | 0.0 | 50 ms | 0 |
| Wed 16 | 0 | 0.0 | 247 ms | 0 |
| Wed 18 | 0 | 0.0 | 122 ms | 0 |
| Wed 20 | 0 | 0.0 | 121 ms | 0 |
| Wed 22 | 0 | 0.0 | 129 ms | 0 |
| Thu 00 | 0 | 0.0 | 299 ms | 0 |
| Thu 03 | 0 | 0.0 | 109 ms | 0 |
| Thu 05 | 0 | 0.0 | 85 ms | 0 |
| Thu 07 | 0 | 0.0 | 125 ms | 0 |
| Thu 09 | 0 | 0.0 | 224 ms | 0 |
| Thu 11 | 0 | 0.0 | 88 ms | 0 |
| Thu 13 | 0 | 0.0 | 154 ms | 0 |
| Thu 15 | 0 | 0.0 | 73 ms | 0 |
| Thu 17 | 0 | 0.0 | 62 ms | 0 |
| Thu 19 | 0 | 0.0 | 380 ms | 0 |
| Thu 21 | 0 | 0.0 | 82 ms | 0 |
| Thu 23 | 0 | 0.0 | 148 ms | 0 |
| Fri 01 | 0 | 0.0 | 67 ms | 0 |
| Fri 03 | 0 | 0.0 | 208 ms | 0 |
| Fri 05 | 0 | 0.0 | 54 ms | 0 |
| Fri 07 | 0 | 0.0 | 89 ms | 0 |
| Fri 09 | 0 | 0.0 | 187 ms | 0 |
| Fri 12 | 0 | 0.0 | 388 ms | 0 |
| Fri 14 | 0 | 0.0 | 84 ms | 0 |
| Fri 16 | 0 | 0.0 | 54 ms | 0 |
| Fri 18 | 0 | 0.0 | 95 ms | 0 |
| Fri 20 | 0 | 0.0 | 84 ms | 0 |
| Fri 22 | 0 | 0.0 | 89 ms | 0 |
| Sat 00 | 0 | 0.0 | 63 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 Publicate 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 Publicate goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Publicate alerts to Slack, Discord or a webhook — free.
We track Publicate (publicate.it) as part of the Productivity group. Design & create beautiful newsletters in minutes with our powerful email builder. Our HTML email template builder allows you to export without any coding.
Publicate publishes an official status page at status.publicate.it; 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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 119 ms average, 54–388 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 Publicate incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
119 ms on average over the last 24 hours (54–388 ms).
Yes, at https://status.publicate.it.
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 Publicate here at once, the problem is on Publicate'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 Publicate. 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.