Is Chase down right now?

Yes. HostTracker lets you add any URL - including third-party services you depend on, not just your own website - as a monitored target, and notifies you automatically the moment it becomes unreachable. Before sending an alert, HostTracker re-verifies a failure from multiple locations in its 300+-location network, so you're notified about real, confirmed outages rather than a single location's momentary blip. The free plan checks two monitors every 30 minutes indefinitely at no cost; paid plans check as often as once a minute, with alerts available through SMS, email, voice call, and several messenger apps.

No - as of the most recent check, www.chase.com is responding normally to HostTracker's monitoring network, and has been up for 17h 33m. Over the last 24 hours it recorded 100.00% uptime across 0 incidents. If it is failing for you specifically, the cause is local - your network, DNS cache, or a regional route - and the live probe results above will show which locations, if any, are affected.

No - as of the most recent check, www.chase.com is responding normally to HostTracker's monitoring network, and has been up for 17h 33m. Over the last 24 hours it recorded 100.00% uptime across 0 incidents. If it is failing for you specifically, the cause is local - your network, DNS cache, or a regional route - and the live probe results above will show which locations, if any, are affected.

No - as of the most recent check, www.chase.com is responding normally to HostTracker's monitoring network, and has been up for 17h 33m. Over the last 24 hours it recorded 100.00% uptime across 0 incidents. If it is failing for you specifically, the cause is local - your network, DNS cache, or a regional route - and the live probe results above will show which locations, if any, are affected.

No - as of the most recent check, www.chase.com is responding normally to HostTracker's monitoring network, and has been up for 17h 33m. Over the last 24 hours it recorded 100.00% uptime across 0 incidents. If it is failing for you specifically, the cause is local - your network, DNS cache, or a regional route - and the live probe results above will show which locations, if any, are affected.

It can be either side. Zelle is built directly into the Chase Mobile app and chase.com rather than run as its own app, but a transfer still depends on the wider Zelle network and, for a recipient at another bank, on that bank's own integration. If every other Chase feature works normally and only Zelle transfers fail, the problem is more likely with Zelle's network or the recipient's bank than with Chase itself.

A single decline is rarely a sign of an outage. Card purchases are authorized by the Visa or Mastercard network in real time, and a decline can come from that network, a spending limit, a fraud hold, or insufficient funds, not from Chase's banking systems being unavailable. A genuine Chase-side problem looks broader: the app and chase.com are both slow or unreachable, and other account actions fail too, not just one card swipe.

The mobile app and the chase.com website are separate pieces of software, so one working while the other does not is a real and fairly common pattern rather than a contradiction. It usually points to a problem specific to the website, or to that browser or connection, rather than to your account or to Chase's banking systems broadly. Trying a different browser is a reasonable first step before assuming a wider issue.

An app or website outage affects access, not the funds themselves, which remain on Chase's core banking systems regardless of whether the app or site can currently display them. The practical concern during an outage is being unable to check a balance or move money right away, not the money being at risk. If a balance or transaction genuinely looks wrong once access is restored, that is a matter for Chase support with your transaction history, not something the outage itself would explain.