Skip to content

Outage tracker / N26

Is N26 down?

I'm having a problem

Checks passingchecked 6 minutes ago

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

As of Oct 14, 2026, 5:07 AM 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 53 days we have checked it (since Aug 22, 2026). This does not show N26 works for users.

our check readinglive · checked Oct 14, 2026, 5:07 AM UTC
US-East261 msChecks passing
US-West103 msChecks passing
Europe39 msChecks passing
Asia-Pacific537 msChecks passing
US-Central157 msChecks passing
Canada396 msChecks passing
UK396 msChecks passing
Southeast Asia1892 msChecks passing
Australia1385 msChecks passing
South America993 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
267msp95 · 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-15 UTC: p95 388ms2026-09-16 UTC: p95 505ms2026-09-17 UTC: p95 463ms2026-09-18 UTC: p95 497ms2026-09-19 UTC: p95 399ms2026-09-20 UTC: p95 388ms2026-09-21 UTC: p95 358ms2026-09-22 UTC: p95 331ms2026-09-23 UTC: p95 436ms2026-09-24 UTC: p95 398ms2026-09-25 UTC: p95 354ms2026-09-26 UTC: p95 371ms2026-09-27 UTC: p95 391ms2026-09-28 UTC: p95 417ms2026-09-29 UTC: p95 354ms2026-09-30 UTC: p95 405ms2026-10-01 UTC: p95 321ms2026-10-02 UTC: p95 292ms2026-10-03 UTC: p95 351ms2026-10-04 UTC: p95 282ms2026-10-05 UTC: p95 316ms2026-10-06 UTC: p95 393ms2026-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 267ms
Sep 15Sep 29Oct 14
US-West
269msp95 · 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-09-15 UTC: p95 260ms2026-09-16 UTC: p95 254ms2026-09-17 UTC: p95 396ms2026-09-18 UTC: p95 361ms2026-09-19 UTC: p95 233ms2026-09-20 UTC: p95 248ms2026-09-21 UTC: p95 343ms2026-09-22 UTC: p95 357ms2026-09-23 UTC: p95 296ms2026-09-24 UTC: p95 592ms2026-09-25 UTC: p95 421ms2026-09-26 UTC: p95 456ms2026-09-27 UTC: p95 312ms2026-09-28 UTC: p95 361ms2026-09-29 UTC: p95 295ms2026-09-30 UTC: p95 438ms2026-10-01 UTC: p95 455ms2026-10-02 UTC: p95 361ms2026-10-03 UTC: p95 364ms2026-10-04 UTC: p95 273ms2026-10-05 UTC: p95 245ms2026-10-06 UTC: p95 223ms2026-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 269ms
Sep 15Sep 29Oct 14
Europe
195msp95 · 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-15 UTC: p95 244ms2026-09-16 UTC: p95 341ms2026-09-17 UTC: p95 360ms2026-09-18 UTC: p95 274ms2026-09-19 UTC: p95 274ms2026-09-20 UTC: p95 305ms2026-09-21 UTC: p95 464ms2026-09-22 UTC: p95 353ms2026-09-23 UTC: p95 548ms2026-09-24 UTC: p95 508ms2026-09-25 UTC: p95 443ms2026-09-26 UTC: p95 359ms2026-09-27 UTC: p95 474ms2026-09-28 UTC: p95 434ms2026-09-29 UTC: p95 347ms2026-09-30 UTC: p95 257ms2026-10-01 UTC: p95 193ms2026-10-02 UTC: p95 305ms2026-10-03 UTC: p95 235ms2026-10-04 UTC: p95 261ms2026-10-05 UTC: p95 200ms2026-10-06 UTC: p95 186ms2026-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 195ms
Sep 15Sep 29Oct 14
Asia-Pacific
817msp95 · 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-15 UTC: p95 959ms2026-09-16 UTC: p95 788ms2026-09-17 UTC: p95 898ms2026-09-18 UTC: p95 762ms2026-09-19 UTC: p95 795ms2026-09-20 UTC: p95 875ms2026-09-21 UTC: p95 744ms2026-09-22 UTC: p95 864ms2026-09-23 UTC: p95 768ms2026-09-24 UTC: p95 875ms2026-09-25 UTC: p95 758ms2026-09-26 UTC: p95 838ms2026-09-27 UTC: p95 909ms2026-09-28 UTC: p95 937ms2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 1.2s2026-10-02 UTC: p95 981ms2026-10-03 UTC: p95 922ms2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 1.0s2026-10-06 UTC: p95 995ms2026-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 817ms
Sep 15Sep 29Oct 14
US-Central
436msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 343ms2026-09-16 UTC: p95 206ms2026-09-17 UTC: p95 404ms2026-09-18 UTC: p95 291ms2026-09-19 UTC: p95 497ms2026-09-20 UTC: p95 312ms2026-09-21 UTC: p95 338ms2026-09-22 UTC: p95 322ms2026-09-23 UTC: p95 379ms2026-09-24 UTC: p95 252ms2026-09-25 UTC: p95 311ms2026-09-26 UTC: p95 385ms2026-09-27 UTC: p95 164ms2026-09-28 UTC: p95 388ms2026-09-29 UTC: p95 478ms2026-09-30 UTC: p95 210ms2026-10-01 UTC: p95 599ms2026-10-02 UTC: p95 317ms2026-10-03 UTC: p95 400ms2026-10-04 UTC: p95 350ms2026-10-05 UTC: p95 287ms2026-10-06 UTC: p95 334ms2026-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 436ms
Sep 15Sep 29Oct 14
Canada
417msp95 · 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-15 UTC: p95 252ms2026-09-16 UTC: p95 406ms2026-09-17 UTC: p95 369ms2026-09-18 UTC: p95 472ms2026-09-19 UTC: p95 578ms2026-09-20 UTC: p95 465ms2026-09-21 UTC: p95 555ms2026-09-22 UTC: p95 445ms2026-09-23 UTC: p95 344ms2026-09-24 UTC: p95 386ms2026-09-25 UTC: p95 477ms2026-09-26 UTC: p95 490ms2026-09-27 UTC: p95 278ms2026-09-28 UTC: p95 421ms2026-09-29 UTC: p95 409ms2026-09-30 UTC: p95 271ms2026-10-01 UTC: p95 422ms2026-10-02 UTC: p95 351ms2026-10-03 UTC: p95 384ms2026-10-04 UTC: p95 425ms2026-10-05 UTC: p95 340ms2026-10-06 UTC: p95 396ms2026-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 417ms
Sep 15Sep 29Oct 14
UK
326msp95 · 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-15 UTC: p95 411ms2026-09-16 UTC: p95 420ms2026-09-17 UTC: p95 442ms2026-09-18 UTC: p95 493ms2026-09-19 UTC: p95 423ms2026-09-20 UTC: p95 577ms2026-09-21 UTC: p95 805ms2026-09-22 UTC: p95 683ms2026-09-23 UTC: p95 528ms2026-09-24 UTC: p95 589ms2026-09-25 UTC: p95 577ms2026-09-26 UTC: p95 597ms2026-09-27 UTC: p95 534ms2026-09-28 UTC: p95 650ms2026-09-29 UTC: p95 696ms2026-09-30 UTC: p95 665ms2026-10-01 UTC: p95 682ms2026-10-02 UTC: p95 718ms2026-10-03 UTC: p95 734ms2026-10-04 UTC: p95 693ms2026-10-05 UTC: p95 777ms2026-10-06 UTC: p95 1.2s2026-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 326ms
Sep 15Sep 29Oct 14
Southeast Asia
2.4sp95 · 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-15 UTC: p95 1.5s2026-09-16 UTC: p95 1.5s2026-09-17 UTC: p95 1.6s2026-09-18 UTC: p95 1.8s2026-09-19 UTC: p95 1.6s2026-09-20 UTC: p95 1.8s2026-09-21 UTC: p95 2.6s2026-09-22 UTC: p95 2.4s2026-09-23 UTC: p95 2.9s2026-09-24 UTC: p95 2.3s2026-09-25 UTC: p95 2.6s2026-09-26 UTC: p95 2.1s2026-09-27 UTC: p95 2.5s2026-09-28 UTC: p95 2.4s2026-09-29 UTC: p95 2.3s2026-09-30 UTC: p95 2.2s2026-10-01 UTC: p95 2.4s2026-10-02 UTC: p95 1.8s2026-10-03 UTC: p95 2.1s2026-10-04 UTC: p95 2.0s2026-10-05 UTC: p95 2.0s2026-10-06 UTC: p95 1.7s2026-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.4s
Sep 15Sep 29Oct 14
Australia
1.2sp95 · 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-15 UTC: p95 1.1s2026-09-16 UTC: p95 1.1s2026-09-17 UTC: p95 1.2s2026-09-18 UTC: p95 1.2s2026-09-19 UTC: p95 1.2s2026-09-20 UTC: p95 1.4s2026-09-21 UTC: p95 1.4s2026-09-22 UTC: p95 1.3s2026-09-23 UTC: p95 1.2s2026-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 1.2s2026-09-27 UTC: p95 1.2s2026-09-28 UTC: p95 1.2s2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 1.4s2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 1.4s2026-10-05 UTC: p95 1.0s2026-10-06 UTC: p95 1.4s2026-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.2s
Sep 15Sep 29Oct 14
South America
1.6sp95 · 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-15 UTC: p95 1.3s2026-09-16 UTC: p95 1.3s2026-09-17 UTC: p95 1.5s2026-09-18 UTC: p95 1.5s2026-09-19 UTC: p95 1.6s2026-09-20 UTC: p95 1.3s2026-09-21 UTC: p95 1.2s2026-09-22 UTC: p95 1.3s2026-09-23 UTC: p95 1.5s2026-09-24 UTC: p95 1.6s2026-09-25 UTC: p95 1.7s2026-09-26 UTC: p95 1.6s2026-09-27 UTC: p95 1.5s2026-09-28 UTC: p95 1.7s2026-09-29 UTC: p95 1.4s2026-09-30 UTC: p95 1.7s2026-10-01 UTC: p95 1.7s2026-10-02 UTC: p95 1.4s2026-10-03 UTC: p95 1.8s2026-10-04 UTC: p95 1.6s2026-10-05 UTC: p95 1.6s2026-10-06 UTC: p95 1.4s2026-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.6s
Sep 15Sep 29Oct 14

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: 261msstatus code: 200checked: Oct 14, 2026, 5:03 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
      Checks passinglatency: 103msstatus code: 200checked: Oct 14, 2026, 5:03 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
      Checks passinglatency: 157msstatus code: 200checked: Oct 14, 2026, 4:27 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
      Checks passinglatency: 396msstatus code: 200checked: Oct 14, 2026, 4:40 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
    Checks passinglatency: 993msstatus code: 200checked: Oct 14, 2026, 5:03 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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 39msstatus code: 200checked: Oct 14, 2026, 5:07 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
      Checks passinglatency: 396msstatus code: 200checked: Oct 14, 2026, 4:59 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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 537msstatus code: 200checked: Oct 14, 2026, 5:06 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
      Checks passinglatency: 1892msstatus code: 200checked: Oct 14, 2026, 4:50 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
      Checks passinglatency: 1385msstatus code: 200checked: Oct 14, 2026, 5:07 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 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

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"></a>

The badge shows the share of our checks that passed 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 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 N26 down?", https://realuptime.io/outages/n26. 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.

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.