Silicon Valley Bank Failure: Duration, Liquidity and Deposit Risk
A security can have low credit risk and still create severe market and liquidity risk. Silicon Valley Bank demonstrates what happens when long-duration assets meet concentrated, fast-moving deposits.
Current position
US regulators closed Silicon Valley Bank on 10 March 2023 and the FDIC was appointed receiver. The bank reported about US$209 billion in total assets at 31 December 2022. Federal Reserve reviews identified weaknesses in bank management and supervision, including interest-rate and liquidity risk. The case should be framed within the US regulatory and deposit-insurance context.
Key facts at a glance
| Closure date | 10 March 2023 |
|---|---|
| Receiver | US Federal Deposit Insurance Corporation |
| Year-end 2022 assets | Approximately US$209 billion |
| Risk mix | Duration losses, concentrated deposits and rapid withdrawals |
What this means in practice
1. Read the substance
Low default risk does not eliminate price sensitivity when interest rates rise.
2. Measure the right risk
Unrealised losses become liquidity problems when assets must be sold to meet withdrawals.
3. Turn the lesson into a control
Depositor concentration and digital banking can accelerate a run far beyond historical assumptions.
Practical example
A bank buys a 10-year bond at a low yield. When market yields rise, the bond’s price falls. If the bank can hold to maturity the loss may remain unrealised; if depositors demand cash, selling crystallises it.
A four-step decision framework
1. Identify the exact entity and period
Start with the legal entity, forum, reporting period or product actually covered. In this article, the first anchor is closure date: 10 March 2023. Similar brand names or later events should not be assumed to have the same treatment.
2. Reconcile the number with its definition
The next anchor is receiver: US Federal Deposit Insurance Corporation. Check whether a figure is a balance, flow, claim, estimate, transaction value, accounting revenue or management-reported operating metric before comparing it.
3. Read the operative status
Use the latest applicable order, filing or policy statement and note its date. Do not rely on an older headline where an appeal, implementation step, later law or winding-up event has changed the position.
4. Convert the lesson into a control
The useful output is a documented action: Identify the regulated entity, product issuer and legal status relevant to Silicon Valley Bank Failure. Assign an owner, a deadline and the evidence needed to show that the control worked.
Action checklist
- Identify the regulated entity, product issuer and legal status relevant to Silicon Valley Bank Failure.
- Reconcile balances, rates, maturities and transaction references.
- Model liquidity and rate sensitivity under a realistic adverse scenario.
- Check official customer instructions before moving or committing funds.
- Escalate unresolved errors through the institution’s formal grievance route.
Evidence and document checklist
- Account statements and transaction references
- Product terms, sanction letter or rate-reset notice
- KYC and customer-service correspondence
- Liquidity or maturity analysis
- Regulator communication and complaint acknowledgement
Common mistakes and red flags
Common mistakes
- Assuming a brand and its regulated entity are identical
- Comparing balances, flows and revenue as though they are the same metric
- Ignoring reset dates, fees or maturity mismatch
- Sharing OTP, PIN or credentials during a dispute
Red flags
- Unexplained transaction or balance mismatch
- Concentrated short-term funding against long-term assets
- Repeated unresolved supervisory or audit issues
- Requests to use unofficial links or accounts
Escalation route
Complain first to the regulated entity. If eligible and unresolved, use RBI’s Complaint Management System or the applicable regulator and preserve every acknowledgement.