Skip to content

Outage tracker / Monzo

Is Monzo down?

I'm having a problem

Operationalchecked 2 minutes ago

We reached Monzo from all 10 regions we check.

As of Oct 5, 2026, 8:15 PM UTC, Monzo answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 44 days we have measured Monzo (since Aug 22, 2026).

our independent probeslive · checked Oct 5, 2026, 8:15 PM UTC
US-East221 msOperational
US-West599 msOperational
Europe111 msOperational
Asia-Pacific1304 msOperational
US-Central626 msOperational
Canada599 msOperational
UK324 msOperational
Southeast Asia803 msOperational
Australia1365 msOperational
South America1083 msOperational
their status pagetheir claim, not our reading

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

from Monzo's own status page, checked Oct 5, 2026, 7:58 PM UTC
Our probes and Monzo's own status page agree: both show Monzo as reachable 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
634msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 553ms2026-09-07 UTC: p95 505ms2026-09-08 UTC: p95 598ms2026-09-09 UTC: p95 600ms2026-09-10 UTC: p95 588ms2026-09-11 UTC: p95 625ms2026-09-12 UTC: p95 486ms2026-09-13 UTC: p95 590ms2026-09-14 UTC: p95 486ms2026-09-15 UTC: p95 492ms2026-09-16 UTC: p95 549ms2026-09-17 UTC: p95 589ms2026-09-18 UTC: p95 536ms2026-09-19 UTC: p95 558ms2026-09-20 UTC: p95 623ms2026-09-21 UTC: p95 492ms2026-09-22 UTC: p95 547ms2026-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 634ms
Sep 6Sep 20Oct 5
US-West
890msp95 · 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-06 UTC: p95 973ms2026-09-07 UTC: p95 875ms2026-09-08 UTC: p95 820ms2026-09-09 UTC: p95 732ms2026-09-10 UTC: p95 734ms2026-09-11 UTC: p95 740ms2026-09-12 UTC: p95 668ms2026-09-13 UTC: p95 651ms2026-09-14 UTC: p95 675ms2026-09-15 UTC: p95 804ms2026-09-16 UTC: p95 956ms2026-09-17 UTC: p95 869ms2026-09-18 UTC: p95 935ms2026-09-19 UTC: p95 908ms2026-09-20 UTC: p95 905ms2026-09-21 UTC: p95 893ms2026-09-22 UTC: p95 928ms2026-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 890ms
Sep 6Sep 20Oct 5
Europe
424msp95 · 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-06 UTC: p95 496ms2026-09-07 UTC: p95 564ms2026-09-08 UTC: p95 721ms2026-09-09 UTC: p95 590ms2026-09-10 UTC: p95 824ms2026-09-11 UTC: p95 539ms2026-09-12 UTC: p95 538ms2026-09-13 UTC: p95 659ms2026-09-14 UTC: p95 553ms2026-09-15 UTC: p95 539ms2026-09-16 UTC: p95 615ms2026-09-17 UTC: p95 775ms2026-09-18 UTC: p95 687ms2026-09-19 UTC: p95 772ms2026-09-20 UTC: p95 773ms2026-09-21 UTC: p95 798ms2026-09-22 UTC: p95 700ms2026-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 424ms
Sep 6Sep 20Oct 5
Asia-Pacific
1.4sp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.4s2026-09-07 UTC: p95 1.4s2026-09-08 UTC: p95 1.5s2026-09-09 UTC: p95 1.4s2026-09-10 UTC: p95 1.5s2026-09-11 UTC: p95 1.4s2026-09-12 UTC: p95 1.5s2026-09-13 UTC: p95 1.4s2026-09-14 UTC: p95 1.5s2026-09-15 UTC: p95 1.5s2026-09-16 UTC: p95 1.4s2026-09-17 UTC: p95 1.6s2026-09-18 UTC: p95 1.7s2026-09-19 UTC: p95 1.5s2026-09-20 UTC: p95 1.4s2026-09-21 UTC: p95 1.4s2026-09-22 UTC: p95 1.3s2026-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.4s
Sep 6Sep 20Oct 5
US-Central
674msp95 · 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-06 UTC: p95 987ms2026-09-07 UTC: p95 477ms2026-09-08 UTC: p95 559ms2026-09-09 UTC: p95 612ms2026-09-10 UTC: p95 717ms2026-09-11 UTC: p95 763ms2026-09-12 UTC: p95 783ms2026-09-13 UTC: p95 900ms2026-09-14 UTC: p95 850ms2026-09-15 UTC: p95 750ms2026-09-16 UTC: p95 849ms2026-09-17 UTC: p95 723ms2026-09-18 UTC: p95 676ms2026-09-19 UTC: p95 745ms2026-09-20 UTC: p95 719ms2026-09-21 UTC: p95 792ms2026-09-22 UTC: p95 740ms2026-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 674ms
Sep 6Sep 20Oct 5
Canada
514msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 636ms2026-09-07 UTC: p95 583ms2026-09-08 UTC: p95 594ms2026-09-09 UTC: p95 613ms2026-09-10 UTC: p95 620ms2026-09-11 UTC: p95 600ms2026-09-12 UTC: p95 589ms2026-09-13 UTC: p95 676ms2026-09-14 UTC: p95 850ms2026-09-15 UTC: p95 810ms2026-09-16 UTC: p95 802ms2026-09-17 UTC: p95 730ms2026-09-18 UTC: p95 778ms2026-09-19 UTC: p95 813ms2026-09-20 UTC: p95 765ms2026-09-21 UTC: p95 875ms2026-09-22 UTC: p95 817ms2026-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 514ms
Sep 6Sep 20Oct 5
UK
396msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 257ms2026-09-07 UTC: p95 445ms2026-09-08 UTC: p95 348ms2026-09-09 UTC: p95 377ms2026-09-10 UTC: p95 495ms2026-09-11 UTC: p95 511ms2026-09-12 UTC: p95 401ms2026-09-13 UTC: p95 504ms2026-09-14 UTC: p95 416ms2026-09-15 UTC: p95 376ms2026-09-16 UTC: p95 603ms2026-09-17 UTC: p95 639ms2026-09-18 UTC: p95 485ms2026-09-19 UTC: p95 411ms2026-09-20 UTC: p95 456ms2026-09-21 UTC: p95 684ms2026-09-22 UTC: p95 762ms2026-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 396ms
Sep 6Sep 20Oct 5
Southeast Asia
1.0sp95 · latest
2.5s1.3s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.5s2026-09-07 UTC: p95 1.3s2026-09-08 UTC: p95 1.3s2026-09-09 UTC: p95 1.4s2026-09-10 UTC: p95 1.5s2026-09-11 UTC: p95 1.5s2026-09-12 UTC: p95 1.3s2026-09-13 UTC: p95 1.2s2026-09-14 UTC: p95 1.2s2026-09-15 UTC: p95 1.2s2026-09-16 UTC: p95 1.2s2026-09-17 UTC: p95 1.3s2026-09-18 UTC: p95 1.3s2026-09-19 UTC: p95 1.3s2026-09-20 UTC: p95 1.3s2026-09-21 UTC: p95 1.7s2026-09-22 UTC: p95 2.3s2026-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 1.0s
Sep 6Sep 20Oct 5
Australia
2.1sp95 · latest
2.5s1.3s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.7s2026-09-07 UTC: p95 1.7s2026-09-08 UTC: p95 1.6s2026-09-09 UTC: p95 1.6s2026-09-10 UTC: p95 1.6s2026-09-11 UTC: p95 2.1s2026-09-12 UTC: p95 2.1s2026-09-13 UTC: p95 2.0s2026-09-14 UTC: p95 1.6s2026-09-15 UTC: p95 1.9s2026-09-16 UTC: p95 1.7s2026-09-17 UTC: p95 2.2s2026-09-18 UTC: p95 1.9s2026-09-19 UTC: p95 2.1s2026-09-20 UTC: p95 2.1s2026-09-21 UTC: p95 2.1s2026-09-22 UTC: p95 2.3s2026-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.1s
Sep 6Sep 20Oct 5
South America
1.4sp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.2s2026-09-07 UTC: p95 1.4s2026-09-08 UTC: p95 1.4s2026-09-09 UTC: p95 1.4s2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 1.2s2026-09-12 UTC: p95 1.3s2026-09-13 UTC: p95 1.1s2026-09-14 UTC: p95 1.0s2026-09-15 UTC: p95 1.2s2026-09-16 UTC: p95 1.0s2026-09-17 UTC: p95 1.2s2026-09-18 UTC: p95 1.1s2026-09-19 UTC: p95 1.1s2026-09-20 UTC: p95 1.4s2026-09-21 UTC: p95 1.4s2026-09-22 UTC: p95 1.3s2026-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.4s
Sep 6Sep 20Oct 5

