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

Pakistan–Afghanistan Border Conflict and Diplomatic Dispute

stories
151
events
39
entities
204
connections
151
Retained edition
Evidence so far on 2026-11-07 UTC · updated 2026-11-07 11:22 UTC · analysis as of 2026-11-07 00:27 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; Pakistan attributed the action to drone attacks in “Pakistan says it struck sites in Afghanistan linked to drone attacks.” [citations] On 25 September, Pakistani security forces exchanged fire with Afghan Taliban fighters, and Zabihullah Mujahid accused Pakistan of aggression in Kandahar. [citations] 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” presented conflicting accounts of those killed. [citations] Pakistan urged Afghanistan’s Taliban government to curb cross-border militant attacks on 12 October, and the Afghan government kept Durand Line crossings closed to Pakistan on 14 October until its demands were accepted. [citations] On 27 October, an Event described Afghan Taliban regime shelling at Angoor Adda that killed a civilian. Reports dated 28 October described Taliban attacks on civilians in South Waziristan and Pakistani troops’ cross-border fire killing two civilians in Nangarhar; Afghanistan also said it struck Pakistani positions in retaliation for drone attacks. Pakistan Army action against Afghan Taliban posts after cross-border firing was reported on 30 October. [citations] Pakistan welcomed a US offer to facilitate dialogue on 1 November; Events also describe missiles fired at homes in Paktika that day and Pakistan Army strikes on Afghan Taliban positions along the border…

Footnotes[46][18][36][50][17][33][10][9][41][6][40][5]
Assessment

The events and attributed statements establish a sustained security dispute involving Pakistani strikes, border fighting, Afghan claims of retaliatory strikes, reciprocal accusations and restrictions on crossings; they do not establish a single cause for the separate incidents. [citations] Accounts of the 1 October Helmand strikes differ: Pakistan’s account described fighters killed, while a Kabul- and UN-attributed account described civilian deaths; the Event lists nine fatalities and 11 injuries. [citations] Separate reports describe civilian deaths or injuries in Afghanistan and Pakistan, including shelling at Angoor Adda, attacks on homes in Pakistan, the reported Pakistani fire in Nangarhar, and the November 2 report of cross-border fire in northwest Pakistan. [citations] The November 2 Paktika airstrike was reported separately from the November 1 missiles-at-homes Event. [citations] Pakistan’s diplomatic demands, the Afghan government’s crossing closure, Sergey Lavrov’s statement about Russia’s role, Pakistan’s welcome for a US dialogue offer, and later calls for dialogue establish diplomatic activity, not a resolution. [citations]

Footnotes[33][10][9][42][34][39][41][40][55][54]

Explanation originally captured 2026-11-07 · Evidence through 2026-11-07 UTC · Source edition sed_51074448ef2deaa99d5f8b207ab11b0f

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 50-day Situation represented by 39 coded Events carried across 151 member Stories.

  • Coded activity

    The coded activity is led by ARMED CLASH (9) 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. 39 coded Events · 15 CAMEO+ · 24 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

39 coded events — 15 CAMEO+ (15 political) · 24 conflict

  • Significance · 390.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 · 39-6.5
    min -10max 3.4
  • Fatalities · 249
    min 0max 31
  • Confidence · 390.68
    min 0.32max 0.91

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

Significance

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

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

across all 39 events

Magnitude

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

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

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

Systemic

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

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

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

Propagation

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

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

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

Market

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

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

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

Goldstein

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

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

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

Fatalities

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

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

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

Confidence

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

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

across all 39 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 day41 reporting days · click a day to open or close it

2026-11-06from the recordslatest

Pakistan forces destroy Afghan Taliban posts, foil infiltration in Kurram

1 Story and 0 coded Events (+1 / -1 against the day before). Widest coverage: Pakistan forces destroy Afghan Taliban posts, foil infiltration in Kurram (1 articles).

Pakistan forces destroy Afghan Taliban posts, foil infiltration in Kurram
1+1
Stories · vs day before
0-1
Events · vs day before
1
articles
The lay of the land

Situation timeline

