Skip to content

Outage tracker / N26

Is N26 down?

I'm having a problem

Checks passingchecked 5 minutes ago

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

As of Nov 5, 2026, 2:29 PM UTC, RealUptime's checks of N26 passed in all 10 regions that returned a reading.

Front-door checks

Our checks of N26 did not fail from two or more distant regions in the 75 days we have checked it (since Aug 22, 2026). This does not show N26 works for users.

our check readinglive · checked Nov 5, 2026, 2:29 PM UTC
US-East472 msChecks passing
US-West715 msChecks passing
Europe168 msChecks passing
Asia-Pacific2139 msChecks passing
US-Central604 msChecks passing
Canada618 msChecks passing
UK469 msChecks passing
Southeast Asia2934 msChecks passing
Australia2090 msChecks passing
South America1714 msChecks passing
their status pagetheir claim, not our reading

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

N26 response time, by region

US-East
1.4sp95 · 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-10-07 UTC: p95 311ms2026-10-08 UTC: p95 303ms2026-10-09 UTC: p95 260ms2026-10-10 UTC: p95 261ms2026-10-11 UTC: p95 238ms2026-10-12 UTC: p95 213ms2026-10-13 UTC: p95 277ms2026-10-14 UTC: p95 272ms2026-10-15 UTC: p95 328ms2026-10-16 UTC: p95 316ms2026-10-17 UTC: p95 710ms2026-10-18 UTC: p95 858ms2026-10-19 UTC: p95 913ms2026-10-20 UTC: p95 937ms2026-10-21 UTC: p95 810ms2026-10-22 UTC: p95 763ms2026-10-23 UTC: p95 770ms2026-10-24 UTC: p95 701ms2026-10-25 UTC: p95 729ms2026-10-26 UTC: p95 1.0s2026-10-27 UTC: p95 775ms2026-10-28 UTC: p95 745ms2026-10-29 UTC: p95 774ms2026-10-30 UTC: p95 886ms2026-10-31 UTC: p95 950ms2026-11-01 UTC: p95 899ms2026-11-02 UTC: p95 980ms2026-11-03 UTC: p95 810ms2026-11-04 UTC: p95 918ms2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5
US-West
1.4sp95 · latest
5s2.5s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 283ms2026-10-08 UTC: p95 321ms2026-10-09 UTC: p95 317ms2026-10-10 UTC: p95 285ms2026-10-11 UTC: p95 268ms2026-10-12 UTC: p95 274ms2026-10-13 UTC: p95 333ms2026-10-14 UTC: p95 276ms2026-10-15 UTC: p95 312ms2026-10-16 UTC: p95 362ms2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 1.0s2026-10-24 UTC: p95 1.1s2026-10-25 UTC: p95 1.0s2026-10-26 UTC: p95 1.3s2026-10-27 UTC: p95 1.4s2026-10-28 UTC: p95 990ms2026-10-29 UTC: p95 984ms2026-10-30 UTC: p95 1.0s2026-10-31 UTC: p95 1.1s2026-11-01 UTC: p95 1.0s2026-11-02 UTC: p95 1.4s2026-11-03 UTC: p95 2.6s2026-11-04 UTC: p95 1.1s2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5
Europe
930msp95 · 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-10-07 UTC: p95 276ms2026-10-08 UTC: p95 179ms2026-10-09 UTC: p95 166ms2026-10-10 UTC: p95 181ms2026-10-11 UTC: p95 228ms2026-10-12 UTC: p95 289ms2026-10-13 UTC: p95 153ms2026-10-14 UTC: p95 182ms2026-10-15 UTC: p95 161ms2026-10-16 UTC: p95 169ms2026-10-17 UTC: p95 471ms2026-10-18 UTC: p95 625ms2026-10-19 UTC: p95 861ms2026-10-20 UTC: p95 638ms2026-10-21 UTC: p95 655ms2026-10-22 UTC: p95 658ms2026-10-23 UTC: p95 693ms2026-10-24 UTC: p95 672ms2026-10-25 UTC: p95 621ms2026-10-26 UTC: p95 896ms2026-10-27 UTC: p95 797ms2026-10-28 UTC: p95 812ms2026-10-29 UTC: p95 572ms2026-10-30 UTC: p95 509ms2026-10-31 UTC: p95 464ms2026-11-01 UTC: p95 467ms2026-11-02 UTC: p95 595ms2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 790ms2026-11-05 UTC: p95 930ms
Oct 7Oct 21Nov 5
Asia-Pacific
2.6sp95 · latest
10s5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 926ms2026-10-08 UTC: p95 803ms2026-10-09 UTC: p95 844ms2026-10-10 UTC: p95 814ms2026-10-11 UTC: p95 816ms2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 773ms2026-10-14 UTC: p95 827ms2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 874ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.8s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 1.8s2026-10-21 UTC: p95 1.7s2026-10-22 UTC: p95 1.8s2026-10-23 UTC: p95 2.1s2026-10-24 UTC: p95 2.0s2026-10-25 UTC: p95 1.8s2026-10-26 UTC: p95 2.3s2026-10-27 UTC: p95 6.5s2026-10-28 UTC: p95 1.7s2026-10-29 UTC: p95 2.3s2026-10-30 UTC: p95 1.8s2026-10-31 UTC: p95 1.8s2026-11-01 UTC: p95 1.9s2026-11-02 UTC: p95 1.8s2026-11-03 UTC: p95 2.1s2026-11-04 UTC: p95 2.6s2026-11-05 UTC: p95 2.6s
Oct 7Oct 21Nov 5
US-Central
786msp95 · 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-10-07 UTC: p95 356ms2026-10-08 UTC: p95 214ms2026-10-09 UTC: p95 330ms2026-10-10 UTC: p95 344ms2026-10-11 UTC: p95 370ms2026-10-12 UTC: p95 286ms2026-10-13 UTC: p95 258ms2026-10-14 UTC: p95 350ms2026-10-15 UTC: p95 315ms2026-10-16 UTC: p95 382ms2026-10-17 UTC: p95 750ms2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.0s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 1.0s2026-10-22 UTC: p95 1.0s2026-10-23 UTC: p95 1.1s2026-10-24 UTC: p95 1.2s2026-10-25 UTC: p95 1.1s2026-10-26 UTC: p95 1.3s2026-10-27 UTC: p95 1.2s2026-10-28 UTC: p95 1.2s2026-10-29 UTC: p95 1.2s2026-10-30 UTC: p95 1.0s2026-10-31 UTC: p95 1.2s2026-11-01 UTC: p95 1.2s2026-11-02 UTC: p95 1.2s2026-11-03 UTC: p95 584ms2026-11-04 UTC: p95 583ms2026-11-05 UTC: p95 786ms
Oct 7Oct 21Nov 5
Canada
919msp95 · 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-10-07 UTC: p95 380ms2026-10-08 UTC: p95 309ms2026-10-09 UTC: p95 387ms2026-10-10 UTC: p95 390ms2026-10-11 UTC: p95 386ms2026-10-12 UTC: p95 392ms2026-10-13 UTC: p95 374ms2026-10-14 UTC: p95 418ms2026-10-15 UTC: p95 217ms2026-10-16 UTC: p95 529ms2026-10-17 UTC: p95 413ms2026-10-18 UTC: p95 839ms2026-10-19 UTC: p95 407ms2026-10-20 UTC: p95 705ms2026-10-21 UTC: p95 635ms2026-10-22 UTC: p95 838ms2026-10-23 UTC: p95 681ms2026-10-24 UTC: p95 731ms2026-10-25 UTC: p95 678ms2026-10-26 UTC: p95 1.3s2026-10-27 UTC: p95 1.0s2026-10-28 UTC: p95 742ms2026-10-29 UTC: p95 1.1s2026-10-30 UTC: p95 1.0s2026-10-31 UTC: p95 1.3s2026-11-01 UTC: p95 1.2s2026-11-02 UTC: p95 1.3s2026-11-03 UTC: p95 702ms2026-11-04 UTC: p95 935ms2026-11-05 UTC: p95 919ms
Oct 7Oct 21Nov 5
UK
4.0sp95 · latest
5s2.5s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 417ms2026-10-08 UTC: p95 546ms2026-10-09 UTC: p95 575ms2026-10-10 UTC: p95 656ms2026-10-11 UTC: p95 1.5s2026-10-12 UTC: p95 669ms2026-10-13 UTC: p95 382ms2026-10-14 UTC: p95 517ms2026-10-15 UTC: p95 417ms2026-10-16 UTC: p95 498ms2026-10-17 UTC: p95 703ms2026-10-18 UTC: p95 893ms2026-10-19 UTC: p95 759ms2026-10-20 UTC: p95 973ms2026-10-21 UTC: p95 701ms2026-10-22 UTC: p95 1.0s2026-10-23 UTC: p95 726ms2026-10-24 UTC: p95 769ms2026-10-25 UTC: p95 968ms2026-10-26 UTC: p95 1.4s2026-10-27 UTC: p95 1.0s2026-10-28 UTC: p95 845ms2026-10-29 UTC: p95 1.2s2026-10-30 UTC: p95 759ms2026-10-31 UTC: p95 735ms2026-11-01 UTC: p95 828ms2026-11-02 UTC: p95 985ms2026-11-03 UTC: p95 1.2s2026-11-04 UTC: p95 1.1s2026-11-05 UTC: p95 4.0s
Oct 7Oct 21Nov 5
Southeast Asia
3.8sp95 · 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-10-07 UTC: p95 2.3s2026-10-08 UTC: p95 2.3s2026-10-09 UTC: p95 2.0s2026-10-10 UTC: p95 1.9s2026-10-11 UTC: p95 2.1s2026-10-12 UTC: p95 2.1s2026-10-13 UTC: p95 2.1s2026-10-14 UTC: p95 2.3s2026-10-15 UTC: p95 2.1s2026-10-16 UTC: p95 2.1s2026-10-17 UTC: p95 2.2s2026-10-18 UTC: p95 2.1s2026-10-19 UTC: p95 2.2s2026-10-20 UTC: p95 2.4s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 2.5s2026-10-23 UTC: p95 2.4s2026-10-24 UTC: p95 2.3s2026-10-25 UTC: p95 2.6s2026-10-26 UTC: p95 2.5s2026-10-27 UTC: p95 2.2s2026-10-28 UTC: p95 2.3s2026-10-29 UTC: p95 2.9s2026-10-30 UTC: p95 2.6s2026-10-31 UTC: p95 3.6s2026-11-01 UTC: p95 3.9s2026-11-02 UTC: p95 3.8s2026-11-03 UTC: p95 4.0s2026-11-04 UTC: p95 3.6s2026-11-05 UTC: p95 3.8s
Oct 7Oct 21Nov 5
Australia
3.9sp95 · 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-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.3s2026-10-09 UTC: p95 1.3s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.7s2026-10-12 UTC: p95 1.4s2026-10-13 UTC: p95 1.6s2026-10-14 UTC: p95 1.5s2026-10-15 UTC: p95 1.6s2026-10-16 UTC: p95 1.9s2026-10-17 UTC: p95 2.2s2026-10-18 UTC: p95 2.0s2026-10-19 UTC: p95 2.2s2026-10-20 UTC: p95 2.0s2026-10-21 UTC: p95 2.5s2026-10-22 UTC: p95 2.4s2026-10-23 UTC: p95 1.8s2026-10-24 UTC: p95 2.5s2026-10-25 UTC: p95 2.7s2026-10-26 UTC: p95 2.6s2026-10-27 UTC: p95 2.5s2026-10-28 UTC: p95 2.5s2026-10-29 UTC: p95 2.0s2026-10-30 UTC: p95 2.2s2026-10-31 UTC: p95 2.1s2026-11-01 UTC: p95 2.3s2026-11-02 UTC: p95 2.0s2026-11-03 UTC: p95 2.9s2026-11-04 UTC: p95 3.0s2026-11-05 UTC: p95 3.9s
Oct 7Oct 21Nov 5
South America
2.2sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 3.7s2026-10-08 UTC: p95 1.8s2026-10-09 UTC: p95 1.6s2026-10-10 UTC: p95 1.7s2026-10-11 UTC: p95 1.6s2026-10-12 UTC: p95 1.9s2026-10-13 UTC: p95 1.8s2026-10-14 UTC: p95 1.6s2026-10-15 UTC: p95 1.4s2026-10-16 UTC: p95 1.7s2026-10-17 UTC: p95 1.6s2026-10-18 UTC: p95 1.8s2026-10-19 UTC: p95 1.8s2026-10-20 UTC: p95 1.8s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.8s2026-10-23 UTC: p95 6.0s2026-10-24 UTC: p95 1.8s2026-10-25 UTC: p95 1.8s2026-10-26 UTC: p95 1.9s2026-10-27 UTC: p95 1.8s2026-10-28 UTC: p95 1.7s2026-10-29 UTC: p95 1.7s2026-10-30 UTC: p95 1.4s2026-10-31 UTC: p95 1.4s2026-11-01 UTC: p95 1.3s2026-11-02 UTC: p95 1.4s2026-11-03 UTC: p95 2.0s2026-11-04 UTC: p95 3.2s2026-11-05 UTC: p95 2.2s
Oct 7Oct 21Nov 5

