checked Sep 21, 2026 9:17 AM UTC · Monta's official status page
Monta is up and running.
All components operational
Statusfield watches Monta alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.
Email only. No password. Free.
6 reports published by Monta in the last 30 days
When Monta breaks, it is typically resolved in 47m — median across 14 resolved incidents over 90 days.
resolvedSep 17 · 13:04 UTC
Charging sessions are now updating correctly in the app, and charge status is reflecting in real time again. As part of deploying the fix, charge status processing paused briefly between 12:43 and 12:48 UTC before resuming and fully catching up by 12:51 UTC.
Reported by Monta on their status page.
resolvedSep 16 · 09:28 UTC
This incident has been resolved.
Reported by Monta on their status page.
resolvedSep 14 · 12:58 UTC
We saw an increase in error rates across platforms, which caused our Hub and App to not load temporarily.
Reported by Monta on their status page.
resolvedSep 14 · 12:56 UTC
We saw an increase in error rates across platforms, which caused our Hub and App to not load temporarily.
Reported by Monta on their status page.
resolvedAug 28 · 14:59 UTC
This incident has been resolved.
Reported by Monta on their status page.
resolvedAug 22 · 11:24 UTC
Between approximately 10:50 and 11:15 UTC, the Monta platform experienced degraded availability. Users may have seen errors, timeouts, or slow responses in the Monta app, the Hub web portal, the Partner API, and related services. The cause was a capacity limit on an internal caching layer that did not autoscale correctly. We increased the capacity of that layer, which restored service. Availability returned to normal by 11:15 UTC, and response times recovered shortly after as queued work was processed. No data was lost. Charge session data that queued during the incident was processed as services recovered. We are adding monitoring on this capacity limit and investigating the underlying issue so this does not recur. We're sorry for the disruption.
Reported by Monta on their status page.
