Rakhine State connectivity crisis, November 2024–2025

DRAFT — needs an editor rewrite. Checked IODA's historical region-level signal for Rakhine (region code 2754) directly for both bgp and ping-slash24 datasources around Nov 16, 2024: both are flat/unchanged (BGP visibility constant at its baseline value throughout) — no routing-layer disruption was detectable, consistent with STOP's own account that the cause may have been physical damage to a tower rather than a deliberate route withdrawal. This null result is reported explicitly rather than omitted silently, per spec principle. STOP records name TWO different attributions across this cluster — the Nov 2024 record says cause is unclear (infrastructure damage, fuel shortage, and deliberate junta action all reported); the Jan 2025 record says the Arakan Army itself was imposing shutdowns in AA-held areas. Attribution question resolved (maintainer research, 2026-07): treated as ONE continuous, evolving disruption rather than two distinct causes or a split into separate events — attribution became clearer over time as AA consolidated territorial control, rather than the underlying disruption itself changing. Engage Media's Nov 2024–Jan 2025 quarterly frames this same period as a single ongoing connectivity crisis; conflict-tracking sources (ACAPS, CSIS) describe continuous AA territorial consolidation across the same townships through this window with no discrete break between the two attributions. Both detection_sequence entries are kept as-is (this is a presentation choice, not new evidence), now with the relationship between them stated explicitly rather than left as an open question. Later STOP records in this cluster (Jun, Aug ×2, Sep 2025 — all bare "Rakhine State" or Kyaukpyu/Ramree township) are summarized in scope/townships but not individually itemized in detection_sequence; full detail is in the exported CSV/JSON.