Skip to content

Which companies just had a verified incident, who lends to them and who owns them. Every claim carries its evidence level and its source. How we decide what is confirmed

DFX Cyber Intelligence ยท United States

US Critical Infrastructure Cyber Intelligence

Early warning, active monitoring, verified incidents and infrastructure dependencies. Provider status posts are shown as what the provider published; only analyst-reviewed findings are called cyber incidents.

Reduced coverageLast successful collection Nov 6 22:20 UTCLast attempt Nov 6 22:20 UTCLatest provider update Nov 6 17:59 UTC19 of 22 sources collected in the last 30 minutes; 3 not checked (robots.txt could not be read)Coverage and health

Coverage is reduced: DFX is not reading 105 of 124 status feeds, because their robots.txt does not allow it or could not be read, while we move to the incident feeds providers publish.

Filtered to all sectors, NM. Clear filters

Confirmed cyber incidents
0
Analyst-confirmed, activity in the last 24 hours
Active confirmed disruptions
7
Confirmed and still not recovered
Unexplained disruptions
0
Cause not established; not called cyber
Remediation and recovery actions
0
Documented containment, resets, restoration
Providers monitored
19
Status feed collected in the last 30 minutes
New developments, 24h
117
Provider status updates first seen in 24h

Where the findings are

Shaded by the number of public findings in each state. A filled marker means the finding documents a site in that state; a ring means it is placed by headquarters only, which says nothing about the area around it. Select a state to filter the page.

Alaska: 0 public findingsAlabama: 0 public findingsArkansas: 0 public findingsArizona: 0 public findingsCalifornia: 0 public findingsColorado: 0 public findingsConnecticut: 0 public findingsDistrict of Columbia: 0 public findingsDelaware: 0 public findingsFlorida: 0 public findingsGeorgia: 0 public findingsHawaii: 0 public findingsIowa: 0 public findingsIdaho: 0 public findingsIllinois: 0 public findingsIndiana: 0 public findingsKansas: 0 public findingsKentucky: 0 public findingsLouisiana: 0 public findingsMassachusetts: 0 public findingsMaryland: 0 public findingsMaine: 0 public findingsMichigan: 0 public findingsMinnesota: 0 public findingsMissouri: 0 public findingsMississippi: 0 public findingsMontana: 0 public findingsNorth Carolina: 0 public findingsNorth Dakota: 0 public findingsNebraska: 0 public findingsNew Hampshire: 0 public findingsNew Jersey: 0 public findingsNew Mexico: 0 public findingsNevada: 0 public findingsNew York: 0 public findingsOhio: 0 public findingsOklahoma: 0 public findingsOregon: 0 public findingsPennsylvania: 0 public findingsRhode Island: 0 public findingsSouth Carolina: 0 public findingsSouth Dakota: 0 public findingsTennessee: 0 public findingsTexas: 0 public findingsUtah: 0 public findingsVirginia: 0 public findingsVermont: 0 public findingsWashington: 0 public findingsWisconsin: 0 public findingsWest Virginia: 0 public findingsWyoming: 0 public findings
Confirmed, documented incident site in state Confirmed, placed by headquarters only Unexplained or other public findingNational platforms with no single location are listed below the map, not placed on it.
National or unlocated
  • None in this window

Confirmed cyber incidents

Incidents confirmed by the organisation, a regulator or compelling corroborated evidence, reviewed by an analyst. Live provider posts never enter this list on their own.

No confirmed cyber incidents with activity in the last 24 hours within monitored coverage.

Emerging operational signals

What providers published on their own status pages in this window, with the kind of wording they used. A disruption, a restriction or even security language is a provider statement, not a DFX finding that an attack occurred.

No provider status incidents with impact in the last 24 hours.

50 provider status incidents are open right now across monitored providers.

Unexplained disruptions

Verifiable operational disruptions with no established cause. Listed factually, without any claim of compromise.

None published in this window.

National timeline

Research findings and significant provider posts in date order. Event, first public observation and acknowledgement dates are kept separate on each record's page.

No dated developments in this window.

Critical infrastructure sectors

Dependencies and downstream exposure

Documented relationships between providers and the organisations that rely on them, from vendor case studies, customer releases, regulator orders and breach notices. A relationship is not an impact: each dependent says whether impact is confirmed.

Continental Utility Solutions, Inc. (CIS/billing vendor)
recovered
  • Kempner WSC TXNo confirmed impact
  • Culleoka WSC TXNo confirmed impact
  • McCoy WSC TXNo confirmed impact
  • Penrose WD CONo confirmed impact
  • Pleasant Valley MWC CANo confirmed impact
  • Village of Hopedale ILNo confirmed impact
Abrigo (Sageworks)
Provider outage; Abrigo's status page states no cause
  • Broadway Bank (San Antonio)No confirmed impact
  • Webster BankNo confirmed impact
  • Capital Credit Union (WI)No confirmed impact
  • Signature Bank of Georgia (ABA release May 2025, reported)No confirmed impact
BankMobile Disbursements (BM Technologies)
ongoing, electronic disbursements paused, Los Rios switched to Nelnet
  • Los Rios CCDNo confirmed impact
  • Santa Monica CollegeNo confirmed impact
  • about 60 California community college districtsNo confirmed impact
unnamed (SmartHub app channel affected; vendor hypothesized)
unknown
  • Joe Wheeler EMCNo confirmed impact
  • Huntsville UtilitiesNo confirmed impact
  • Decatur UtilitiesNo confirmed impact
Southern Company shared portal
unknown
  • Georgia PowerNo confirmed impact
  • Alabama PowerNo confirmed impact
  • Mississippi PowerNo confirmed impact
Pepco
recovered
  • U.S. State Department Foggy Bottom facilitiesNo confirmed impact
  • George Washington UniversityNo confirmed impact
  • DC traffic signalsNo confirmed impact
GitBook
verified (customer-wide revocation); hypothesized (Trade.xyz link)
  • All GitBook customers (API tokens invalidated, secrets rotation...No confirmed impact
  • one unnamed targeted customerNo confirmed impact
  • possibly Trade.xyzImpact reported publicly
Mercadien, P.C.
data incident, no operational impact
  • Bangkok Bank PCL NY BranchNo confirmed impact
  • Fairwinds Credit Union (Sep 2026 notice)No confirmed impact
Global financial service disruptionsInfrastructure WatchMonitoring coverage and healthHow this works and what it cannot seeResearch baseline: Operation Early Warning, 29 Oct to 5 Nov 2026 (41 public findings).