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 247 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 11 | 0 | 0.0 | 161 ms | 0 |
| Mon 13 | 0 | 0.0 | 207 ms | 0 |
| Mon 15 | 0 | 0.0 | 158 ms | 0 |
| Mon 18 | 0 | 0.0 | 363 ms | 0 |
| Mon 20 | 0 | 0.0 | 200 ms | 0 |
| Mon 22 | 0 | 0.0 | 183 ms | 0 |
| Tue 00 | 0 | 0.0 | 202 ms | 0 |
| Tue 02 | 0 | 0.0 | 237 ms | 0 |
| Tue 04 | 0 | 0.0 | 222 ms | 0 |
| Tue 06 | 0 | 0.0 | 232 ms | 0 |
| Tue 09 | 0 | 0.0 | 184 ms | 0 |
| Tue 11 | 0 | 0.0 | 172 ms | 0 |
| Tue 13 | 0 | 0.0 | 209 ms | 0 |
| Tue 15 | 0 | 0.0 | 144 ms | 0 |
| Tue 17 | 0 | 0.0 | 51 ms | 0 |
| Tue 20 | 0 | 0.0 | 221 ms | 0 |
| Tue 22 | 0 | 0.0 | 89 ms | 0 |
| Wed 00 | 0 | 0.0 | 145 ms | 0 |
| Wed 02 | 0 | 0.0 | 220 ms | 0 |
| Wed 05 | 0 | 0.0 | 191 ms | 0 |
| Wed 07 | 0 | 0.0 | 176 ms | 0 |
| Wed 09 | 0 | 0.0 | 214 ms | 0 |
| Wed 11 | 0 | 0.0 | 167 ms | 0 |
| Wed 14 | 0 | 0.0 | 199 ms | 0 |
| Wed 16 | 0 | 0.0 | 198 ms | 0 |
| Wed 18 | 0 | 0.0 | 254 ms | 0 |
| Wed 20 | 0 | 0.0 | 239 ms | 0 |
| Wed 22 | 0 | 0.0 | 236 ms | 0 |
| Thu 00 | 0 | 0.0 | 235 ms | 0 |
| Thu 03 | 0 | 0.0 | 244 ms | 0 |
| Thu 05 | 0 | 0.0 | 109 ms | 0 |
| Thu 07 | 0 | 0.0 | 223 ms | 0 |
| Thu 09 | 0 | 0.0 | 192 ms | 0 |
| Thu 11 | 0 | 0.0 | 195 ms | 0 |
| Thu 13 | 0 | 0.0 | 196 ms | 0 |
| Thu 15 | 0 | 0.0 | 244 ms | 0 |
| Thu 17 | 0 | 0.0 | 225 ms | 0 |
| Thu 19 | 0 | 0.0 | 229 ms | 0 |
| Thu 21 | 0 | 0.0 | 223 ms | 0 |
| Thu 23 | 0 | 0.0 | 146 ms | 0 |
| Fri 01 | 0 | 0.0 | 245 ms | 0 |
| Fri 03 | 0 | 0.0 | 230 ms | 0 |
| Fri 05 | 0 | 0.0 | 204 ms | 0 |
| Fri 07 | 0 | 0.0 | 160 ms | 0 |
| Fri 09 | 0 | 0.0 | 218 ms | 0 |
| Fri 11 | 0 | 0.0 | 156 ms | 0 |
| Fri 13 | 0 | 0.0 | 194 ms | 0 |
| Fri 15 | 0 | 0.0 | 247 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 Polymail 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 Polymail goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Polymail alerts to Slack, Discord or a webhook — free.
Polymail is listed in our Productivity category and checked at polymail.io. Turn your inbox into a control center for getting work done. Polymail combines tracking, follow-ups, and scheduling directly inside email for founders and operators.
Polymail publishes an official status page at status.polymail.io; 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: 208 ms average, 146–247 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 Polymail incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
208 ms on average over the last 24 hours (146–247 ms).
Yes, at https://status.polymail.io.
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 Polymail here at once, the problem is on Polymail'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 Polymail. 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.