Monnit Outage History

Monnit is up right now

Monnit had 6 outages in the last 2 years totaling 40h 37m of downtime — averaging 0.2 incidents per month.

There were 6 Monnit outages since October 9, 2025 totaling 40h 37m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.monnit.com

Minor October 11, 2026

service outage

Detected by Pingoru
Oct 11, 2026, 07:04 PM UTC
Resolved
Oct 11, 2026, 08:22 PM UTC
Duration
1h 17m
Affected: Web PortalGateway ServiceNotification DeliveryWebhook DeliveryRest API
Timeline · 3 updates

Read the full incident report →

Minor October 5, 2026

Service Outage

Detected by Pingoru
Oct 05, 2026, 09:20 PM UTC
Resolved
Oct 06, 2026, 03:00 AM UTC
Duration
5h 39m
Affected: Web PortalGateway ServiceNotification DeliveryWebhook DeliveryRest APIStaging Test ImplementationWeb StorePartner Order API
Timeline · 5 updates

Read the full incident report →

Minor April 3, 2026

Service Disruption

Detected by Pingoru
Apr 03, 2026, 04:44 PM UTC
Resolved
Apr 03, 2026, 08:01 PM UTC
Duration
3h 17m
Affected: Web PortalGateway ServiceNotification DeliveryWebhook DeliveryRest APIWeb StorePartner Order API
Timeline · 3 updates
  1. investigating Apr 03, 2026, 04:44 PM UTC

    We are investigating a service disruption affecting all production services.

  2. monitoring Apr 03, 2026, 05:15 PM UTC

    We were able to get the secondary database node to take over processing. We’re monitoring that, and still evaluating root cause.

  3. resolved Apr 03, 2026, 08:01 PM UTC

    All services restored

Read the full incident report →

Minor March 17, 2026

Gateway Service Disruption

Detected by Pingoru
Mar 17, 2026, 06:55 PM UTC
Resolved
Mar 17, 2026, 10:42 PM UTC
Duration
3h 47m
Affected: Web PortalGateway ServiceNotification DeliveryWebhook DeliveryRest API
Timeline · 2 updates
  1. investigating Mar 17, 2026, 06:55 PM UTC

    We are investigating an issue in the database synchronization that is causing service disruption.

  2. resolved Mar 17, 2026, 10:42 PM UTC

    DB synchronization error has been remedied by ejecting the unhealthy node. There are still multiple active nodes processing data. The ejected node will be evaluated resolved and added back in later.

Read the full incident report →