GDELT CloudGDELT Cloud
Connected Situation / Through 2026-11-05

Pakistan–Afghanistan Border Conflict and Diplomatic Dispute

stories
150
events
38
entities
204
connections
150
Retained edition
Evidence so far on 2026-11-05 UTC · updated 2026-11-05 15:22 UTC · analysis as of 2026-11-05 01:26 UTCSign in for the live Situation ↗
Narrative

As-of analysis

Carried forward
Situation at a glance

Pakistan’s armed forces struck 10 sites in Afghanistan on 24 September, with the Afghan Taliban named as the target; the account appeared under “Pakistan launches airstrikes on Afghan targets as Taliban threaten retaliation.” On 25 September, Pakistani security forces exchanged fire with Afghan Taliban fighters, and Zabihullah Mujahid accused Pakistan of aggression in Kandahar. On 1 October, Pakistani military airstrikes hit two houses in Helmand; “Pakistan says airstrikes on Afghanistan hideouts killed 22 fighters” and “Pakistani airstrikes kill 10 civilians in Afghanistan, Kabul and UN say” gave different accounts of the dead and their status. On 12 October, Pakistan urged Afghanistan’s Taliban government to curb cross-border militant attacks; on 14 October, Afghanistan’s government kept Durand Line crossings closed until Pakistan accepted its demands. In late October, events included Afghan Taliban regime shelling at Angoor Adda that killed a civilian, attacks on civilians reported on both sides of the border, and a Pakistan Army operation against Afghan Taliban posts after cross-border firing. On 1 November, Pakistan welcomed a US offer to facilitate dialogue, while a separate Event describes Pakistan Armed Forces firing missiles at homes in Paktika; on 2 November, the Pakistan Army struck Afghan Taliban positions along the border.

Footnotes[45][16][35][49][18][32][10][9][40][5][39][4]
Assessment

The Events establish distinct strikes, clashes, official accusations and diplomatic measures; they do not establish one continuous operation or a single cause for the cross-border violence. The Helmand accounts conflict: one Pakistani account says 22 fighters were killed, while a report attributing its account to Kabul and the UN says 10 civilians died; the Event lists nine fatalities and 11 injuries. Pakistan’s claim that the Kohat attackers had Afghan roots remains an attributed claim, and the Events and reports do not establish that the Kohat attack caused later strikes. Reports of civilians harmed near the border and returning refugees at risk broaden the impact beyond security forces, while the US dialogue offer and Sergei Lavrov’s statement about normalization establish diplomatic activity, not a resolution.

Footnotes[32][10][9][24][26][28][2][53][1][54][7]

Explanation originally captured 2026-11-05 · Evidence through 2026-11-05 UTC · Source edition sed_6a1b7358b03dd1f58a681098c9adaba3

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

This retained edition
  • Scope

    A 46-day Situation represented by 38 coded Events carried across 150 member Stories.

  • Coded activity

    The coded activity is led by ARMED CLASH (8) and AIR/DRONE STRIKE (5).

  • Prominent subjects

    Taliban, Zabihullah Mujahid, and Pakistan Army are prominent in the retained actor and relationship evidence.

  • Entity coverage

    204 canonical Entities are linked to this edition.

Metric coverage. 38 coded Events · 15 CAMEO+ · 23 conflict. The four dimensions describe the CAMEO+ subset; conflict Events do not carry these scores.

Magnitude3.8
min 2max 7
15 measured
Systemic importance0.12
min 0.1max 0.2
15 measured
Propagation potential0.32
min 0.26max 0.44
15 measured
Market sensitivity0.05
min 0.05max 0.05
15 measured

Dot = mean · shaded span = observed range · position uses each metric’s defined scale.

All 8 scores, distributions & definitions

How the coder scored the full retained Event set

38 coded events — 15 CAMEO+ (15 political) · 23 conflict

  • Significance · 380.41
    min 0.16max 0.73
  • Magnitude · 153.8
    min 2max 7
  • Systemic · 150.12
    min 0.1max 0.2
  • Propagation · 150.32
    min 0.26max 0.44
  • Market · 150.05
    min 0.05max 0.05
  • Goldstein · 38-6.5
    min -10max 3.4
  • Fatalities · 239
    min 0max 31
  • Confidence · 380.68
    min 0.32max 0.91

Quad class over those 38 events · Material Conflict 24 · Verbal Conflict 9 · Verbal Cooperation 5. The four CAMEO+ scores are over the 15 CAMEO+ events only; the 23 conflict events have no such column.

Significance

38 measured / 38 eligible · 0 missing · 0 not applicable

score (0 to 1) · Event-level distribution, not a Situation risk score.

across all 38 events

Magnitude

15 measured / 15 eligible · 0 missing · 23 not applicable

score (0 to 10) · Event-level distribution, not a Situation risk score.

across the 15 of 38 events coded in the CAMEO+ family; the conflict family has no such column

Systemic

15 measured / 15 eligible · 0 missing · 23 not applicable

