Dispatch logo

Is Dispatch Down?

SaaSLive status, outages, and incident history

No. Dispatch is up right now.

Every monitored Dispatch system is operational as of November 14, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · every 60s

Know the moment Dispatch breaks

Dispatch is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official Dispatch status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Dispatch Status Summary

As of 17:13 UTC on 14 November 2026, Dispatch is operational. PulsAPI checked Dispatch's official status page and found 20 of 20 components operational, with no active incidents. The latest incident, "Log in Issues with iOS Field and Manager v7.1.1", was on Oct 8, 2026 and lasted 23h 14m.

Cite as: PulsAPI, “Dispatch status”, checked 14 November 2026, 17:13 UTC. https://www.pulsapi.com/services/dispatch

Dispatch Component Status

The main Dispatch systems on this page. All 20 are operational right now.

20operational
Cloud Providers and 3rd Party Providers » AWS ec2-us-east-1
Operational
Cloud Providers and 3rd Party Providers » Dashboards and Reports
Operational
Cloud Providers and 3rd Party Providers » SendGrid API
Operational

17 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Cloud Providers and 3rd Party Providers » SendGrid API v2, Cloud Providers and 3rd Party Providers » SendGrid API v3, Cloud Providers and 3rd Party Providers » SendGrid SMTP, Cloud Providers and 3rd Party Providers » Third Party Integrations and Providers, Cloud Providers and 3rd Party Providers » Twilio SMS, Corporate Website, Integration and Auxiliary APIs » Connector Integration Endpoints, Integration and Auxiliary APIs » Direct API Availability, Integration and Auxiliary APIs » Files API, Integration and Auxiliary APIs » URL Shortener Service, Notifications » Email, Notifications » Inbox, and 5 more.

See all of them free

Component statuses may change independently during partial outages.

Recent Dispatch Outages & Incidents

Incident history from the official Dispatch status page, including resolution updates.

Log in Issues with iOS Field and Manager v7.1.1Resolved Oct 8, 2026 · 23h 14mResolved

Dispatch Field v7.1.2 and Dispatch Manager v7.1.2 are now available. Users should upgrade to v7.1.2 as soon as possible. --- [2026-10-08T11:43:23.064-04:00] (monitoring) A fix has been implemented for iOS users and we are seeing users log in again via Mobile. We will continue to monitor. --- [2026-10-08T08:44:23.956-04:00] (identified) Users on iOS v7.1.1 of Field and Manager are experiencing issues logging into the mobile apps. We are releasing Field and Manager v7.1.2 to address this issue. iOS Uers who are not currently on v7.1.1 should not upgrade until v7.1.2 is made available. We will provide an update when iOS v7.1.2 can be downloaded.

Notification DelayResolved Sep 3, 2026 · 1h 34mResolved

This incident has been resolved. --- [2026-09-03T15:03:01.676-04:00] (identified) Notifications are currently delayed. We have identified the cause and are working on mitigating the impact.

Upcoming maintenance

Announced by Dispatch. Planned work, not an outage.

System maintenanceScheduled for Nov 15, 2026 · 4h 0mScheduled

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.

System maintenanceScheduled for Feb 14, 2027 · 4h 0mScheduled

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.

Dispatch Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Dispatch incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history3 days observed
Nov 12100.00% averageNov 14

Live Dispatch Outage Reports

Problems reported by engineers using Dispatch. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Dispatch problems reported yet.

Something wrong with Dispatch on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Dispatch

Dispatch posts its status at status.dispatch.me. The page covers 20 components, among them AWS ec2-us-east-1, Dashboards and Reports and SendGrid API. Past incidents and uptime for Dispatch stay on this page, which helps when you want to know how often it has trouble.

Dispatch Status FAQ

Is Dispatch down right now?

The verdict at the top of this page comes from the latest poll of the official Dispatch status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Dispatch is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Dispatch recovers.

How do I check Dispatch uptime history?

PulsAPI tracks Dispatch uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is not published yet, because a 30-day figure needs 30 days of tracked history. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Dispatch changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Dispatch outages?

PulsAPI reads the official Dispatch status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Dispatch components?

Yes. PulsAPI monitors 20 individual Dispatch components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Dispatch goes down?

Yes. Create a free account and subscribe to Dispatch: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Dispatch to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Dispatch problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Dispatch?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Dispatch plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Dispatch with the rest of your stack

4372+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services