Is it Monzo, or is it you?

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: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational

Get an email when we see Monzo go down, and when it is back

Get told when we measure this

We will tell you when our probes stop reaching Monzo, and again when they can reach it again. That is our own measurement from ten regions, not Monzo's status page. No account, no card.

Delivery channel

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

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 we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 221msstatus code: 200checked: Oct 5, 2026, 8:09 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
      Operationallatency: 599msstatus code: 200checked: Oct 5, 2026, 8:08 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
      Operationallatency: 626msstatus code: 200checked: Oct 5, 2026, 8:06 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
      Operationallatency: 599msstatus code: 200checked: Oct 5, 2026, 8:01 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
    Operationallatency: 1083msstatus code: 200checked: Oct 5, 2026, 8:06 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
    OperationalEurope, UK
    • Europe
      Operationallatency: 111msstatus code: 200checked: Oct 5, 2026, 8:10 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
      Operationallatency: 324msstatus code: 200checked: Oct 5, 2026, 8:09 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
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 1304msstatus code: 200checked: Oct 5, 2026, 8:15 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
      Operationallatency: 803msstatus code: 200checked: Oct 5, 2026, 8:02 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
      Operationallatency: 1365msstatus code: 200checked: Oct 5, 2026, 7:59 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 outages

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

measured 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 measurements and Monzo's own claim at the time, side by side.

Full availability history for Monzo: 90-day availability by region, month-by-month uptime, and every incident 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 measured by RealUptimeLive, from this page's own readings.
[![Monzo uptime measured by RealUptime](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 measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and 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: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Monzo's SLA implies, from our measurement

At or above your target

We measured none of downtime for Monzo over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Monzo's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

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
RealUptime is not affiliated with Monzo; the name identifies what we measured, 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 clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.