Check your own site while you wait on N26

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.

Get an email when our checks of N26 fail from two or more distant regions, and again when they pass

Get an email when our checks change

We will email you when our checks of N26 fail from two or more distant regions, and again when they pass. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when our checks fail from two or more distant regions, one when they pass, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is our own reading from outside. It is not N26's official status.

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: 472msstatus code: 200checked: Nov 5, 2026, 2:28 PM 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
      Checks passinglatency: 715msstatus code: 200checked: Nov 5, 2026, 2:26 PM 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
      Checks passinglatency: 604msstatus code: 200checked: Nov 5, 2026, 2:11 PM 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
      Checks passinglatency: 618msstatus code: 200checked: Nov 5, 2026, 2:13 PM 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
    Checks passinglatency: 1714msstatus code: 200checked: Nov 5, 2026, 2:29 PM 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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 168msstatus code: 200checked: Nov 5, 2026, 2:08 PM 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
      Checks passinglatency: 469msstatus code: 200checked: Nov 5, 2026, 2:13 PM 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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 2139msstatus code: 200checked: Nov 5, 2026, 1:57 PM 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
      Checks passinglatency: 2934msstatus code: 200checked: Nov 5, 2026, 2:25 PM 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
      Checks passinglatency: 2090msstatus code: 200checked: Nov 5, 2026, 1:46 PM 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 probe events

No probe events on record yet for N26.

check 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 check readings and N26's own claim at the time, side by side.

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

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

N26 uptime by RealUptime's checksLive, from this page's own readings.
[![N26 uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

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

How our checks compare with N26's stated SLA

At or above your target

Our checks of N26 failed for none over the last 30 days, which is 100% uptime by our checks. A 99.9% target allows 43 minutes over that period.

Our checks show no gap in this period. That does not rule out one you saw.

These figures come from our own checks of one public endpoint per service. They are not the service's real uptime. This is computed from our own checks, 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

What our check can and cannot see

A pass means the service's public web page loaded and answered normally. It does not show that the product, the API or sign-in behind it works; a page can load from a cache while the product is down.

Host checked: n26.com

RealUptime is not affiliated with N26; the name identifies what we checked, 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 is its front door only: a passing check means the endpoints above answered, not that the underlying product or account features work. Read the full methodology.