Skip to content

Outage tracker / N26

Is N26 down?

I'm having a problem

Operationalchecked 18 minutes ago

We reached N26 from all 10 regions we check.

As of Oct 5, 2026, 7:59 PM UTC, N26 answered RealUptime's probes in all 10 regions that returned a reading.

Reachability verified

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

our independent probeslive · checked Oct 5, 2026, 7:59 PM UTC
US-East225 msOperational
US-West124 msOperational
Europe137 msOperational
Asia-Pacific469 msOperational
US-Central89 msOperational
Canada197 msOperational
UK846 msOperational
Southeast Asia1057 msOperational
Australia803 msOperational
South America1065 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
340msp95 · 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 284ms2026-09-07 UTC: p95 306ms2026-09-08 UTC: p95 292ms2026-09-09 UTC: p95 299ms2026-09-10 UTC: p95 294ms2026-09-11 UTC: p95 326ms2026-09-12 UTC: p95 291ms2026-09-13 UTC: p95 321ms2026-09-14 UTC: p95 329ms2026-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 340ms
Sep 6Sep 20Oct 5
US-West
213msp95 · 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-06 UTC: p95 367ms2026-09-07 UTC: p95 689ms2026-09-08 UTC: p95 329ms2026-09-09 UTC: p95 801ms2026-09-10 UTC: p95 401ms2026-09-11 UTC: p95 590ms2026-09-12 UTC: p95 175ms2026-09-13 UTC: p95 576ms2026-09-14 UTC: p95 254ms2026-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 213ms
Sep 6Sep 20Oct 5
Europe
188msp95 · 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 206ms2026-09-07 UTC: p95 290ms2026-09-08 UTC: p95 268ms2026-09-09 UTC: p95 216ms2026-09-10 UTC: p95 361ms2026-09-11 UTC: p95 430ms2026-09-12 UTC: p95 339ms2026-09-13 UTC: p95 323ms2026-09-14 UTC: p95 266ms2026-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 188ms
Sep 6Sep 20Oct 5
Asia-Pacific
976msp95 · 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 877ms2026-09-07 UTC: p95 839ms2026-09-08 UTC: p95 1.0s2026-09-09 UTC: p95 1.3s2026-09-10 UTC: p95 1.0s2026-09-11 UTC: p95 1.1s2026-09-12 UTC: p95 891ms2026-09-13 UTC: p95 844ms2026-09-14 UTC: p95 961ms2026-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 976ms
Sep 6Sep 20Oct 5
US-Central
299msp95 · 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-06 UTC: p95 537ms2026-09-07 UTC: p95 448ms2026-09-08 UTC: p95 278ms2026-09-09 UTC: p95 380ms2026-09-10 UTC: p95 237ms2026-09-11 UTC: p95 360ms2026-09-12 UTC: p95 388ms2026-09-13 UTC: p95 395ms2026-09-14 UTC: p95 426ms2026-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 299ms
Sep 6Sep 20Oct 5
Canada
342msp95 · 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 435ms2026-09-07 UTC: p95 308ms2026-09-08 UTC: p95 339ms2026-09-09 UTC: p95 291ms2026-09-10 UTC: p95 340ms2026-09-11 UTC: p95 259ms2026-09-12 UTC: p95 355ms2026-09-13 UTC: p95 234ms2026-09-14 UTC: p95 269ms2026-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 342ms
Sep 6Sep 20Oct 5
UK
818msp95 · 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-06 UTC: p95 498ms2026-09-07 UTC: p95 604ms2026-09-08 UTC: p95 1.1s2026-09-09 UTC: p95 813ms2026-09-10 UTC: p95 599ms2026-09-11 UTC: p95 377ms2026-09-12 UTC: p95 422ms2026-09-13 UTC: p95 351ms2026-09-14 UTC: p95 346ms2026-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 818ms
Sep 6Sep 20Oct 5
Southeast Asia
1.9sp95 · 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-06 UTC: p95 2.2s2026-09-07 UTC: p95 1.9s2026-09-08 UTC: p95 2.1s2026-09-09 UTC: p95 1.9s2026-09-10 UTC: p95 2.4s2026-09-11 UTC: p95 2.3s2026-09-12 UTC: p95 1.6s2026-09-13 UTC: p95 1.7s2026-09-14 UTC: p95 1.4s2026-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 1.9s
Sep 6Sep 20Oct 5
Australia
941msp95 · 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-06 UTC: p95 1.2s2026-09-07 UTC: p95 1.4s2026-09-08 UTC: p95 1.3s2026-09-09 UTC: p95 1.6s2026-09-10 UTC: p95 1.3s2026-09-11 UTC: p95 1.2s2026-09-12 UTC: p95 1.4s2026-09-13 UTC: p95 1.1s2026-09-14 UTC: p95 1.2s2026-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 941ms
Sep 6Sep 20Oct 5
South America
1.6sp95 · 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.3s2026-09-09 UTC: p95 1.1s2026-09-10 UTC: p95 1.3s2026-09-11 UTC: p95 873ms2026-09-12 UTC: p95 1.0s2026-09-13 UTC: p95 964ms2026-09-14 UTC: p95 1.3s2026-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.6s
Sep 6Sep 20Oct 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.

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

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.

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: 225msstatus code: 200checked: Oct 5, 2026, 7:57 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
      Operationallatency: 124msstatus code: 200checked: Oct 5, 2026, 7:47 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
      Operationallatency: 89msstatus code: 200checked: Oct 5, 2026, 7:21 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
      Operationallatency: 197msstatus code: 200checked: Oct 5, 2026, 7:35 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
    Operationallatency: 1065msstatus code: 200checked: Oct 5, 2026, 7:57 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
    OperationalEurope, UK
    • Europe
      Operationallatency: 137msstatus code: 200checked: Oct 5, 2026, 7:55 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
      Operationallatency: 846msstatus code: 200checked: Oct 5, 2026, 7:54 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
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 469msstatus code: 200checked: Oct 5, 2026, 7:56 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
      Operationallatency: 1057msstatus code: 200checked: Oct 5, 2026, 7:41 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
      Operationallatency: 803msstatus code: 200checked: Oct 5, 2026, 7:59 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 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

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 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 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.