score (0 to 1) · Event-level distribution, not a Situation risk score.

across the 15 of 38 events coded in the CAMEO+ family; the conflict family has no such column

Propagation

15 measured / 15 eligible · 0 missing · 23 not applicable

score (0 to 1) · Event-level distribution, not a Situation risk score.

across the 15 of 38 events coded in the CAMEO+ family; the conflict family has no such column

Market

15 measured / 15 eligible · 0 missing · 23 not applicable

score (0 to 1) · Event-level distribution, not a Situation risk score.

across the 15 of 38 events coded in the CAMEO+ family; the conflict family has no such column

Goldstein

38 measured / 38 eligible · 0 missing · 0 not applicable

score (-10 to 10) · Event-level distribution, not a Situation risk score.

across the 38 of 38 events Goldstein is defined on — CAMEO+ POLITICAL and the conflict family; the other nine CAMEO+ domains have no Goldstein semantics

Fatalities

23 measured / 23 eligible · 0 missing · 15 not applicable

reported people · Reports may overlap; these are Event-level reports, not an additive unique human toll.

across the 23 of 38 events that report a toll — the conflict family only, and never 0 on a CAMEO+ event

Confidence

38 measured / 38 eligible · 0 missing · 0 not applicable

score (0 to 1) · Event-level distribution, not a Situation risk score.

across all 38 events

Metric definitions and limitations

This retained edition, independent of graph and page limits. Different dimensions, not a blended risk score; reported tolls may overlap.

Day by day39 reporting days · click a day to open or close it

2026-11-02from the recordslatest

Pakistan Army strikes Afghan Taliban positions along the border

5 Stories and 1 coded Event (+2 / -1 against the day before). Widest coverage: Pakistani airstrike kills one and injures students in Afghanistan's Paktika (5 articles). Recorded acting: Pakistan Army.

Pakistan Army strikes Afghan Taliban positions along the borderPakistani airstrike kills one and injures students in Afghanistan's PaktikaPAPakistan Army
5+2
Stories · vs day before
1-1
Events · vs day before
9
articles
The lay of the land

Situation timeline

Threads
All 39 daysarticlesstoriesevents
09-1809-2610-0310-1410-2511-02
Loading Situation timeline…

What kind of event · 14 coded types

over 38 coded events on this edition

  • Political15
    • 111 · Criticize or Denounce3
    • 01 · Make Public Statement2
    • 1042 · Policy Change2
    • 1123 · Aggression2
    • 114 · Complain Officially2
    • 022 · Appeal for Diplomatic Cooperation1
    • 0242 · Policy Change1

Countries · where it happened

Countries · who is acting

Salient structure

What holds this Situation together

Selected from the complete retained edition

Key threads

  1. core
    AnalystCross-border strikes and fighting

    Pakistan’s strikes and border clashes, Afghan accounts of Pakistani actions, and reported attacks on civilians form the central security thread; the accounts of casualties and responsibility are not fully consistent.

    Pakistan’s strikes and border clashes, Afghan accounts of Pakistani actions, and reported attacks on civilians form the central security thread; the accounts of casualties and responsibility are not fully consistent.

    Footnotes[45][16][35][15][44][17][38][33]
  2. development
    AnalystOfficial claims, protests and diplomatic activity

    Pakistani and Afghan officials made accusations, demands and protest statements; Russia and the United States also appear in diplomatic accounts.

    Pakistani and Afghan officials made accusations, demands and protest statements; Russia and the United States also appear in diplomatic accounts.

    Footnotes[49][50][40][39][54][53]
  3. development
    AnalystPakistani domestic security incidents

    Separate Events describe attacks on police and Pakistani security operations in Kohat and Hangu; the supplied accounts do not establish that these incidents caused the cross-border actions.

    Separate Events describe attacks on police and Pakistani security operations in Kohat and Hangu; the supplied accounts do not establish that these incidents caused the cross-border actions.

    Footnotes[29][26][37][31][24]
  4. development
    AnalystCivilian and refugee impact

    Events and reports describe civilian deaths and injuries in Afghanistan and Pakistan, as well as danger to returning refugees near a crossing.

    Events and reports describe civilian deaths and injuries in Afghanistan and Pakistan, as well as danger to returning refugees near a crossing.

    Footnotes[32][9][41][33][34][2]

