User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
dispatch.me · Cloud & developer
Is Dispatch 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 → dispatch.me—
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 1 hr ago. Last stored result reached it in 46 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 04 | 0 | 0.0 | 120 ms | 0 |
| Mon 06 | 0 | 0.0 | 104 ms | 0 |
| Mon 09 | 0 | 0.0 | 77 ms | 0 |
| Mon 11 | 0 | 0.0 | 70 ms | 0 |
| Mon 13 | 0 | 0.0 | 94 ms | 0 |
| Mon 15 | 0 | 0.0 | 53 ms | 0 |
| Mon 17 | 0 | 0.0 | 47 ms | 0 |
| Mon 19 | 0 | 0.0 | 30 ms | 0 |
| Mon 21 | 0 | 0.0 | 35 ms | 0 |
| Mon 23 | 0 | 0.0 | 49 ms | 0 |
| Tue 01 | 0 | 0.0 | 73 ms | 0 |
| Tue 03 | 0 | 0.0 | 60 ms | 0 |
| Tue 06 | 0 | 0.0 | 22 ms | 0 |
| Tue 08 | 0 | 0.0 | 67 ms | 0 |
| Tue 10 | 0 | 0.0 | 47 ms | 0 |
| Tue 12 | 0 | 0.0 | 62 ms | 0 |
| Tue 14 | 0 | 0.0 | 51 ms | 0 |
| Tue 16 | 0 | 0.0 | 88 ms | 0 |
| Tue 19 | 0 | 0.0 | 30 ms | 0 |
| Tue 21 | 0 | 0.0 | 46 ms | 0 |
| Tue 23 | 0 | 0.0 | 54 ms | 0 |
| Wed 01 | 0 | 0.0 | 43 ms | 0 |
| Wed 04 | 0 | 0.0 | 52 ms | 0 |
| Wed 06 | 0 | 0.0 | 81 ms | 0 |
| Wed 08 | 0 | 0.0 | 84 ms | 0 |
| Wed 10 | 0 | 0.0 | 65 ms | 0 |
| Wed 13 | 0 | 0.0 | 59 ms | 0 |
| Wed 15 | 0 | 0.0 | 134 ms | 0 |
| Wed 17 | 0 | 0.0 | 64 ms | 0 |
| Wed 19 | 0 | 0.0 | 12 ms | 0 |
| Wed 21 | 0 | 0.0 | 50 ms | 0 |
| Wed 23 | 0 | 0.0 | 52 ms | 0 |
| Thu 01 | 0 | 0.0 | 52 ms | 0 |
| Thu 03 | 0 | 0.0 | 47 ms | 0 |
| Thu 06 | 0 | 0.0 | 83 ms | 0 |
| Thu 08 | 0 | 0.0 | 46 ms | 0 |
| Thu 10 | 0 | 0.0 | 52 ms | 0 |
| Thu 12 | 0 | 0.0 | 55 ms | 0 |
| Thu 14 | 0 | 0.0 | 52 ms | 0 |
| Thu 16 | 0 | 0.0 | 111 ms | 0 |
| Thu 18 | 0 | 0.0 | 141 ms | 0 |
| Thu 20 | 0 | 0.0 | 25 ms | 0 |
| Thu 21 | 0 | 0.0 | 99 ms | 0 |
| Thu 23 | 0 | 0.0 | 14 ms | 0 |
| Fri 01 | 0 | 0.0 | 56 ms | 0 |
| Fri 03 | 0 | 0.0 | 53 ms | 0 |
| Fri 05 | 0 | 0.0 | 55 ms | 0 |
| Fri 07 | 0 | 0.0 | 46 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 Dispatch badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
This week
Planned maintenance
System maintenance
The Dispatch system will be undergoing scheduled system maintenance beginning at 12AM Eastern. During this time, access to our Mobile Apps, Work, and Manage web platforms will be affected. Thank you for your patience.
Announced by Dispatch · source
Planned maintenance is not an outage. Times and wording are the vendor’s own. Outage Weather →
Past outages
No outages on record for Dispatch yet. Outages of 10 minutes or more get their own page here.
Having trouble with Dispatch?
One report per service every 10 minutes from this network. No account.
Follow Dispatch
Get an email when Dispatch goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Dispatch alerts to Slack, Discord or a webhook — free.
About Dispatch
We track Dispatch (dispatch.me) as part of the Cloud & developer group. Connect contractors, customers, and service operations with field service dispatch software that provides real-time visibility from acceptance to completion.
Dispatch publishes an official status page at status.dispatch.me; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
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: 60 ms average, 12–141 ms range across 13 successful checks.
Questions
Is Dispatch down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Dispatch last down?
We have not recorded a public Dispatch incident since monitoring began 8 days ago.
What is Dispatch's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Dispatch respond?
60 ms on average over the last 24 hours (12–141 ms).
Does Dispatch have an official status page?
Yes, at https://status.dispatch.me.
Dispatch 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 cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Dispatch here at once, the problem is on Dispatch'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 Dispatch. 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.