Skip to content

Outage tracker / N26

Is N26 down?

I'm having a problem

Operationalchecked 2 minutes ago

We reached N26 from all 10 regions we check.

Reachability verified

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

our independent probeslive · checked Sep 5, 2026, 2:06 AM UTC
US-East54 msOperational
US-West661 msOperational
Europe194 msOperational
Asia-Pacific711 msOperational
US-Central235 msOperational
Canada416 msOperational
UK308 msOperational
Southeast Asia1541 msOperational
Australia751 msOperational
South America558 msOperational
their status pagetheir claim, not our reading

N26 publishes no status feed we can read, so the only independent reading here is ours on the left.

N26 response time, by region

US-East
383msp95 · latest
500ms250ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 354ms2026-08-23 UTC: p95 422ms2026-08-24 UTC: p95 428ms2026-08-25 UTC: p95 456ms2026-08-26 UTC: p95 410ms2026-08-27 UTC: p95 401ms2026-08-28 UTC: p95 373ms2026-08-29 UTC: p95 400ms2026-08-30 UTC: p95 492ms2026-08-31 UTC: p95 426ms2026-09-01 UTC: p95 476ms2026-09-02 UTC: p95 456ms2026-09-03 UTC: p95 386ms2026-09-04 UTC: p95 310ms2026-09-05 UTC: p95 383ms
Aug 7Aug 21Sep 5
US-West
619msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 167ms2026-08-23 UTC: p95 602ms2026-08-24 UTC: p95 322ms2026-08-25 UTC: p95 368ms2026-08-26 UTC: p95 179ms2026-08-27 UTC: p95 630ms2026-08-28 UTC: p95 964ms2026-08-29 UTC: p95 609ms2026-08-30 UTC: p95 648ms2026-08-31 UTC: p95 512ms2026-09-01 UTC: p95 534ms2026-09-02 UTC: p95 603ms2026-09-03 UTC: p95 751ms2026-09-04 UTC: p95 730ms2026-09-05 UTC: p95 619ms
Aug 7Aug 21Sep 5
Europe
190msp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 1.3s2026-08-23 UTC: p95 540ms2026-08-24 UTC: p95 536ms2026-08-25 UTC: p95 171ms2026-08-26 UTC: p95 369ms2026-08-27 UTC: p95 447ms2026-08-28 UTC: p95 394ms2026-08-29 UTC: p95 388ms2026-08-30 UTC: p95 324ms2026-08-31 UTC: p95 282ms2026-09-01 UTC: p95 465ms2026-09-02 UTC: p95 457ms2026-09-03 UTC: p95 426ms2026-09-04 UTC: p95 344ms2026-09-05 UTC: p95 190ms
Aug 7Aug 21Sep 5
Asia-Pacific
742msp95 · 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-08-22 UTC: p95 602ms2026-08-23 UTC: p95 761ms2026-08-24 UTC: p95 893ms2026-08-25 UTC: p95 1.0s2026-08-26 UTC: p95 1.1s2026-08-27 UTC: p95 1.1s2026-08-28 UTC: p95 938ms2026-08-29 UTC: p95 1.0s2026-08-30 UTC: p95 1.1s2026-08-31 UTC: p95 987ms2026-09-01 UTC: p95 974ms2026-09-02 UTC: p95 1.5s2026-09-03 UTC: p95 1.2s2026-09-04 UTC: p95 876ms2026-09-05 UTC: p95 742ms
Aug 7Aug 21Sep 5
US-Central
278msp95 · latest
500ms250ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 383ms2026-09-04 UTC: p95 419ms2026-09-05 UTC: p95 278ms
Aug 7Aug 21Sep 5
Canada
406msp95 · latest
500ms250ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 496ms2026-09-04 UTC: p95 373ms2026-09-05 UTC: p95 406ms
Aug 7Aug 21Sep 5
UK
486msp95 · 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-03 UTC: p95 523ms2026-09-04 UTC: p95 1.3s2026-09-05 UTC: p95 486ms
Aug 7Aug 21Sep 5
Southeast Asia
1.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-03 UTC: p95 2.8s2026-09-04 UTC: p95 2.2s2026-09-05 UTC: p95 1.6s
Aug 7Aug 21Sep 5
Australia
1.3sp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.0s2026-09-04 UTC: p95 881ms2026-09-05 UTC: p95 1.3s
Aug 7Aug 21Sep 5
South America
555msp95 · 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-03 UTC: p95 1.2s2026-09-04 UTC: p95 596ms2026-09-05 UTC: p95 555ms
Aug 7Aug 21Sep 5

Is it N26, 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 N26 -- it cannot diagnose N26's own systems.

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: 54msstatus code: 200checked: Sep 5, 2026, 2:04 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach N26 normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 661msstatus code: 200checked: Sep 5, 2026, 1:42 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach N26 normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 235msstatus code: 200checked: Sep 5, 2026, 2:02 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach N26 normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 416msstatus code: 200checked: Sep 5, 2026, 2:03 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach N26 normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 558msstatus code: 200checked: Sep 5, 2026, 1:34 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach N26 normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 194msstatus code: 200checked: Sep 5, 2026, 1:44 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach N26 normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 308msstatus code: 200checked: Sep 5, 2026, 1:38 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach N26 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: 711msstatus code: 200checked: Sep 5, 2026, 1:45 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach N26 normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 1541msstatus code: 200checked: Sep 5, 2026, 2:00 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach N26 normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 751msstatus code: 200checked: Sep 5, 2026, 2:06 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach N26 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 N26, 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 N26 yet, which is not evidence that nothing is wrong.

Recent outages

No outages on record yet for N26.

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

We have been measuring N26 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 N26 covering any window you pick, with our measurements and N26's own claim at the time, side by side.

Full availability history for N26: 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

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching N26, and again when they can reach it again. That is our own measurement from ten regions, not N26'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.

Put this badge in your README

N26 uptime measured by RealUptimeLive, from this page's own readings.
[![N26 uptime measured by RealUptime](https://realuptime.io/outages/n26/badge.svg?days=30)](https://realuptime.io/outages/n26)
<a href="https://realuptime.io/outages/n26"><img src="https://realuptime.io/outages/n26/badge.svg?days=30" alt="N26 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 N26's SLA implies, from our measurement

At or above your target

We measured none of downtime for N26 over the 338h 8m since we started watching it on 2026-08-22, which is 100% uptime by our reading. A 99.9% target allows 20 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 N26'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

primary
https://n26.com/en-eu
RealUptime is not affiliated with N26; the name identifies what we measured, and nothing here speaks for N26's own team. We send a single web request to N26 from 10 regions on our own schedule and time the response. We do not see inside N26's systems, do not use an account or real transaction, and are not the same signal N26's own team has access to. Treat this as one external data point, not a verdict. What we check for N26 proves reachability only: the endpoints above answer, but that does not confirm the underlying product or account features work. Read the full methodology.