Key actors

  1. T
    AnalystTaliban

    The Taliban is named as the target of Pakistan’s 24 September strike and the Pakistan Army’s 30 October operation, and as the actor in an Event describing an attack on civilians in Pakistan on 28 October.

    The Taliban is named as the target of Pakistan’s 24 September strike and the Pakistan Army’s 30 October operation, and as the actor in an Event describing an attack on civilians in Pakistan on 28 October.

    Footnotes[55][45][43][38]
  2. ZM
    AnalystZabihullah Mujahid

    Zabihullah Mujahid made the 25 September accusation that Pakistan was acting aggressively in Kandahar.

    Zabihullah Mujahid made the 25 September accusation that Pakistan was acting aggressively in Kandahar.

    Footnotes[56][49][18]
  3. PA
    AnalystPakistan Army

    The Pakistan Army is identified as actor in Events describing the Hangu firefight, its accusation against Mullah Shireen, and strikes on Afghan Taliban positions on 2 November.

    The Pakistan Army is identified as actor in Events describing the Hangu firefight, its accusation against Mullah Shireen, and strikes on Afghan Taliban positions on 2 November.

    Footnotes[57][31][48][46]
  4. AT
    AnalystAttaullah Tarar

    Attaullah Tarar criticized the Khyber Pakhtunkhwa government and urged the Afghan Taliban government to change policy.

    Attaullah Tarar criticized the Khyber Pakhtunkhwa government and urged the Afghan Taliban government to change policy.

    Footnotes[58][47][51]
  5. PA
    AnalystPakistan Air Force

    The Pakistan Air Force is identified as actor in the 23 September strike on drone facilities in Afghanistan.

    The Pakistan Air Force is identified as actor in the 23 September strike on drone facilities in Afghanistan.

    Footnotes[59][42][19]

Key Events

  1. contextAnalystUnidentified suicide bomber kills 17 at Pakistani police complex

    An Event dates a suicide bombing at a Pakistani police complex to 18 September and lists 17 fatalities; a linked Story reports at least 20.

    An Event dates a suicide bombing at a Pakistani police complex to 18 September and lists 17 fatalities; a linked Story reports at least 20.

    Footnotes[29][25]
  2. contextAnalystPakistan armed forces strike 10 sites in Afghanistan

    On 24 September, Pakistan’s armed forces struck 10 sites in Afghanistan, with the Afghan Taliban named as the target; the linked Story reports threatened retaliation.

    On 24 September, Pakistan’s armed forces struck 10 sites in Afghanistan, with the Afghan Taliban named as the target; the linked Story reports threatened retaliation.

    Footnotes[45][16]
  3. contextAnalystPakistani security forces exchange fire with Afghan Taliban fighters

    On 25 September, Pakistani security forces exchanged fire with Afghan Taliban fighters.

    On 25 September, Pakistani security forces exchanged fire with Afghan Taliban fighters.

    Footnotes[35][15]
  4. contextAnalystZabihullah Mujahid accuses Pakistan of aggression in Kandahar

    Zabihullah Mujahid accused Pakistan of aggression in Kandahar on 25 September.

    Zabihullah Mujahid accused Pakistan of aggression in Kandahar on 25 September.

    Footnotes[49][18]
  5. contextAnalystPakistani military airstrikes hit two houses in Helmand

    On 1 October, Pakistani military airstrikes hit two houses in Helmand; the Event lists nine fatalities and 11 injuries, while linked accounts differ on toll and target.

    On 1 October, Pakistani military airstrikes hit two houses in Helmand; the Event lists nine fatalities and 11 injuries, while linked accounts differ on toll and target.

    Footnotes[32][10][9]

Notable connections

Evidenced relationships involving significant participants beyond the central cast.

  1. Pakistan Armed Forces acted in the 24 September strike on 10 sites · recorded participationAnalystPakistan Armed Forces → Pakistan armed forces strike 10 sites in Afghanistan

    The Event identifies Pakistan Armed Forces as actor.

    The Event identifies Pakistan Armed Forces as actor.

    Footnotes[60][45]
  2. The Taliban was named as the target of the 24 September strike · recorded participationAnalystTaliban → Pakistan armed forces strike 10 sites in Afghanistan

    The Event identifies the Taliban as target.

    The Event identifies the Taliban as target.

    Footnotes[55][45]
  3. Pakistan Air Force struck drone facilities in Afghanistan on 23 September · recorded participationAnalystPakistan Air Force → Pakistan Air Force strikes drone facilities in Afghanistan

    The Event identifies Pakistan Air Force as actor.

    The Event identifies Pakistan Air Force as actor.

    Footnotes[59][42]
  4. Zabihullah Mujahid made the 25 September accusation against Pakistan · recorded participationAnalystZabihullah Mujahid → Zabihullah Mujahid accuses Pakistan of aggression in Kandahar

    The Event identifies Mujahid as speaker and actor.

    The Event identifies Mujahid as speaker and actor.

    Footnotes[56][49]
  5. Pakistan Army acted against Afghan Taliban posts on 30 October · recorded participationAnalystPakistan Army → Pakistan Army destroys Afghan Taliban posts after cross-border firing

    The Event identifies Pakistan Army as actor and Afghan Taliban as target.

    The Event identifies Pakistan Army as actor and Afghan Taliban as target.

    Footnotes[57][55][43]

Current related Situations

Explore all →

Finding connected developments…

Compared with currently maintained Situation membership; this list is not part of the retained edition above.

How a Situation is put together150 Stories · 38 Events · 150 membership connections · 935 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 204 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.