Rakhine–Ayeyarwady border area shutdown amid Arakan Army fighting, January 2025
2025-01-02 → Resolution unclear
- Rakhine: confirmed by 1 independent source — STOP — last checked 2025-01-02
- Ayeyarwady: confirmed by 1 independent source — STOP — last checked 2025-01-02
DRAFT — needs an editor rewrite. STOP records this as coinciding with fighting between the Arakan Army and junta troops; local reports cited in the record say phone lines were cut immediately after junta troops fled a communication tower they had controlled. STOP's status field is "Unknown". STOP-anchored only; no detection-sequence backfill attempted.
Resolution note: No source confirms a resolution date for this specific junta-ordered cutoff. Stale-ongoing review (M2 patch, 2026-07): the Arakan Army captured Gwa township on Dec 29, 2024 — three days before this event's own date_start — and by Jan 2026 AA's civil administration was issuing licensed Starlink access to Gwa-area civilians, implying the original military-council-ordered cutoff most likely ended once the junta lost control of the area, followed by a different AA-administered access regime (a separate condition, not the same shutdown continuing). No source addresses this specific record directly, so reclassified unresolved rather than ended or left ongoing. See internal research notes — also flagged for a possible merge with 2024-rakhine-connectivity-crisis.
Detection sequence
- Access Now STOP
Access Now STOP record: internet and phone lines cut by the military council in multiple villages along the Pathein River and coast, Gwa township (Rakhine State) and Thabaung township (Ayeyarwady Region), amid Arakan Army–junta fighting.
- IODA
IODA cross-check (maintainer research, 2026-07): queried regions 2754 (Rakhine) and 2756 (Ayeyarwady) for Dec 20, 2024–Feb 15, 2025. At this event's own Jan 2, 2025 start date: NO SIGNAL in either region on either datasource (Rakhine bgp/ping-slash24 both flat at baseline through Jan 24; Ayeyarwady bgp near-flat, ping-slash24 steady ~17.85 mean through Jan 24). A SEPARATE, real signal appears in BOTH regions starting Jan 25-28, 2025, ~3-4 weeks after this event's start: Rakhine ping-slash24 goes to a sustained data gap (ALL NULL) from Jan 25 onward (ambiguous — could be a real outage or an instrumentation/coverage loss, can't distinguish from this signal alone); Ayeyarwady ping-slash24 shows a genuine sustained step-down from ~17.85 to ~10.9 (not noise — a real, lasting level shift) from Jan 27-28 onward. NOT attributed to this event: the ~3-4 week timing gap doesn't match this event's Jan 2 date_start, and region-level data can't isolate Gwa/Thabaung specifically from the rest of Rakhine/Ayeyarwady. Logged here in case it's relevant to a different, not-yet-documented disruption — not used to set this event's date_end or change its status.