Skip to content

Outage tracker / Monzo

Is Monzo down?

I'm having a problem

Vendor reports no incidentWhat Monzo reports

Monzo reports no incident on its status page.

As of the last successful poll, 2026-10-22 19:00 UTC.

Monzo's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 1 minute ago

Our checks of Monzo pass from all 10 regions we check.

As of Oct 22, 2026, 7:04 PM UTC, RealUptime's checks of Monzo passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Oct 22, 2026, 7:04 PM UTC
US-East930 msChecks passing
US-West1636 msChecks passing
Europe256 msChecks passing
Asia-Pacific2485 msChecks passing
US-Central872 msChecks passing
Canada808 msChecks passing
UK853 msChecks passing
Southeast Asia2841 msChecks passing
Australia2672 msChecks passing
South America1994 msChecks passing
their status pagetheir claim, not our reading

Monzo reports: All systems operational (“All Systems Operational”)

from Monzo's own status page, checked Oct 22, 2026, 6:52 PM UTC
Monzo's own status page shows no incident, and our checks of Monzo pass right now.

Monzo's own component breakdown, as they publish it

  • 📱 Monzo AppOperational
  • 💳 Card PaymentsOperational
  • 💸 Outbound Bank TransfersOperational
  • 💰 Inbound Bank TransfersOperational
  • 💷 Cash DepositsOperational
  • 🔗 Public APIOperational
  • ✉️ Email SupportOperational
  • 💬 Chat SupportOperational
  • ☎️ Phone SupportOperational
  • 📨 SMS Outbound DeliveryOperational
  • 📨 SMS OutboundOperational
  • 📬 Email DeliveryOperational

These are Monzo's components, named and scored by Monzo. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Monzo's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Monzo response time, by region

