Significance
43 measured / 43 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 43 events
Connected Situation / Through 2026-10-26
Taiwan Typhoon Impacts and Recovery
- stories
- 18
- events
- 43
- entities
- 22
- connections
- 18
Evidence so far on 2026-10-26 UTC · updated 2026-10-26 03:23 UTC · analysis as of 2026-10-25 04:30 UTCSign in for the live Situation ↗
Narrative
As-of analysis
Situation at a glance
“Typhoon ravages Taiwan, leaving 1 dead and 527 injured” reports that toll and identifies Typhoon Champi as the storm affecting Taiwan. [Citation: Story.] On October 23, Taiwan Railways suspended several lines through October 24, while “Hsinchu County closes high-risk roads as storm strengthens” describes local road restrictions. [Citations: Event and Story.] On October 24, “Typhoon damages 304 cell sites in Taiwan; Taiwan Mobile rushes repairs” describes damage to communications infrastructure and Taiwan Mobile’s repair effort. [Citation: Story.] That day, Taiwan highway authorities reopened cross-island routes, and Taipower restored power to more than 10,000 Hsinchu homes. [Citations: Events.] “Taiwan CDC warns of four infectious disease risks after typhoon” adds the Taiwan CDC’s public-health warning. [Citation: Story.]
Footnotes[1][7][3][14][5][15][16][2]Assessment
The named accounts describe substantial reported harm alongside disruption to rail, roads, power and cell sites, with specific transport and electricity restoration actions on October 24. The seed headline’s casualty figures are reported figures; the cited Event entries do not provide corresponding fatality or injury totals. Storm names differ across the material: the seed names Champi, while a Keelung power-outage Event names Chanthu, so these labels cannot be reconciled from these facts alone. The China railway-schedule Event is linked to the Taiwan typhoon roundup, but its title and location describe the Yangtze River Delta; that connection does not establish that the Taiwan storm caused the schedule change.
Footnotes[1][7][8][16][15][18][14][17][2][7][16][15]Explanation originally captured 2026-10-25 · Evidence through 2026-10-26 UTC · Source edition sed_4ec4b556fee4c8b2602512ee4b3e2139
What informs this explanation
- Complete retained Story and Event membership
- Daily reporting and coded-occurrence time steps
- Event taxonomies, metrics, units, and denominators
- Canonical Entities and recorded actor/target bindings
- Typed reporting, membership, and incident edges
- Changes against the preceding retained edition
- Permitted macro, public-record, and asset facts only when they were retained with an explicit source and observation date
Quantitative
Evidence in numbers
- Scope
A 4-day Situation represented by 43 coded Events carried across 18 member Stories.
- Coded activity
The coded activity is led by EN02 · Meteorological Hazard (28) and IN02 · Transport Disruption (8).
- Prominent subjects
🇹🇼Taiwan and 🇨🇳China are prominent in the retained actor and relationship evidence.
- Entity coverage
22 canonical Entities are linked to this edition.
Metric coverage. 43 coded Events · 43 CAMEO+ · 0 conflict. The four dimensions describe the CAMEO+ subset; conflict Events do not carry these scores.
Magnitude2.2
min 1max 4
Systemic importance0.15
min 0.03max 0.43
Propagation potential0.28
min 0max 0.43
Market sensitivity0.09
min 0.05max 0.6
Dot = mean · shaded span = observed range · position uses each metric’s defined scale.
All 6 scores, distributions & definitions
How the coder scored the full retained Event set
43 coded events — 43 CAMEO+
- Significance · 430.25min 0.15max 0.39
- Magnitude · 432.2min 1max 4
- Systemic · 430.15min 0.03max 0.43
- Propagation · 430.28min 0max 0.43
- Market · 430.09min 0.05max 0.6
- Confidence · 430.42min 0.34max 0.55
No conflict-family event here, so nothing carries a fatality count — a missing column, not a toll of zero. 43 sit outside POLITICAL, where Goldstein and quad class are undefined.
Magnitude
43 measured / 43 eligible · 0 missing · 0 not applicable
score (0 to 10) · Event-level distribution, not a Situation risk score.
across all 43 events — every one of them CAMEO+
Systemic
43 measured / 43 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 43 events — every one of them CAMEO+
Propagation
43 measured / 43 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 43 events — every one of them CAMEO+
Market
43 measured / 43 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 43 events — every one of them CAMEO+
Confidence
43 measured / 43 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 43 events
This retained edition, independent of graph and page limits. Different dimensions, not a blended risk score; reported tolls may overlap.
Day by day4 reporting days · click a day to open or close it
2026-10-26from the recordslatest
Typhoon 薔琵 winds devastate crops in Pingtung County
2 Stories and 2 coded Events (-2 / -4 against the day before). Widest coverage: Typhoon passes Taiwan; Shei-Pa National Park partially reopens (1 articles).
- 2-2
- Stories · vs day before
- 2-4
- Events · vs day before
- 2
- articles
The lay of the land
Situation timeline
Threads
All 4 daysarticlesstoriesevents
10-2310-2410-2510-26
Loading Situation timeline…
What kind of event · 6 coded types
over 43 coded events on this edition
- Environment28
- EN02 · Meteorological Hazard28
- Infrastructure14
- IN02 · Transport Disruption8
- IN01 · Energy Infrastructure Event4
- IN04 · Communications Infrastructure1
- IN06 · Water Infrastructure Event1
- Crime1
- CR08 · Arrest Charge Conviction or Sentencing1
Countries · where it happened
Countries · who is acting
Salient structure
What holds this Situation together
Selected from the complete retained edition
Key threads
- core
AnalystReported impacts across Taiwan
The seed roundup reports the casualty toll, while local Stories describe blocked roads, damage to cell sites and power outages. The differing storm names in coded Event titles remain unresolved.
- development
AnalystTransport disruption and restoration
Taiwan Railways suspended several lines, while separate October 24 Events describe highway reopenings, a lifted Suhua corridor closure, and resumed Matsu ferry services.
- development
AnalystPost-typhoon health warning
Taiwan CDC warned of four infectious-disease risks after the typhoon. The Central Weather Administration is mentioned in this Story, but no supplied Event binds it as a participant.
Key actors
Key Events
contextAnalystTaiwan Railways suspends several lines through October 24
On October 23, Taiwan Railways suspended several lines through October 24.
On October 23, Taiwan Railways suspended several lines through October 24.
Footnotes[7]
contextAnalystHsinchu County closes high-risk roads as storm strengthens
On October 23, Hsinchu County closed high-risk roads as the storm strengthened.
On October 23, Hsinchu County closed high-risk roads as the storm strengthened.
Footnotes[14]contextAnalystTaiwan Mobile rushes repairs after typhoon damages 304 cell sites
On October 24, Taiwan Mobile rushed repairs after typhoon damage to 304 cell sites.
On October 24, Taiwan Mobile rushed repairs after typhoon damage to 304 cell sites.
Footnotes[9]contextAnalystTaiwan highway authorities reopen cross-island routes after typhoon weakens
On October 24, Taiwan highway authorities reopened cross-island routes after the typhoon weakened.
On October 24, Taiwan highway authorities reopened cross-island routes after the typhoon weakened.
Footnotes[15]contextAnalystTaipower restores power to more than 10,000 Hsinchu homes
On October 24, Taipower restored power to more than 10,000 Hsinchu homes.
On October 24, Taipower restored power to more than 10,000 Hsinchu homes.
Footnotes[16]
Notable connections
Evidenced relationships involving significant participants beyond the central cast.
The Taiwan Railways suspension Event is linked to the typhoon impact roundup. · reporting linkAnalystTaiwan Railways suspends several lines through October 24 → Typhoon ravages Taiwan, leaving 1 dead and 527 injured
The Event lists the roundup among its supporting Stories.
The Taiwan Mobile repair Event is linked to the cell-site damage Story. · reporting linkAnalystTaiwan Mobile rushes repairs after typhoon damages 304 cell sites → Typhoon damages 304 cell sites in Taiwan; Taiwan Mobile rushes repairs
The Event lists the cell-site damage Story as support.
Taiwan Mobile is mentioned in the cell-site damage Story. · reporting linkAnalystTaiwan Mobile → Typhoon damages 304 cell sites in Taiwan; Taiwan Mobile rushes repairs
The Entity is associated with that Story as a mention; this does not establish a separate Entity-to-Event participation binding.
How a Situation is put together18 Stories · 43 Events · 18 membership connections · 96 graph edges
A retained time step
This edition freezes the complete served membership and analysis available through its UTC cutoff. Later repairs or identity changes do not rewrite what this edition showed.
Stories, Events, and cast
Stories are reporting clusters. Events are coded occurrences within that reporting. The cast contains 22 canonical people and organizations linked to the retained evidence.
Typed connections
Story-to-Event edges identify supporting reporting. Entity-to-Event edges identify recorded actor or target participation. Mentions and analytical roles stay visibly distinct from recorded participation.
Core, precursor, and continuation labels organize the reading. They do not by themselves establish causation. Collapsed graph groups and paginated evidence change presentation only; counts use the complete retained edition.