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 2 hr ago. Last stored result reached it in 887 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 13 | 0 | 0.0 | 727 ms | 0 |
| Mon 15 | 0 | 0.0 | 896 ms | 0 |
| Mon 18 | 0 | 0.0 | 828 ms | 0 |
| Mon 20 | 0 | 0.0 | 1010 ms | 0 |
| Mon 22 | 0 | 0.0 | 876 ms | 0 |
| Tue 00 | 0 | 0.0 | 932 ms | 0 |
| Tue 02 | 0 | 0.0 | 1472 ms | 0 |
| Tue 04 | 0 | 0.0 | 1028 ms | 0 |
| Tue 06 | 0 | 0.0 | 748 ms | 0 |
| Tue 08 | 0 | 0.0 | 900 ms | 0 |
| Tue 10 | 0 | 0.0 | 839 ms | 0 |
| Tue 12 | 0 | 0.0 | 849 ms | 0 |
| Tue 15 | 0 | 0.0 | 877 ms | 0 |
| Tue 17 | 0 | 0.0 | 1069 ms | 0 |
| Tue 19 | 0 | 0.0 | 1052 ms | 0 |
| Tue 22 | 0 | 0.0 | 981 ms | 0 |
| Wed 00 | 0 | 0.0 | 807 ms | 0 |
| Wed 02 | 0 | 0.0 | 788 ms | 0 |
| Wed 04 | 0 | 0.0 | 1322 ms | 0 |
| Wed 06 | 0 | 0.0 | 863 ms | 0 |
| Wed 09 | 0 | 0.0 | 938 ms | 0 |
| Wed 11 | 0 | 0.0 | 873 ms | 0 |
| Wed 13 | 0 | 0.0 | 746 ms | 0 |
| Wed 15 | 0 | 0.0 | 776 ms | 0 |
| Wed 17 | 0 | 0.0 | 2752 ms | 0 |
| Wed 20 | 0 | 0.0 | 2482 ms | 0 |
| Wed 21 | 0 | 0.0 | 1397 ms | 0 |
| Wed 23 | 0 | 0.0 | 683 ms | 0 |
| Thu 01 | 0 | 0.0 | 873 ms | 0 |
| Thu 03 | 0 | 0.0 | 714 ms | 0 |
| Thu 05 | 0 | 0.0 | 700 ms | 0 |
| Thu 07 | 0 | 0.0 | 820 ms | 0 |
| Thu 09 | 0 | 0.0 | 795 ms | 0 |
| Thu 12 | 0 | 0.0 | 793 ms | 0 |
| Thu 14 | 0 | 0.0 | 861 ms | 0 |
| Thu 16 | 0 | 0.0 | 714 ms | 0 |
| Thu 18 | 0 | 0.0 | 917 ms | 0 |
| Thu 20 | 0 | 0.0 | 1675 ms | 0 |
| Thu 22 | 0 | 0.0 | 1128 ms | 0 |
| Fri 00 | 0 | 0.0 | 4804 ms | 0 |
| Fri 02 | 0 | 0.0 | 1341 ms | 0 |
| Fri 04 | 0 | 0.0 | 2260 ms | 0 |
| Fri 06 | 0 | 0.0 | 695 ms | 0 |
| Fri 08 | 0 | 0.0 | 713 ms | 0 |
| Fri 10 | 0 | 0.0 | 853 ms | 0 |
| Fri 11 | 0 | 0.0 | 703 ms | 0 |
| Fri 13 | 0 | 0.0 | 1304 ms | 0 |
| Fri 15 | 0 | 0.0 | 887 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 PostGrid 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 PostGrid goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send PostGrid alerts to Slack, Discord or a webhook — free.
We track PostGrid (postgrid.com) as part of the Productivity group. PostGrid provides companies a platform and API service for automating transactional mails, marketing direct mails and address verification at scale.
PostGrid publishes an official status page at status.postgrid.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: 1461 ms average, 695–4804 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 PostGrid incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
1461 ms on average over the last 24 hours (695–4804 ms).
Yes, at https://status.postgrid.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 PostGrid here at once, the problem is on PostGrid'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 PostGrid. 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.