US-East
1.3sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 731ms2026-09-24 UTC: p95 939ms2026-09-25 UTC: p95 648ms2026-09-26 UTC: p95 564ms2026-09-27 UTC: p95 535ms2026-09-28 UTC: p95 507ms2026-09-29 UTC: p95 545ms2026-09-30 UTC: p95 501ms2026-10-01 UTC: p95 575ms2026-10-02 UTC: p95 452ms2026-10-03 UTC: p95 589ms2026-10-04 UTC: p95 655ms2026-10-05 UTC: p95 623ms2026-10-06 UTC: p95 635ms2026-10-07 UTC: p95 564ms2026-10-08 UTC: p95 654ms2026-10-09 UTC: p95 552ms2026-10-10 UTC: p95 554ms2026-10-11 UTC: p95 554ms2026-10-12 UTC: p95 566ms2026-10-13 UTC: p95 684ms2026-10-14 UTC: p95 611ms2026-10-15 UTC: p95 724ms2026-10-16 UTC: p95 700ms2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.5s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 1.6s2026-10-21 UTC: p95 1.6s2026-10-22 UTC: p95 1.3s
Sep 23Oct 7Oct 22
US-West
1.8sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 930ms2026-09-24 UTC: p95 833ms2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 999ms2026-09-27 UTC: p95 786ms2026-09-28 UTC: p95 846ms2026-09-29 UTC: p95 930ms2026-09-30 UTC: p95 948ms2026-10-01 UTC: p95 819ms2026-10-02 UTC: p95 791ms2026-10-03 UTC: p95 831ms2026-10-04 UTC: p95 902ms2026-10-05 UTC: p95 912ms2026-10-06 UTC: p95 897ms2026-10-07 UTC: p95 939ms2026-10-08 UTC: p95 873ms2026-10-09 UTC: p95 887ms2026-10-10 UTC: p95 1.6s2026-10-11 UTC: p95 1.6s2026-10-12 UTC: p95 870ms2026-10-13 UTC: p95 845ms2026-10-14 UTC: p95 1.0s2026-10-15 UTC: p95 897ms2026-10-16 UTC: p95 925ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.6s2026-10-21 UTC: p95 1.9s2026-10-22 UTC: p95 1.8s
Sep 23Oct 7Oct 22
Europe
575msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 670ms2026-09-24 UTC: p95 821ms2026-09-25 UTC: p95 716ms2026-09-26 UTC: p95 729ms2026-09-27 UTC: p95 382ms2026-09-28 UTC: p95 616ms2026-09-29 UTC: p95 618ms2026-09-30 UTC: p95 549ms2026-10-01 UTC: p95 395ms2026-10-02 UTC: p95 376ms2026-10-03 UTC: p95 395ms2026-10-04 UTC: p95 443ms2026-10-05 UTC: p95 423ms2026-10-06 UTC: p95 387ms2026-10-07 UTC: p95 473ms2026-10-08 UTC: p95 440ms2026-10-09 UTC: p95 377ms2026-10-10 UTC: p95 287ms2026-10-11 UTC: p95 356ms2026-10-12 UTC: p95 372ms2026-10-13 UTC: p95 270ms2026-10-14 UTC: p95 881ms2026-10-15 UTC: p95 552ms2026-10-16 UTC: p95 221ms2026-10-17 UTC: p95 907ms2026-10-18 UTC: p95 866ms2026-10-19 UTC: p95 990ms2026-10-20 UTC: p95 688ms2026-10-21 UTC: p95 571ms2026-10-22 UTC: p95 575ms
Sep 23Oct 7Oct 22
Asia-Pacific
2.8sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 1.5s2026-09-24 UTC: p95 1.7s2026-09-25 UTC: p95 1.5s2026-09-26 UTC: p95 1.4s2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 1.2s2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 1.5s2026-10-03 UTC: p95 1.5s2026-10-04 UTC: p95 1.5s2026-10-05 UTC: p95 1.4s2026-10-06 UTC: p95 1.6s2026-10-07 UTC: p95 1.4s2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 2.1s2026-10-10 UTC: p95 2.1s2026-10-11 UTC: p95 2.1s2026-10-12 UTC: p95 1.9s2026-10-13 UTC: p95 1.5s2026-10-14 UTC: p95 1.5s2026-10-15 UTC: p95 1.3s2026-10-16 UTC: p95 1.4s2026-10-17 UTC: p95 2.3s2026-10-18 UTC: p95 2.4s2026-10-19 UTC: p95 2.4s2026-10-20 UTC: p95 2.5s2026-10-21 UTC: p95 2.6s2026-10-22 UTC: p95 2.8s
Sep 23Oct 7Oct 22
US-Central
1.3sp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 1.2s2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 777ms2026-09-26 UTC: p95 862ms2026-09-27 UTC: p95 871ms2026-09-28 UTC: p95 918ms2026-09-29 UTC: p95 670ms2026-09-30 UTC: p95 673ms2026-10-01 UTC: p95 746ms2026-10-02 UTC: p95 685ms2026-10-03 UTC: p95 686ms2026-10-04 UTC: p95 858ms2026-10-05 UTC: p95 685ms2026-10-06 UTC: p95 772ms2026-10-07 UTC: p95 884ms2026-10-08 UTC: p95 764ms2026-10-09 UTC: p95 645ms2026-10-10 UTC: p95 1.6s2026-10-11 UTC: p95 1.6s2026-10-12 UTC: p95 686ms2026-10-13 UTC: p95 859ms2026-10-14 UTC: p95 897ms2026-10-15 UTC: p95 775ms2026-10-16 UTC: p95 832ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.3s
Sep 23Oct 7Oct 22
Canada
1.5sp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 842ms2026-09-24 UTC: p95 832ms2026-09-25 UTC: p95 698ms2026-09-26 UTC: p95 683ms2026-09-27 UTC: p95 607ms2026-09-28 UTC: p95 667ms2026-09-29 UTC: p95 700ms2026-09-30 UTC: p95 665ms2026-10-01 UTC: p95 648ms2026-10-02 UTC: p95 583ms2026-10-03 UTC: p95 732ms2026-10-04 UTC: p95 888ms2026-10-05 UTC: p95 624ms2026-10-06 UTC: p95 515ms2026-10-07 UTC: p95 475ms2026-10-08 UTC: p95 636ms2026-10-09 UTC: p95 690ms2026-10-10 UTC: p95 688ms2026-10-11 UTC: p95 1.5s2026-10-12 UTC: p95 1.4s2026-10-13 UTC: p95 769ms2026-10-14 UTC: p95 648ms2026-10-15 UTC: p95 715ms2026-10-16 UTC: p95 731ms2026-10-17 UTC: p95 774ms2026-10-18 UTC: p95 780ms2026-10-19 UTC: p95 777ms2026-10-20 UTC: p95 804ms2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 1.5s
Sep 23Oct 7Oct 22
UK
1.2sp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 615ms2026-09-24 UTC: p95 786ms2026-09-25 UTC: p95 654ms2026-09-26 UTC: p95 405ms2026-09-27 UTC: p95 525ms2026-09-28 UTC: p95 480ms2026-09-29 UTC: p95 644ms2026-09-30 UTC: p95 672ms2026-10-01 UTC: p95 438ms2026-10-02 UTC: p95 349ms2026-10-03 UTC: p95 388ms2026-10-04 UTC: p95 486ms2026-10-05 UTC: p95 405ms2026-10-06 UTC: p95 507ms2026-10-07 UTC: p95 354ms2026-10-08 UTC: p95 282ms2026-10-09 UTC: p95 507ms2026-10-10 UTC: p95 385ms2026-10-11 UTC: p95 379ms2026-10-12 UTC: p95 404ms2026-10-13 UTC: p95 304ms2026-10-14 UTC: p95 248ms2026-10-15 UTC: p95 149ms2026-10-16 UTC: p95 309ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 1.2s
Sep 23Oct 7Oct 22
Southeast Asia
3.6sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 2.0s2026-09-24 UTC: p95 1.8s2026-09-25 UTC: p95 1.7s2026-09-26 UTC: p95 1.3s2026-09-27 UTC: p95 1.3s2026-09-28 UTC: p95 1.2s2026-09-29 UTC: p95 1.5s2026-09-30 UTC: p95 1.5s2026-10-01 UTC: p95 1.2s2026-10-02 UTC: p95 1.3s2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 997ms2026-10-06 UTC: p95 1.3s2026-10-07 UTC: p95 1.6s2026-10-08 UTC: p95 1.6s2026-10-09 UTC: p95 1.7s2026-10-10 UTC: p95 1.7s2026-10-11 UTC: p95 1.7s2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 1.5s2026-10-14 UTC: p95 1.4s2026-10-15 UTC: p95 1.5s2026-10-16 UTC: p95 1.5s2026-10-17 UTC: p95 2.1s2026-10-18 UTC: p95 2.6s2026-10-19 UTC: p95 2.8s2026-10-20 UTC: p95 3.0s2026-10-21 UTC: p95 2.8s2026-10-22 UTC: p95 3.6s
Sep 23Oct 7Oct 22
Australia
2.8sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 2.0s2026-09-24 UTC: p95 2.0s2026-09-25 UTC: p95 2.0s2026-09-26 UTC: p95 2.3s2026-09-27 UTC: p95 1.8s2026-09-28 UTC: p95 1.8s2026-09-29 UTC: p95 1.9s2026-09-30 UTC: p95 2.0s2026-10-01 UTC: p95 2.3s2026-10-02 UTC: p95 1.7s2026-10-03 UTC: p95 2.0s2026-10-04 UTC: p95 2.0s2026-10-05 UTC: p95 2.1s2026-10-06 UTC: p95 1.9s2026-10-07 UTC: p95 1.8s2026-10-08 UTC: p95 2.1s2026-10-09 UTC: p95 2.2s2026-10-10 UTC: p95 2.5s2026-10-11 UTC: p95 2.5s2026-10-12 UTC: p95 1.9s2026-10-13 UTC: p95 1.5s2026-10-14 UTC: p95 1.8s2026-10-15 UTC: p95 1.7s2026-10-16 UTC: p95 1.7s2026-10-17 UTC: p95 2.9s2026-10-18 UTC: p95 2.8s2026-10-19 UTC: p95 2.8s2026-10-20 UTC: p95 3.0s2026-10-21 UTC: p95 3.0s2026-10-22 UTC: p95 2.8s
Sep 23Oct 7Oct 22
South America
2.8sp95 · latest
5s2.5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 1.4s2026-09-24 UTC: p95 1.4s2026-09-25 UTC: p95 1.5s2026-09-26 UTC: p95 1.2s2026-09-27 UTC: p95 1.7s2026-09-28 UTC: p95 1.2s2026-09-29 UTC: p95 1.5s2026-09-30 UTC: p95 1.3s2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 1.3s2026-10-03 UTC: p95 1.5s2026-10-04 UTC: p95 1.6s2026-10-05 UTC: p95 1.3s2026-10-06 UTC: p95 1.3s2026-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.4s2026-10-09 UTC: p95 1.7s2026-10-10 UTC: p95 2.2s2026-10-11 UTC: p95 2.1s2026-10-12 UTC: p95 1.8s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.4s2026-10-15 UTC: p95 1.3s2026-10-16 UTC: p95 1.7s2026-10-17 UTC: p95 2.4s2026-10-18 UTC: p95 2.5s2026-10-19 UTC: p95 2.5s2026-10-20 UTC: p95 2.7s2026-10-21 UTC: p95 2.8s2026-10-22 UTC: p95 2.8s
Sep 23Oct 7Oct 22

