Skip to content

Outage tracker

Monzo: the full evidence record

The last 24 hours in detail, 15 days of measured availability, a 12-month summary, our own incident log, Monzo's declared record, and how the two compare.

← Back to Monzo's live status

We started measuring Monzo on August 22, 2026, which is 15 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.

The last 24 hours

What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Monzo's own status page declared. Below it, any public chatter we saw about Monzo and the extra probe it triggered.

The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Monzo's own status page declared. Three records side by side; none of them changes another.

Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about Monzo in the last 24 hours, which is not evidence that nothing is wrong.
Monzo's status pageNo incident declared in the last 24 hours.

Each probe cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused probe is not an outage. Report bars count unverified reports, not people we verified; they never change our reading. The status-page lane is Monzo's own declaration, shown as they made it.

Third-party chatter, labeled

Public posts from the last hour that mention Monzo next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.

No matching public posts in the last hour from the sources we watch.

Availability by region

Availability is measured probes that succeeded, divided by every probe we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.

RegionAvailabilityProbes recorded
US-East100.00%1841
US-West100.00%1832
Europe100.00%1765
Asia-Pacific100.00%1559
US-Central100.00%175
Canada100.00%175
UK100.00%174
Southeast Asia100.00%143
Australia100.00%140
South America100.00%165

Monthly summary

Tracking Monzo since Aug 22, 2026. In that time our probes detected no outage. Months before that date are not tracked and carry no figure.

MonthUptimeOutagesDowntime
Oct 2025not tracked
Nov 2025not tracked
Dec 2025not tracked
Jan 2026not tracked
Feb 2026not tracked
Mar 2026not tracked
Apr 2026not tracked
May 2026not tracked
Jun 2026not tracked
Jul 2026not tracked
Aug 2026 from Aug 22, 2026100%00 min
Sep 2026100%00 min

Uptime here is the share of each month in which our probes had no outage open for Monzo: two consecutive failed readings from a region opens one, the first clean reading closes it. Any detected outage counts, including one seen from a single region, and an outage that crosses midnight on the first of a month is counted in both months with its minutes split. User reports, public posts and Monzo's own status page contribute nothing to these figures.

Our incident log

Every outage our own probes detected for Monzo in the last 90 days, or since we started measuring it if that is more recent. This list is probe-only: Monzo's own declared incidents appear further down this page in their own attributed section, never merged with what we measured here. User reports live on the live page, in their own labeled block.

No outages detected for Monzo since we started measuring it on August 22, 2026. We show nothing from before that date.

Their declared record

Monzo's own incident history, taken from their public status feed. This is their account of what happened, not our measurement, and it never changes the incident log above or the other way around.

We are experiencing platform issuesAll systems operational
Aug 19, 2026, 11:55 AM UTC to Aug 19, 2026, 3:40 PM UTC (3h 44m)resolved
their latest update (Aug 19, 2026, 3:40 PM UTC): We’re happy to say that our platform issues are all sorted. Thanks for your patience while we worked on the fix 🙏
Issues with Barclays sending and receiving paymentsMinor incident
Jul 27, 2026, 4:25 PM UTC to Jul 27, 2026, 5:53 PM UTC (1h 28m)resolved
their latest update (Jul 27, 2026, 5:53 PM UTC): The issue is now resolved.
Issues with Barclays sending and receiving paymentsMinor incident
Jul 27, 2026, 1:52 PM UTC to Jul 27, 2026, 4:21 PM UTC (2h 30m)resolved
their latest update (Jul 27, 2026, 4:21 PM UTC): This is now resolved
We're experiencing issues with our phone lines.All systems operational
Mar 2, 2026, 11:52 AM UTC to Mar 2, 2026, 5:08 PM UTC (5h 16m)resolved
their latest update (Mar 2, 2026, 5:08 PM UTC): This incident has been resolved.
Platform issuesPartial outage
Jan 13, 2026, 5:07 PM UTC to Jan 13, 2026, 5:36 PM UTC (29 min)resolved
their latest update (Jan 13, 2026, 5:36 PM UTC): We've recovered now. Still keeping an eye for any side-effects.
UK Freephone is unreachablePartial outage
Dec 22, 2025, 11:39 AM UTC to Dec 22, 2025, 11:45 AM UTC (6 min)resolved
their latest update (Dec 22, 2025, 11:45 AM UTC): The issue affecting our UK Freephone number (+448008021281) has been fixed.
Calls impacted due to third party outage.Minor incident
Nov 25, 2025, 3:25 PM UTC to Nov 25, 2025, 4:06 PM UTC (41 min)resolved
their latest update (Nov 25, 2025, 4:06 PM UTC): The issue has now been resolved and all call operations are back to normal.
Calls impacted due to AWS outageMinor incident
Oct 20, 2025, 8:43 AM UTC to Oct 21, 2025, 8:29 AM UTC (23h 46m)resolved
their latest update (Oct 21, 2025, 8:29 AM UTC): This incident has been resolved.
Our phones lines have gone down, and we're working to fix them as soon as we canMinor incident
Jul 14, 2025, 5:28 PM UTC to Jul 14, 2025, 6:30 PM UTC (1h 2m)resolved
their latest update (Jul 14, 2025, 6:30 PM UTC): The issue has now been resolved and our phone lines are now working again. Please be aware that there might be a slight wait as we catch up.
Our phones lines have gone down, and we're working to fix them as soon as we canMinor incident
Mar 11, 2025, 2:55 PM UTC to Mar 11, 2025, 4:37 PM UTC (1h 42m)resolved
their latest update (Mar 11, 2025, 4:37 PM UTC): This incident has been resolved.

Showing the 10 most recent of 50 incidents Monzo has declared in the history we hold.

These entries are Monzo's own declarations, taken from their public status feed, shown separately from the outages we detected ourselves. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.

The scorecard

How Monzo's status page compared with what we measured, for every outage above that falls inside the window we have been capturing their claims.

We started recording Monzo's own status page on August 22, 2026, 13 days ago. This comparison covers that period only, we do not reconstruct what they said before it, and we compare only inside outages we measured ourselves.

We have not measured an outage for Monzo since we started recording their status page, so there is nothing to compare. That is a short measurement window, not a track record.

Monzo decides what their status page covers, and it may report per component while our check reaches one surface from ten regions. We state what each side measured and leave the conclusion to you. If Monzo believes a figure here is wrong, we publish corrections as prominently as the original.

Full detail on what a probe does and does not prove is in the methodology page.