User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Productivity
Is Dyspatch down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → dyspatch.io—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 2 hr ago. Last stored result reached it in 129 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 07 | 0 | 0.0 | 150 ms | 0 |
| Mon 09 | 0 | 0.0 | 132 ms | 0 |
| Mon 11 | 0 | 0.0 | 92 ms | 0 |
| Mon 13 | 0 | 0.0 | 119 ms | 0 |
| Mon 15 | 0 | 0.0 | 253 ms | 0 |
| Mon 17 | 0 | 0.0 | 160 ms | 0 |
| Mon 20 | 0 | 0.0 | 141 ms | 0 |
| Mon 22 | 0 | 0.0 | 126 ms | 0 |
| Tue 00 | 0 | 0.0 | 123 ms | 0 |
| Tue 02 | 0 | 0.0 | 142 ms | 0 |
| Tue 04 | 0 | 0.0 | 125 ms | 0 |
| Tue 06 | 0 | 0.0 | 124 ms | 0 |
| Tue 08 | 0 | 0.0 | 105 ms | 0 |
| Tue 10 | 0 | 0.0 | 164 ms | 0 |
| Tue 12 | 0 | 0.0 | 207 ms | 0 |
| Tue 15 | 0 | 0.0 | 129 ms | 0 |
| Tue 17 | 0 | 0.0 | 147 ms | 0 |
| Tue 19 | 0 | 0.0 | 95 ms | 0 |
| Tue 21 | 0 | 0.0 | 153 ms | 0 |
| Wed 00 | 0 | 0.0 | 110 ms | 0 |
| Wed 02 | 0 | 0.0 | 168 ms | 0 |
| Wed 04 | 0 | 0.0 | 127 ms | 0 |
| Wed 06 | 0 | 0.0 | 135 ms | 0 |
| Wed 09 | 0 | 0.0 | 68 ms | 0 |
| Wed 11 | 0 | 0.0 | 130 ms | 0 |
| Wed 13 | 0 | 0.0 | 163 ms | 0 |
| Wed 15 | 0 | 0.0 | 80 ms | 0 |
| Wed 17 | 0 | 0.0 | 158 ms | 0 |
| Wed 19 | 0 | 0.0 | 112 ms | 0 |
| Wed 22 | 0 | 0.0 | 148 ms | 0 |
| Thu 00 | 0 | 0.0 | 104 ms | 0 |
| Thu 02 | 0 | 0.0 | 131 ms | 0 |
| Thu 04 | 0 | 0.0 | 220 ms | 0 |
| Thu 06 | 0 | 0.0 | 269 ms | 0 |
| Thu 08 | 0 | 0.0 | 118 ms | 0 |
| Thu 10 | 0 | 0.0 | 98 ms | 0 |
| Thu 12 | 0 | 0.0 | 119 ms | 0 |
| Thu 14 | 0 | 0.0 | 122 ms | 0 |
| Thu 16 | 0 | 0.0 | 154 ms | 0 |
| Thu 18 | 0 | 0.0 | 114 ms | 0 |
| Thu 20 | 0 | 0.0 | 200 ms | 0 |
| Thu 22 | 0 | 0.0 | 119 ms | 0 |
| Fri 00 | 0 | 0.0 | 125 ms | 0 |
| Fri 03 | 0 | 0.0 | 262 ms | 0 |
| Fri 05 | 0 | 0.0 | 162 ms | 0 |
| Fri 07 | 0 | 0.0 | 95 ms | 0 |
| Fri 09 | 0 | 0.0 | 159 ms | 0 |
| Fri 11 | 0 | 0.0 | 129 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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.
Embed this status: free live Dyspatch badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Dyspatch yet. Outages of 10 minutes or more get their own page here.
Having trouble with Dyspatch?
One report per service every 10 minutes from this network. No account.
Follow Dyspatch
Get an email when Dyspatch goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Dyspatch alerts to Slack, Discord or a webhook — free.
About Dyspatch
Dyspatch, at dyspatch.io, is one of the Productivity services we monitor. Build, collaborate on, and localize on-brand email templates without code. Trusted by Canva, Culture Amp, and 300+ global teams. See how it works.
Dyspatch publishes an official status page at status.dyspatch.io; 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: 150 ms average, 95–262 ms range across 12 successful checks.
Questions
Is Dyspatch down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Dyspatch last down?
We have not recorded a public Dyspatch incident since monitoring began 8 days ago.
What is Dyspatch's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Dyspatch respond?
150 ms on average over the last 24 hours (95–262 ms).
Does Dyspatch have an official status page?
Yes, at https://status.dyspatch.io.
Dyspatch not working for me but the status is fine. What now?
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 Dyspatch here at once, the problem is on Dyspatch'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 Dyspatch. 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.