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 7 min ago. Last stored result reached it in 161 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 14 | 0 | 0.0 | 97 ms | 0 |
| Mon 16 | 0 | 0.0 | 99 ms | 0 |
| Mon 18 | 0 | 0.0 | 85 ms | 0 |
| Mon 20 | 0 | 0.0 | 171 ms | 0 |
| Mon 22 | 0 | 0.0 | 415 ms | 0 |
| Tue 01 | 0 | 0.0 | 207 ms | 0 |
| Tue 03 | 0 | 0.0 | 194 ms | 0 |
| Tue 05 | 0 | 0.0 | 86 ms | 0 |
| Tue 07 | 0 | 0.0 | 105 ms | 0 |
| Tue 09 | 0 | 0.0 | 189 ms | 0 |
| Tue 11 | 0 | 0.0 | 151 ms | 0 |
| Tue 13 | 0 | 0.0 | 395 ms | 0 |
| Tue 16 | 0 | 0.0 | 276 ms | 0 |
| Tue 18 | 0 | 0.0 | 310 ms | 0 |
| Tue 20 | 0 | 0.0 | 79 ms | 0 |
| Tue 22 | 0 | 0.0 | 192 ms | 0 |
| Wed 01 | 0 | 0.0 | 103 ms | 0 |
| Wed 03 | 0 | 0.0 | 153 ms | 0 |
| Wed 05 | 0 | 0.0 | 291 ms | 0 |
| Wed 07 | 0 | 0.0 | 132 ms | 0 |
| Wed 10 | 0 | 0.0 | 345 ms | 0 |
| Wed 12 | 0 | 0.0 | 141 ms | 0 |
| Wed 14 | 0 | 0.0 | 174 ms | 0 |
| Wed 16 | 0 | 0.0 | 128 ms | 0 |
| Wed 18 | 0 | 0.0 | 148 ms | 0 |
| Wed 20 | 0 | 0.0 | 395 ms | 0 |
| Wed 23 | 0 | 0.0 | 119 ms | 0 |
| Thu 01 | 0 | 0.0 | 345 ms | 0 |
| Thu 03 | 0 | 0.0 | 198 ms | 0 |
| Thu 05 | 0 | 0.0 | 191 ms | 0 |
| Thu 07 | 0 | 0.0 | 135 ms | 0 |
| Thu 09 | 0 | 0.0 | 115 ms | 0 |
| Thu 11 | 0 | 0.0 | 230 ms | 0 |
| Thu 13 | 0 | 0.0 | 157 ms | 0 |
| Thu 15 | 0 | 0.0 | 358 ms | 0 |
| Thu 17 | 0 | 0.0 | 146 ms | 0 |
| Thu 19 | 0 | 0.0 | 94 ms | 0 |
| Thu 21 | 0 | 0.0 | 229 ms | 0 |
| Thu 23 | 0 | 0.0 | 335 ms | 0 |
| Fri 00 | 0 | 0.0 | 98 ms | 0 |
| Fri 02 | 0 | 0.0 | 217 ms | 0 |
| Fri 05 | 0 | 0.0 | 125 ms | 0 |
| Fri 07 | 0 | 0.0 | 158 ms | 0 |
| Fri 09 | 0 | 0.0 | 138 ms | 0 |
| Fri 11 | 0 | 0.0 | 88 ms | 0 |
| Fri 13 | 0 | 0.0 | 343 ms | 0 |
| Fri 15 | 0 | 0.0 | 128 ms | 0 |
| Fri 17 | 0 | 0.0 | 217 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 Envoke 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 Envoke goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Envoke alerts to Slack, Discord or a webhook — free.
We track Envoke (envoke.com) as part of the Productivity group. Envoke is a Canadian email marketing and communications software. Engage stakeholders with professional emails without risking your organization's reputation.
Envoke publishes an official status page at status.envoke.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: 186 ms average, 88–343 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 Envoke incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
186 ms on average over the last 24 hours (88–343 ms).
Yes, at https://status.envoke.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 Envoke here at once, the problem is on Envoke'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 Envoke. 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.