Threads
All 41 daysarticlesstoriesevents
09-1809-2610-0410-1610-2711-06
Loading Situation timeline…

What kind of event · 14 coded types

over 39 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

    Pakistani strikes and border clashes, Afghan accounts of Pakistani actions, and later Pakistani Army operations against Afghan Taliban positions form the central security thread. Civilian-harm accounts and descriptions of targets vary across the linked reports.

    Pakistani strikes and border clashes, Afghan accounts of Pakistani actions, and later Pakistani Army operations against Afghan Taliban positions form the central security thread. Civilian-harm accounts and descriptions of targets vary across the linked reports.

    Footnotes[43][46][36][45][44][47][33]
  2. development
    AnalystOfficial claims, protests and diplomatic activity

    Pakistani and Afghan officials made accusations, demands, protest statements and decisions affecting crossings; Russian and US diplomatic activity also features. These actions do not establish a settlement.

    Pakistani and Afghan officials made accusations, demands, protest statements and decisions affecting crossings; Russian and US diplomatic activity also features. These actions do not establish a settlement.

    Footnotes[50][51][41][40][55][54][17][5][2]
  3. development
    AnalystPakistani domestic security incidents

    Separate Events describe attacks on Pakistani police and Pakistani security operations in Kohat and Hangu. Pakistan attributed the Kohat attackers to militants with Afghan roots, but the incidents do not establish a cause for later cross-border action.

    Separate Events describe attacks on Pakistani police and Pakistani security operations in Kohat and Hangu. Pakistan attributed the Kohat attackers to militants with Afghan roots, but the incidents do not establish a cause for later cross-border action.

    Footnotes[29][26][25][28][31][32][23]
  4. development
    AnalystCivilian and refugee impact

    Events and Stories describe civilian deaths and injuries in Afghanistan and Pakistan. The casualty accounts do not reconcile all reported tolls.

    Events and Stories describe civilian deaths and injuries in Afghanistan and Pakistan. The casualty accounts do not reconcile all reported tolls.

    Footnotes[33][42][34][39][35][18][9][1]

Key actors

  1. T
    AnalystTaliban

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

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

    Footnotes[56][46][44][39]
  2. ZM
    AnalystZabihullah Mujahid

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

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

    Footnotes[57][50][17]
  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[58][31][49][47]
  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[59][48][52]
  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[60][43]

Key Events

  1. contextAnalystUnidentified suicide bomber kills 17 at Pakistani police complex

    A suicide bombing at a Pakistani police complex is dated to 18 September; “Suicide attack on police headquarters kills at least 20 in northwest Pakistan” gives a different toll from the Event.

    A suicide bombing at a Pakistani police complex is dated to 18 September; “Suicide attack on police headquarters kills at least 20 in northwest Pakistan” gives a different toll from the Event.

    Footnotes[29][24]
  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 target.

    On 24 September, Pakistan’s armed forces struck 10 sites in Afghanistan, with the Afghan Taliban named as target.

    Footnotes[46][18]
  3. contextAnalystPakistani security forces exchange fire with Afghan Taliban fighters

    On 25 September, Pakistani security forces exchanged fire with Afghan Taliban fighters; the Event lists three fatalities.

    On 25 September, Pakistani security forces exchanged fire with Afghan Taliban fighters; the Event lists three fatalities.

    Footnotes[36][15]
  4. 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 the toll and those killed.

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

    Footnotes[33][10][9]
  5. contextAnalystPakistan urges Taliban government to curb cross-border militant attacks

    On 12 October, Pakistan urged Afghanistan’s Taliban government to curb cross-border militant attacks.

    On 12 October, Pakistan urged Afghanistan’s Taliban government to curb cross-border militant attacks.

    Footnotes[41][6]

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[61][46]
  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[56][46]
  3. Pakistan Air Force acted in the 23 September strike on drone facilities in Afghanistan · 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[60][43]
  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[57][50]
  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 the Taliban as target.

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

    Footnotes[58][56][44]

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 together151 Stories · 39 Events · 151 membership connections · 938 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.