by HonkWatch

Is Commerzbank down?

No. Commerzbank is working. Updated 4 Nov, 12:46 UTC, 4 min ago · No status page: this is what our own checks see No problems recorded since 4 Nov 2026.
Having trouble with Commerzbank?

Last 9030 days

Collecting since 4 Nov; the uptime figure shows after the first hour of readings

Of the last 90 days, 0 had a partial or major outage, 0 had maintenance only and 89 have no data. Recent problems are listed in a table further down.

90 days ago30 days agoToday

No problems Partial outage Major outage Maintenance No data yet

Last 24 hours

Every 15 minutes, hours in UTC

Bars: the share of our own checks of commerzbank.de that failed (872 checks). Our checks showed no problem in this time. We don't collect user reports.

0%26%53% 18:0000:0006:0012:00 53% of 170 checks failed44% of 133 checks failed44% of 135 checks failed41% of 127 checks failed44% of 135 checks failed42% of 129 checks failed42% of 43 checks failed

Our own checks of commerzbank.de

Every 5 minutes, from our probes

9 of 34 cities can't reach commerzbank.de.

Los Angeles: loaded in 2144 ms St. Louis: loaded in 875 ms Johannesburg: loaded in 980 ms Hong Kong: loaded in 904 ms Cape Town: loaded in 911 ms Tokyo: loaded in 1093 ms Dallas: loaded in 732 ms New York: loaded in 538 ms Melbourne: loaded in 1259 ms Delhi: loaded in 1109 ms Sydney: loaded in 1432 ms Mumbai: loaded in 706 ms Seattle: loaded in 932 ms Hamina: loaded in 281 ms Singapore: loaded in 759 ms Seoul: loaded in 1080 ms Tel Aviv: loaded in 397 ms Querétaro: loaded in 854 ms Portsmouth: loaded in 330 ms New Jersey: loaded in 801 ms Jakarta: loaded in 924 ms São Paulo: loaded in 1508 ms Toronto: loaded in 581 ms Doha: loaded in 561 ms Lauterbourg: loaded in 191 ms Osaka: could not load it (ConnectionResetError: [Errno 104] Connection reset by peer) London: could not load it (ConnectionResetError: [Errno 104] Connection reset by peer) Madrid: could not load it (ConnectionResetError: [Errno 104] Connection reset by peer) Bangalore: could not load it (ConnectionResetError: [Errno 104] Connection reset by peer) Atlanta: could not load it (ConnectionResetError: [Errno 104] Connection reset by peer) Amsterdam: could not load it (ConnectionResetError: [Errno 104] Connection reset by peer) Frankfurt: could not load it (ConnectionResetError: [Errno 104] Connection reset by peer) Warsaw: could not load it (ConnectionResetError: [Errno 104] Connection reset by peer) Santiago: could not load it (ConnectionResetError: [Errno 104] Connection reset by peer)
  • OsakaConnection reset by the server624 ms, 4 min ago
  • LondonConnection reset by the server229 ms, 4 min ago
  • MadridConnection reset by the server66 ms, 4 min ago
  • BangaloreConnection reset by the server358 ms, 4 min ago
  • AtlantaConnection reset by the server328 ms, 4 min ago
  • AmsterdamConnection reset by the server20 ms, 4 min ago
  • FrankfurtConnection reset by the server162 ms, 4 min ago
  • WarsawConnection reset by the server40 ms, 4 min ago
  • SantiagoConnection reset by the server398 ms, 4 min ago
  • Los AngelesReachable2144 ms, 4 min ago
  • St. LouisReachable875 ms, 4 min ago
  • JohannesburgReachable980 ms, 4 min ago
  • Hong KongReachable904 ms, 4 min ago
  • Cape TownReachable911 ms, 4 min ago
  • TokyoReachable1093 ms, 4 min ago
  • DallasReachable732 ms, 4 min ago
  • New YorkReachable538 ms, 4 min ago
  • MelbourneReachable1259 ms, 4 min ago
  • DelhiReachable1109 ms, 4 min ago
  • SydneyReachable1432 ms, 4 min ago
  • MumbaiReachable706 ms, 4 min ago
  • SeattleReachable932 ms, 4 min ago
  • HaminaReachable281 ms, 4 min ago
  • SingaporeReachable759 ms, 4 min ago
  • SeoulReachable1080 ms, 4 min ago
  • Tel AvivReachable397 ms, 4 min ago
  • QuerétaroReachable854 ms, 4 min ago
  • PortsmouthReachable330 ms, 4 min ago
  • New JerseyReachable801 ms, 4 min ago
  • JakartaReachable924 ms, 4 min ago
  • São PauloReachable1508 ms, 4 min ago
  • TorontoReachable581 ms, 4 min ago
  • DohaReachable561 ms, 4 min ago
  • LauterbourgReachable191 ms, 4 min ago

We load commerzbank.de the way a visitor would and note whether it answers.

No status page

Commerzbank does not publish a status page, so there is nothing for us to read. What you see here is what we measure ourselves: its website is loaded from our probes in 34 cities every 5 minutes. We show a problem when a quarter of the cities that are working normally can't load it, and an outage when half can't. A city that has not been able to load it once in the last two days is left out: some sites only open for people in their own country, and that is not an outage. When too few cities are left, we say we can't tell.

Recent problems

No problems recorded since 4 Nov 2026.

Alert me when Commerzbank is down

HonkWatch can load Commerzbank's website for you from several cities and alert you by email, Slack, Discord or Telegram when it stops answering.

Start free Log in

More in Finance and accounting

Questions

Is Commerzbank down, or is it just me?

Our checks reach Commerzbank's website from most of our cities. If it isn't working for you, the cause is more likely near you: your network, your browser, or a problem only in your area. Try another network or device.

How do we know?

Commerzbank has no public status page. We load commerzbank.de from our own probes in several cities and note whether it answers. We don't guess from social media posts or reports.

How often do we check?

The website every 5 minutes, day and night. We keep 90 days of history: a day we have no reading for shows as "no data yet", never as working.

Our own checks of the Commerzbank website. HonkWatch also checks websites from 34 cities.

← All services