Network Status

Every communications node, current posture, and why. Degraded nodes lead their group; the cause chip tells the story.

Green 9Degraded 1
Main CP

Main CP Node, Theater HQ

Theater HQ Element (fictional)

Green
NN_001Upper TIas of 2026-06-10

Primary hub for the task force upper tier. Fictional node.

TAC

TAC Node, Battle Group East

Battle Group East (fictional)

Green
NN_002Lower TIas of 2026-06-10
Retrans

Retrans Site North (Hilltop 14)

2d Cavalry Sqdn (fictional)

Amber
NN_003FMInterferenceas of 2026-06-10

Intermittent degradation on the command net retrans since 2026-06-09 evening. Suspected interference; ticket TKT_001 in work. Reported up ops channels per MIJI-style procedure.

Retrans Site South

South Flank Bn (fictional)

Green
NN_007FMas of 2026-06-10
Unit Gateway

Unit Gateway, 1st Combined Arms Bn

1st Combined Arms Bn (fictional)

Green
NN_004Lower TIas of 2026-06-10

Unit Gateway, 2d Cavalry Sqdn

2d Cavalry Sqdn (fictional)

Green
NN_008Lower TIas of 2026-06-10

Unit Gateway, 3d Infantry Bn

3d Infantry Bn (fictional)

Green
NN_005Lower TIas of 2026-06-10

Gateway router swap scheduled; see TKT_003.

Unit Gateway, MI Collection Det

MI Collection Det (fictional)

Green
NN_009Upper TIas of 2026-06-10
SATCOM Terminal

SATCOM Terminal Alpha, Theater HQ

Theater HQ Element (fictional)

Green
NN_006SATCOMas of 2026-06-10

SATCOM Terminal Bravo, Airborne Det South

Airborne Det South (fictional)

Green
NN_010SATCOMas of 2026-06-10

Maintenance window requested for 2026-06-16; will brief at the sync.

Signal sites (schematic)

NN_003NN_001NN_007NN_006NN_010NN_002NN_004NN_008NN_005NN_009

Fictional positions, normalized sketch. Dot color is the node status; the halo marks a degraded site.

Degraded node detailTicket queue →
Retrans Site North (Hilltop 14)Amber

Cause: Interference. Intermittent degradation on the command net retrans since 2026-06-09 evening. Suspected interference; ticket TKT_001 in work. Reported up ops channels per MIJI-style procedure.

Lane note

Interference is a signal problem first: it lives here as a node status and a trouble ticket, and goes up ops channels as a MIJI-style report. The S2 acts on it through the existing reporting workflow if ops routes it there; TKT_001 is the live example.