Check your own site while you wait on Monzo

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Monzo. It cannot diagnose Monzo's own systems.

What we measured, function by function

Monzo answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Email me when Monzo reports an incident on its status page, and again when it reports it resolved.

Get an email when Monzo reports an incident

Email me when Monzo reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when it reports an incident, one when it reports it resolved, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is Monzo's own statement from its status page, with our regional reading beside it.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 930msstatus code: 200checked: Oct 22, 2026, 7:04 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Monzo normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 1636msstatus code: 200checked: Oct 22, 2026, 6:57 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Monzo normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 872msstatus code: 200checked: Oct 22, 2026, 6:59 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Monzo normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 808msstatus code: 200checked: Oct 22, 2026, 7:03 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Monzo normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 1994msstatus code: 200checked: Oct 22, 2026, 6:59 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Monzo normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 256msstatus code: 200checked: Oct 22, 2026, 7:02 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Monzo normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 853msstatus code: 200checked: Oct 22, 2026, 6:58 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Monzo normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 2485msstatus code: 200checked: Oct 22, 2026, 7:04 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Monzo normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 2841msstatus code: 200checked: Oct 22, 2026, 7:03 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Monzo normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 2672msstatus code: 200checked: Oct 22, 2026, 6:46 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Monzo normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Monzo, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Monzo yet, which is not evidence that nothing is wrong.

