Skip to main content
developingInfrastructure

US Banking Sector Experiences Widespread Technical Glitch Disrupting Transactions

Multiple major US banks, including Chase, JPMorgan Chase, and Bank of America, experienced technical issues on Monday, disrupting customer transactions and banking app functionality.

AI disclosure: Model-written assessment of the linked reports, not a verified fact. Check the sources. How Mosaic works

Reported1 of 5 key facts linked
Not measuredno reporting-volume measure is served for situations
Not assessedno severity is rated for situations
2 publishers2 reports

: Stable (the model's assessment, not a measurement)

Nov 16First seen Nov 16Assessment written Nov 16
Why now
Newest report Nov 16: Widespread technical glitch disrupts major US banking apps (Le Soir).from the newest member report, published 16 Nov 20:24 UTC
Why it matters
The incident underscores systemic fragility in critical financial infrastructure, potentially impacting economic stability and public confidence.
Affected
United States (lead)countries named in the evidence; the lead is the country it is filed under, not an event location
Next catalyst
No scheduled catalyst known.Mosaic holds a schedule only for economic-calendar releases; 3 indicators to watch below
Watch in Monitor Export brief

Save keeps it in Monitor › Saved, without alerts. Watch opens Monitor with “US Banking Outage” as the subject.

Known and unknown

key facts by their own evidence status

Known

  • ReportedChase confirmed a 'technical issue' but stated customers retained account access.

Not established

  • Multiple US banks (Chase, JPMorgan Chase, Bank of America) experienced technical issues on Monday.
  • Customer transactions were disrupted, and banking apps were affected.
  • The incident may signal systemic infrastructure vulnerability.
  • The precise scope and root cause of the technical issues.

stated, not yet supported by linked evidence

Indicators to watch

  • →Official statements from affected banks detailing root cause and resolution.
  • →Regulatory investigations into the incident's impact and systemic implications.
  • →Reports of prolonged service disruptions or financial losses for customers.

what would change the read; not a schedule

Evidence

Reported · 2 reports · 2 distinct outlets

Central claim Chase and Other US Banks Hit by Technical Glitch Disrupting Transactions

2 reports, newest first. Each time is when the report was published, or when Mosaic recorded it if no publication time was given; event times are not recorded. Several outlets can carry one story, so a number of reports is not independent confirmation.

  1. published
  2. published

Connected

named in this situation's reports; not a claim that one causes another

Other situations in United States

Loading…

Actors

Loading…

Places

Anomalies

Loading…

Assessment

model confidence: under Technical details
Read the full assessment

Multiple major US banks, including Chase, JPMorgan Chase, and Bank of America, experienced technical issues on Monday, disrupting customer transactions and banking app functionality. While Chase confirmed a 'technical issue' and stated account access was maintained, the precise scope and root cause of the incident remain unclear. This event highlights potential vulnerabilities within the US financial infrastructure.

AI disclosure: Model-written assessment of the linked reports, not a verified fact. Check the sources. How Mosaic works

Topics banking · technical issue · infrastructure · financial services · outage · technical outage · financial infrastructure · downdetector · jpmorgan · bank of america

Technical details
Impact score
4.9 / 10 · a priority score, not confidence
Model confidence
Medium: evidence reported (1 of 5 key facts linked to evidence; the model marked a key fact as unclear); 2 distinct outlets
Coverage focus
100% in primary evidence group
Coherence
0.90
Review state
published
Refreshed
Updated Nov 16, synthesized Nov 16. Not evidence time.
Cluster type
story
Member signals
2
Situation id
dd85cb30-5dcc-4450-b76f-7d0258e12f3c
Last evidenceNov 16, 20:26 UTC
Last successful evaluationSuccessful evaluation timestamp unavailable (legacy)
Last attempt·

Public comments

…

Anyone who opens this situation can read these comments, with the author's display name. They are not private notes.

Sign in to post a public comment, contribute a source, or challenge the assessment.