Dispatchit Outage History

Dispatchit is up right now

Pingoru has recorded 14 incidents for Dispatchit: 2 in the last 12 months and 0 in the last 90 days.

Source: status.dispatchit.com

14incidents recorded
2last 12 months
0last 90 days
14 hourstypical duration
Incidents per month
012MayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%MayJunJulAugSepOctNov0%
Pingoru began tracking Dispatchit in May 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
May 2026120 of 744 (3%)
June 202618 of 720 (1%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 744 (0%)
November 202600 of 19 (0%)

Incidents, newest first

Minor June 16, 2026 Reduction in performance when placing orders 7h 39m

Started Jun 16, 2026, 12:59 PM UTC· resolved Jun 16, 2026, 08:38 PM UTC

  1. investigating Jun 16, 2026, 12:59 PM UTC

    We are aware of a reduced performance while attempting to place orders. We are currently investigating the situation. Next update: 30 minutes..

  2. identified Jun 16, 2026, 01:33 PM UTC

    We've identified the cause of the issues and are deploying a fix for this incident. Next update: 30 minutes.

  3. monitoring Jun 16, 2026, 01:55 PM UTC

    We implemented a fix and are currently monitoring the result. Next update: 60 mins..

  4. monitoring Jun 16, 2026, 04:36 PM UTC

    We are continuing to monitor our fix. Next update: 60 mins..

  5. monitoring Jun 16, 2026, 05:58 PM UTC

    We are continuing to monitor our fix..

  6. resolved Jun 16, 2026, 08:38 PM UTC

    This incident has been resolved..

Read the full incident report →

Minor May 27, 2026 Investigating issues with system delays and error rates 19h 34m

Started May 27, 2026, 07:17 PM UTC· resolved May 28, 2026, 02:52 PM UTC

  1. investigating May 27, 2026, 07:17 PM UTC

    We're currently experiencing system delays. We are currently investigating. Next update: 30 minutes..

  2. monitoring May 27, 2026, 07:46 PM UTC

    We implemented a fix and are currently monitoring the result..

  3. resolved May 28, 2026, 02:52 PM UTC

    This issue has been resolved..

Read the full incident report →