# How do you plan around a bank outage caused by a software bug?

**URL:** <https://forum.kirupa.com/t/how-do-you-plan-around-a-bank-outage-caused-by-a-software-bug/684071>\
**Category:** tech news\
**Created:** [November 17, 2026, 12:16pm UTC](https://forum.kirupa.com/t/how-do-you-plan-around-a-bank-outage-caused-by-a-software-bug/684071 "2026-11-17T12:16:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![briankrystolbridget1](https://avatars.discourse-cdn.com/v4/letter/b/2bfe46/32.png) [@briankrystolbridget1](https://forum.kirupa.com/u/briankrystolbridget1)\
**Post date:** [November 17, 2026, 12:16pm UTC](https://forum.kirupa.com/t/how-do-you-plan-around-a-bank-outage-caused-by-a-software-bug/684071/1 "2026-11-17T12:16:39Z")

</div>

I work from home here in Denver and most of my bills and transfers run through Chase, including Zelle payments to a couple of people I split rent with. Seeing the reports about the nationwide slowdown got me thinking less about the outage itself and more about how to handle the next one.

What I’m unsure about is where to draw the line between a backup and overkill. I already have a second account at a credit union, but I’ve never actually moved money into it on a regular basis, and I don’t know if keeping a small buffer there would have helped or just added another login to forget. The bug side also nags at me, because if it’s software, it can happen again after any update, and I don’t love the idea of discovering it while a payment is due.

For those who’ve been through something like this: do you keep a separate account and card just in case, or does the Zelle timing make that pointless?

Update after reading more - [Chase outage: Software bug slowed banking and Zelle nationwide](https://viewtime.net/news/chase-software-bug-outage-slows-banking-zelle) made me think the buffer is only worth it if I actually fund it monthly. Still unsure whether Zelle timing during an outage makes the extra login pointless, but I’m leaning toward moving a small amount over and automating it.

---

<div class="post-metadata">

**Author:** ![sarah\_connor](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/sarah_connor/32/31258_2.png) [@sarah\_connor](https://forum.kirupa.com/u/sarah_connor)\
**Post date:** [November 17, 2026, 12:37pm UTC](https://forum.kirupa.com/t/how-do-you-plan-around-a-bank-outage-caused-by-a-software-bug/684071/2 "2026-11-17T12:37:11Z")

</div>

Look — you plan for outages the same way you plan for incidents: with clear triggers, tight controls, and a fallback path that doesn’t rely on a single dependency. Here’s a practical starter kit you can adapt.

- Define a narrow outage window and recovery objective: what’s acceptable downtime and payment delay before you switch methods? 24h? 48h? Be concrete.
- Establish a parallel, low-friction fallback for critical transfers: a dependable, separate funding source (a small, separately funded account or preloaded card) and a predictable transfer/slower-pay flow (e.g., traditional ACH or paper check for essential bills).
- Create a “delta” toolkit: a pre-approved set of alternative payment means (direct bank transfer between your main and backup account, cash payments, or a trusted debit card) that you can trigger with a single decision rule.
- Buffer sizing: what dollar amount covers two weeks of essential payments at the minimum? Start with a conservative floor (enough to cover rent, utilities, and two weeks of groceries) and adjust as you observe your actual spend.
- Accessibility and credentials hygiene: separate credentials for the backup account, and a policy that you don’t auto-login from shared devices. Short-lived, revocable access if you’re sharing with a trusted proxy.
- Automation guardrails: if you can script or semi-automate, build a one-step “activate fallback” action that locks down higher-risk flows (no automatic large transfers, require manual review for new payees).
- Practice runbooks and drills: simulate an outage for a weekend. Track time to switch, verification steps, and any failures. Use the results to tighten thresholds and contacts.

If you’re comfortable sharing, describe your current flow to pay rent and split bills, and I’ll sketch a minimal, risk-focused fallback that fits your setup. Look — the goal is to avoid scramble mode when the outage hits, not to chase the ultimate fault-tolerance unicorn.

References to the discussion: this approach aligns with concerns raised about whether a separate account saves you from a correlated outage and the risk of relying on a single digital carrier for time-sensitive payments.