Recent probe events

We are experiencing platform issues, 3h 44mdeclared on their status page2026-08-19
Issues with Barclays sending and receiving payments, 1h 28mdeclared on their status page2026-07-27
Issues with Barclays sending and receiving payments, 2h 30mdeclared on their status page2026-07-27
We're experiencing issues with our phone lines., 5h 16mdeclared on their status page2026-03-02
Platform issues, 29mdeclared on their status page2026-01-13
UK Freephone is unreachable, 6mdeclared on their status page2025-12-22
Calls impacted due to third party outage., 41mdeclared on their status page2025-11-25
Calls impacted due to AWS outage, 23h 46mdeclared on their status page2025-10-20

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Monzo since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Monzo covering any window you pick, with our check readings and Monzo's own claim at the time, side by side.

Full check history for Monzo: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Put this badge in your README

Monzo uptime by RealUptime's checksLive, from this page's own readings.
[![Monzo uptime by RealUptime's checks](https://realuptime.io/outages/monzo/badge.svg?days=30)](https://realuptime.io/outages/monzo)
<a href="https://realuptime.io/outages/monzo"><img src="https://realuptime.io/outages/monzo/badge.svg?days=30" alt="Monzo uptime by RealUptime's checks" height="20"></a>

The badge shows the share of our checks that passed over the last 30 days. The window is printed on it, so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

To cite this page: RealUptime, "Is Monzo down?", https://realuptime.io/outages/monzo. The readings change with every check, so give the date you read them.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

What we check

primaryfunctional: live API
https://api.monzo.com/ping/whoami
secondary
https://monzo.com/
secondary
https://monzo.statuspage.io/api/v2/status.json

What our check can and cannot see

A pass means a public route of the service's API answered our request normally. We do not check what it returned, so it does not show that the data is right, that sign-in works or that the rest of the product works.

Host checked: api.monzo.com

RealUptime is not affiliated with Monzo; the name identifies what we checked, and nothing here speaks for Monzo's own team. We send a single web request to Monzo from 10 regions on our own schedule and time the response. We do not see inside Monzo's systems, do not use an account or real transaction, and are not the same signal Monzo's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Monzo is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.