ReliefSignal
EnglishENFrançaisFRالعربيةAREspañolESPortuguêsPT
Live command surfaceRed Sea logistics•Global

What is breaking, where, and what do we do now?

Posture: Escalation windowSignals 24h: 486Sources live: 35
Do now
Check continuity posture (strained) before assuming current flow is durable.
Next 6h
Prepare fallback (Secondary hub / corridor fallback) if risk within 24h.
Watch 24h
Track tradeoff exposure: Lower throughput and slower confirmation cadence.
Control rail
Scope stays attached to the map.
Control rail
Corridor-first board controls. Keep location, filters and layers tight.
location → filters → layers
GlobalGlobalStress (structural)Fresh evidencebroad corroboration
Selection: GlobalInfrastructure points show asset locations.
Stay close to ports, airports and corridor pressure first.
Location
Flow: location → filters → layers
Board controls and state
WorkspaceRed Sea logistics
Mission
Reorders panels; does not change scoring.
Workspace state
Persistence version 2026-03-30.v2 · canonical view default · shareable state ready.
Active source: Canonical baseline
Restore target: default
Board mode: Canonical board posture
Saved board label: No saved board yet
Named snapshots: 0 · next label Snapshot 1
Latest named snapshot: None yet
Operational profile: Maritime logistics · Corridor continuity · Red Sea corridor · Next 24h · Early-warning sensitive
Share state: /en/dashboard?workspace=red-sea-logistics&timeRange=72h&logisticsMode=maritime&impactLens=logistics&confidence=medium_plus&preset=logistics&layers=corridors%2Cmaritime%2Cincidents
Open share state
Live filter chips
Canonical presets
Layer groups
Event propagation trace
Last event: no active propagated event yet
This is the initial E1 trace: controls now emit typed workspace events instead of changing only visuals.
Stored state: not yet stored
Operator flow: You are currently looking at the canonical baseline.
Working state: Current working state matches the active baseline.
Profile continuity: Maritime logistics · Corridor continuity · Red Sea corridor · Next 24h · Early-warning sensitive
Draft status: Operator draft is aligned with the active baseline.
Divergence summary: Current board is aligned with the active baseline.
Restore confidence: high
Operator flow summary
Canonical baseline: default · Last saved: none · Latest named snapshot: none · Draft: aligned
Named snapshot preview
Snapshot picker: choose a named snapshot restore target explicitly before restoring or comparing state continuity.
Baseline: default · Active source: canonical baseline · Active label: default · Latest snapshot: none · Total snapshots: 0 · Draft: aligned
Inventory: 0 snapshots · active canonical baseline · draft aligned
Snapshot picker
No snapshot picker entries yet.
No named snapshots yet.
LocationCurrent dashboard scopeIncident log
Shared focus state
Focus: Red Sea corridor
Last event: scope.changed from filters
Reconfiguration audit
scope.changed reshaped tactical field + decision rail
Focus
Red Sea corridor
Event source
filters
Affected surfaces
tactical field, decision rail
Board structure and saved views
Resolved widgets: pressure_map_main · corridor_monitor_main · incident_feed_main · decision_rail_main•Composition: 4 visible · dominant zone Left rail · top widgets pressure_map_main · corridor_monitor_main · incident_feed_main
Corridor watchKeeps logistics corridor posture foregrounded.
Port frictionUse when port congestion and maritime disruption need tighter review.
Supply pressureBiases the board toward operational consequences and action follow-through.
Runtime layout4 visible widgets · density balanced · layer preset logistics
Left rail1 widgets · lead incident_feed_main
Center stage1 widgets · lead pressure_map_main
Right rail1 widgets · lead corridor_monitor_main
Bottom evidence lane1 widgets · lead decision_rail_main
Tactical field

The map decides first for Global

Action, verification and evidence follow the field.
Map firstWorkspace: Red Sea logistics
Authority rule
The map owns the first decision.
Action and verification stay locked to corridor pressure.
Action priority
Move from reading to execution for Global: generate a plan, log impact, and capture evidence.
Corridor-aware execution stays attached to the field.
Generate Action PlanLog impactBrowse playbooks
Action
Do now
What to do now?
Check continuity posture (strained) before assuming current flow is durable. Priority posture: Corridor-first prioritization.
For logistics-focused boards, execution framing comes first in the quick scan. Mission Corridor continuity · trust Early-warning sensitive.
Situation
Watch
What is happening?
Track tradeoff exposure: Lower throughput and slower confirmation cadence. Active profile: Maritime logistics.
Check ports and airspace first before assuming corridor continuity. Action horizons and corridor continuity lead the read once world-to-local posture is clear.
Impact
Next 6h
What is the impact?
Prepare fallback (Secondary hub / corridor fallback) if risk within 24h. Watch dependencies: ports, airspace.
Track tradeoff exposure: Lower throughput and slower confirmation cadence. Failure priorities: port disruption, route failure.
Profile
Enterprise / Ops
Control-room oriented. Ops risk + corridors + infrastructure stress.
Pocket brief
ReliefSignal — Ops update (Global)
Designed for morning brief / delta brief use, then handoff back to the full dashboard.
Stress-proof pocket read
Maritime corridors → Signals indicate elevated disruption levels affecting: Panama Canal, Global maritime. → Context focus: operational risk and system-level exposure for Global. Use the Control Room to drill down into corridors, infrastructure stress, and supporting evidence. → Confidence high
Scan order locked: world → region → country → near you → now.
This compact read should still help under degraded attention, sparse time, and conflicting signal density.
Stress mode: Maritime disruptionPublic usefulness under uncertainty
  • • Scan posture: Maritime corridors
  • • Anchor location: Context focus: operational risk and system-level exposure for Global. Use the Control Room to drill down into corridors, infrastructure stress, and supporting evidence.
  • • Use local fallback: Confidence high
  • • Execute now: Maritime disruption
What changed
Maritime corridors
Why it matters
Signals indicate elevated disruption levels affecting: Panama Canal, Global maritime.
For your context
Context focus: operational risk and system-level exposure for Global. Use the Control Room to drill down into corridors, infrastructure stress, and supporting evidence.
Next 3 checks
  • Maritime disruption
  • Commodity / fuel volatility
  • Airspace & mobility constraints
Confidence: high
Open full dashboard
Data freshness: Last successful update: 2026-04-14T12:00:25.492Z
Continuity fold
Keep verification, friction and context in the same read.
verify → friction → context
Reading guide(optional for logistics boards)
  1. Action: take the next move first.
  2. Corridor pressure: confirm friction and propagation on the map.
  3. Context: use saved views and next checks only if needed.
Use Quick views to change perspective fast.
Lower support

Verification, friction and context

Continue the same board read below the fold.

Verification(trust snapshot, region detail, map context)
Situation
Trust cluster
Trust snapshot and regional verification stay together.
freshness → region drivers → country handoff
Trust snapshot
Fast checks.
Derived from aggregate queries only.
Events last 24h: 486
Active countries (72h): 92
Last ingestion: 2026-04-14T14:06:21.509Z
Last recompute: 2026-04-14T13:09:06.029Z
If values look stale or unexpectedly low, the pipeline may be initializing or delayed.
Region verification appears here when a region is selected, keeping trust and scope in the same cluster.
Map stage rule

Country Risk Choropleth

The map decides first. Risk, move and fallback stay fused to the same first read.
Signals 24h 486Sources live 35
Main risk now
Track tradeoff exposure: Lower throughput and slower confirmation cadence.
Primary move
Check continuity posture (strained) before assuming current flow is durable.
Fallback option
Secondary hub / corridor fallback
risk → move → fallback → map
Single-screen rule: do not split the first answer across hero, rails and lower layers.
Control rail
Scope stays subordinate to the field.
Control rail
Corridor-first board controls. Keep location, filters and layers tight.
location → filters → layers
GlobalGlobalStress (structural)Fresh evidencebroad corroboration
Selection: GlobalInfrastructure points show asset locations.
Stay close to ports, airports and corridor pressure first.
Location
Flow: location → filters → layers
Corridor pressure and disruption lane
Validate corridor pressure before expanding outward.
Asset-first read
Risk first, then crossings, ports, airports and corridor-linked hubs.
Tactical fieldLive pressure surfaceMission OPSAggressive tactical fieldPublic + third-party backedAssets before countriesCorridor-linked hubs first
Pressure
Read where hotspots, dense clusters and sharp signal spikes are forming now.
Propagation
Read corridors, routes and access paths that may tighten or spread next.
Exposure
Read who and what may carry the next-order burden as pressure moves.
Context
Keep infrastructure and support layers visible as consequence context, not primary pressure.
Time rangePropagation view: emergent
Tactical priority (logistics)
Corridor-led
Evidence posture
Externally sustained
Hotspots live
0
Corridor-linked hubs
0
Live geospatial wavefield
Synthetic overlay-energy preview inside the tactical surface
Surface saturation
Operationally light
22
Combined read of wave energy and coupling density to show how loaded the tactical surface feels right now.
Evidence field
Evidence field light
33
Approximate read of how much active evidence mass is implied inside the current tactical surface.
External evidence depth
External evidence depth emerging
45
Proxy read for how much the current surface feels sustained by outward-facing spatial evidence rather than only internal rendering.
Pressure wave37
Corridor wave10
Context wave8
Live overlay stack
richer geospatial depthmap-behavior firstcorridor-linked assets highlighted
Hotspot field
0 clusters
0
Corridor field
0 routes
0
Context field
0 assets
0
Activity field
94 active countries
100
Overlay response state
Pressure
Light pressure
Propagation
Corridors light
Context
Context light
Coupling density
Loose live field
25
Measures how strongly hotspots, corridors, active-country density and context mass are acting like one spatial system.
This pass pushes the map HUD toward visible overlay behavior rather than only descriptive semantics around the surface.
Operational map
Current surface: Logistics pressure•Country activity (72h)•2D•Mission default: OPS•Focus: Global
Interactive control console
Use presets, layers, time and scale to steer the tactical field instead of only reading static framing.
Map mode
Dimension
Pressure hotspotsPropagation corridorsInfrastructure contextHeat by time horizonLive signal densityPublic alert overlaysThird-party layers
Use the surface label + focus state first; overlays are supporting layers, not the primary read. Hotspots are the primary spatial read, corridors explain propagation, and infrastructure exposes operational constraints. In 2D the map should stay flat for clarity; 3D is optional terrain context.
Country shading is suppressed when evidence is too sparse, so large-country color does not overstate the situation.
Layers
Infrastructure mix
Map scale760px
Legend
Low (< 25)
Elevated (25–50)
High (50–75)
Severe (≥ 75)
Insufficient signal
Colors represent a structural logistics stress score (analytical).
Last updated: 2026-04-14T13:48:56.503Z
High-level map only (no tactical markers).
Choropleth only (country-level). No tactical markers.
Map-first field
Dominant zone is leftRail, so the spatial field stays foregrounded. Shared focus now points to Red Sea corridor. Tactical read should stay anchored on Red Sea corridor.
Corridor pressure lane
Corridor monitor and logistics friction stay near the top of the board. Shared focus now points to Red Sea corridor. Tactical read should stay anchored on Red Sea corridor.
Evidence attachment
Evidence should validate corridor pressure before expanding outward. Shared focus now points to Red Sea corridor. Tactical read should stay anchored on Red Sea corridor.
Intelligence rail(tap to expand)
Decision rail
Verify the map, keep the decision tight, and hold rollback close.
Scope: Global · Logistics stress
Verify
Current pressure
Scope: Global
Mode: Logistics Stress (v1)
Operator posture
Profile priority: Corridor continuity · dependencies ports, airspace · failure focus port disruption, route failure.
Decision pressure
See what needs action now, what may rise next, and what stays on watch.
Action order
Act now
Action bias
Top active country is the lead issue right now.
Use the top active score as the front-door action bias, then validate with the rail and field before escalation.
Monitor next
Monitor next
Regional utility / cold-chain stress is the next issue to monitor.
This should stay attached to the main read as the likely next source of widening operational strain.
Keep on watch
Hold posture
Cross-panel drift is watch-state unless reinforced by rail + field + continuity together.
If evidence remains thin or only one panel spikes, treat it as monitor-next rather than action-now.
Rail / tactical alignment
Keep the rail and tactical field aligned around the same dominant operational read.
Tactical field note
Map-first field
Dominant zone is leftRail, so the spatial field stays foregrounded. Shared focus now points to Red Sea corridor.
Tactical read should stay anchored on Red Sea corridor.
Decision rail note
Action
Operational posture starts with immediate follow-through before broad scan. Active shared focus: Red Sea corridor.
Prioritize Red Sea corridor when translating action into action.
Pressure confirmation
Confirm the threshold, hold the evidence floor, then decide whether the current move survives verification.
verify → decide → revoke
Threshold
Escalate only when the threshold holds. Revoke fast when it breaks.
Escalate on corroborated reinforcement
Bias now
Reroute pressure
Corridor disruption is high enough that alternate lanes and fallback assumptions deserve early attention.
Escalate
Escalate when live pulse or corridor stress is reinforced by multiple governed signals or sustained tactical confirmation.
Revoke
Revoke the escalation read if the spike decays quickly or the supporting cross-surface evidence fails to hold.
Evidence floor
Act only when evidence clears the floor. Hold or revoke when it does not.
Bias now
Reroute pressure
Corridor disruption is high enough that alternate lanes and fallback assumptions deserve early attention.
Act
Act only in prepared / reversible ways unless corroboration improves beyond broad contextual inference.
Hold
Hold when the picture depends more on context than direct confirmation in the current scope.
Revoke
Revoke the stronger read if the next corroboration pass does not materially improve local confirmation.
Verification
Confirm quickly, revoke quickly, and keep the horizon close.
Bias now
Reroute pressure
Corridor disruption is high enough that alternate lanes and fallback assumptions deserve early attention.
Confirm
Confirm the move if the same pressure pattern persists across the next cross-surface verification pass.
Revoke
Revoke the move if the reinforcing evidence decays quickly or splits across rail, field and continuity cues.
Horizon
Immediate to next 6h
Continuation path
Keep the move, monitor the next hours, and keep the exit path visible before pressure widens.
continue → monitor → exit
Keep moving
Fallback / monitoring contract
Keep fallback readiness and the next verification move attached to the same compact decision context.
available with penalty
Primary fallback
Secondary hub / corridor fallback
Lower throughput and slower confirmation cadence.
Monitoring contract
Re-check corridor status, hub throughput and fallback lane readiness before escalating or relaxing posture.
Next verification move
Prepare fallback (Secondary hub / corridor fallback) if risk within 24h.
Safe move
Take the safest move that still holds. Abort fast when it breaks.
Bias now
Reroute pressure
Corridor disruption is high enough that alternate lanes and fallback assumptions deserve early attention.
Move
Escalate in a bounded, reversible way tied to the current highest-pressure surface.
Why it holds
The read is strong enough to move because pressure, threshold and evidence floor are aligned rather than isolated.
Abort
Abort or step back if the reinforcing evidence decays quickly or the next verification pass breaks the same pattern.
Timing
Keep now, next and monitor timing visible without extra explanation.
Bias now
Reroute pressure
Corridor disruption is high enough that alternate lanes and fallback assumptions deserve early attention.
Act now
Treat the next bounded move as immediate while the pressure pattern is still reinforced.
Next hours
Use the next 6h to confirm whether the reinforcement holds or starts to decay.
Monitor
Keep secondary surfaces under watch for spread, contradiction or corridor-side drag.
Cost and exit
Read the consequence and tradeoff first, then hold the commitment and rollback contract close.
cost → commit → reverse
Consequence
Show what happens if we act, delay, or absorb the first cost.
Bias now
Reroute pressure
Corridor disruption is high enough that alternate lanes and fallback assumptions deserve early attention.
Act now
A bounded move now can stabilize the current posture before pressure propagates into harder-to-reverse downstream effects.
Delay
Delay increases the chance that the same pressure spreads into fallback, throughput or decision-quality degradation.
First cost
The first cost at risk is usually continuity and recovery flexibility, not only immediate visibility.
Tradeoff
Show the gain, the accepted loss and the main tradeoff with less ceremony.
Bias now
Reroute pressure
Corridor disruption is high enough that alternate lanes and fallback assumptions deserve early attention.
Gain now
You gain earlier control over the pressure window and reduce the chance that disruption spreads unchecked.
Accepted loss
You accept a more aggressive posture and the burden of justifying it quickly if reinforcement fades.
Main tradeoff
Trade some optionality for earlier control while the signal is still strong enough to matter.
Commit or reverse
Commitment / action contract
Commit, defer, or reopen without losing the current action context.
commit → defer
Bias now
Reroute pressure
Corridor disruption is high enough that alternate lanes and fallback assumptions deserve early attention.
Commit now
Commit now to a bounded escalation tied to the highest-pressure governed surface.
Intentionally defer
Defer broader expansion or irreversible posture changes until the reinforcing evidence persists through the next verification loop.
Reopen if
Reopen the commitment immediately if the live pulse decays, corridor stress relaxes or corroboration fractures across surfaces.
Rollback / action contract
Keep the trigger, first reversal and fallback posture close to the same decision.
trigger → reverse
Bias now
Reroute pressure
Corridor disruption is high enough that alternate lanes and fallback assumptions deserve early attention.
Rollback if
Rollback if the reinforcing pressure window collapses, corroboration splits or corridor stress normalizes faster than the escalation case expected.
Reverse first
Reverse the most aggressive posture layer first, while preserving the verification loop and the fallback trace.
Fallback posture
Fall back to prepared watchstanding with bounded monitoring and reversible contingency moves still warm.
Regional utility / cold-chain alert
Fallback: select a region to compute regional utility/cold-chain alert.
Top active (72h)
Click a country to select it.
Top regions (72h)
No region aggregates available.
Click a region to filter the dashboard.
Top drivers (72h)
No drivers available.
qs: country=— · region=—
Supporting intelligence layer
Validate the map before expanding outward.
map → validate → inspect
Decision-linked evidence lane
View all incidents
Validate corridor and map pressure early. Shared focus: Red Sea corridor.
Signal pulse
LIVE SIGNAL RAIL
Incident feed (24h): 0 · Official alert (24h): 530
Signals now (24h): 838 · previous 24h: 601(+237, +39.4%)
Live pulse: 15m 40 · 60m 40 LIVE
NOWOfficial alertTier A
M 4.7 - 152 km SE of Attu Station, Alaska
— • — • other • corroboration high
ShakeMap - IIITime2026-04-14 12:45:45 UTC2026-04-14 12:45:45 UTC at epicenterLocation52.096°N 175.056°EDepth61.70 km (38.34 mi)
2026-04-14T14:06:20.335Zconf: 0.78
NOWOfficial alertTier A
M 1.3 - 7 km NW of The Geysers, CA
— • — • other • corroboration high
Time2026-04-14 12:05:28 UTC2026-04-14 12:05:28 UTC at epicenterLocation38.815°N 122.818°WDepth0.68 km (0.42 mi)
2026-04-14T14:06:21.509Zconf: 0.68
NOWOfficial alertTier A
M 1.0 - 23 km WNW of Mentone, Texas
— • — • other • corroboration high
Time2026-04-14 12:09:05 UTC2026-04-14 12:09:05 UTC at epicenterLocation31.756°N 103.841°WDepth7.18 km (4.46 mi)
2026-04-14T14:06:21.420Zconf: 0.68
Inherited lower-stack suppression
Hold the same cockpit silhouette below the first screen a little longer.
Support stack deferred below cockpit continuity fold.
Incidents · scoped by Red Sea corridorLogistics · scoped by Red Sea corridorCritical supply · scoped by Red Sea corridorMethodology · scoped by Red Sea corridor
Deep analysis boards(secondary layer, below the cockpit slide)
Deep analysis should stay scoped to Red Sea corridor unless the operator intentionally broadens the board.
System trace remains scoped by the shared focus on Red Sea corridor.
Status spine

System Trace

Hotspot-first propagation read: where pressure started, how it may move through corridors, and what downstream context deserves attention.

Hotspot pulse
Primary driver: military intensity
Current scope: Global. Read this as the first point of spatial pressure, not the whole story.
Corridor highlight
No elevated corridor highlighted right now.
Use this to decide whether hotspot pressure is turning into movement or access friction.
Downstream exposure glow
Watch downstream exposure around ARE.
This is a downstream context bridge, not a forecast and not a direct local diagnosis.
Watchlist review should stay aligned with the shared focus on Red Sea corridor.
Watchlists + saved views
Keep persistent operating context instead of rebuilding it every visit.
Watchlist
No watchlist items yet.
Saved views
Cockpit continuity fold

Do now / Next 6h / Next 24h

The action window stays inside the same cockpit language instead of dropping into a legacy white board immediately below the map stage.

Do now
  • Check corridor and port status for Global before treating timing assumptions as stable.
  • Review procurement-sensitive items tied to Global.
  • Review conflict-linked disruption drivers before escalating conclusions for Global.
Next 6h
  • Recheck maritime disruption signals for corroboration and spread.
  • Check whether commodity stress is becoming more corroborated across sources.
  • Check whether conflict intensity is propagating into access or logistics friction.
Next 24h
  • Update shipment timing assumptions if disruption remains persistent.
  • Refresh procurement exposure assumptions if price/supply stress persists.
  • Refresh disruption assumptions if conflict-linked signals remain elevated.
Structural friction cluster

Corridor board (Maritime + Air)

Operational status view for disrupted and elevated corridors with confidence hints.

Open logistics
No non-normal maritime/air corridors for current context.
Structural friction cluster
Customs, ground mobility, utilities and sourcing exposure belong to one structural-friction cluster under the support continuum.
Read these boards together when you need to understand drag across movement, infrastructure and procurement, not as isolated destinations.
Cluster flow: corridor → border → utilities → sourcing
Customs / Border friction

Cross-border delay pressure

Early operational indicator for customs, inspection and document friction by active corridor context.

LOWFriction score: 0/100
No corridor friction signals in current context.
inspection: 0strike: 0document: 0queue: 0
Do now
pre-clear customs docs for priority SKUs.
Next 6h
confirm alternate border/corridor options.
Next 24h
rebalance buffer stock for delayed lanes.
Rail + Road disruptions

Ground mobility stress

Operational snapshot for land-route pressure with fallback mode hints.

LOWGround stress: 0/100
No rail/road-specific corridor disruptions detected in current context.
Fallback hint
Land routes stable; keep periodic checks.
Utilities risk

Power / telecom / water stress proxy

Operational proxy from infrastructure stress signals to anticipate cold-chain and warehousing impact.

LOWUtility stress: 0/100
2 utility signal(s) · 0 disrupted · 0 elevated
Ops hint
Utility stress low: maintain routine monitoring and contingency checks.
Supplier / procurement exposure

Resilience actions for sourcing risk

Geo-exposure proxy from active-country intensity and corridor stress. Use as planning support.

MODERATEExposure score: 25/100corridor disruption factor: 100%
Most exposed countries (proxy)
  • ARE100.0
  • AFG99.6
  • HTI99.6
  • LBN99.4
  • CAN97.0
Recommended resilience actions
  • Pre-qualify alternate suppliers in lower-stress regions.
  • Increase safety stock for top-risk lanes/items.
  • Apply temporary lead-time buffer where corridor stress is elevated.
Global Timeline(collapsed)
Collapsed by default. Shared focus currently biases review toward Red Sea corridor.

Global Event Timeline

Recent, descriptive timeline (last 72h). Source links only. No predictions.

How to use: Scan the brief, then the timeline, then review your context impact.

NOW (≤ 6h)
Disaster2h agoESP
Green flood alert in Spain
source
Disaster2h agoDZA
Green flood alert in Algeria
source
Last 24h
Conflict/Security10h agoAGO
Sudan: Three children born into war every minute as maternal deaths rise and health services deteriorate
source
Conflict/Security12h agoARE
2026 update: Takaaya Sudan’s community kitchens running on fumes
source
Conflict/Security13h agoARE
Hundreds of Sudan’s community kitchens forced to shut in last six months, new Islamic Relief research finds
source
Conflict/Security19h agoHTI
Haiti: Tragedy at the Citadelle Laferrière: Statement from the Office of the Resident and Humanitarian Coordinator
source
Conflict/Security9h agoARE
World: The Long Reach of War: The Middle East Conflict’s Economic Impact on Fragile Contexts (April 2026)
source
24–48h
Conflict/Security26h agoCAN
MIDDLE EAST LIVE 13 April: US-Iran talks falter; Strait of Hormuz uncertainty deepens
source
Conflict/Security24h agoARE
Sudan - National Health Cluster Meeting, 8 April 2026 [Meeting Minutes]
source
Conflict/Security30h agoAFG
Iran: Escalation in the Middle East and Beyond Situation Report (10 April 2026)
source
Conflict/Security26h agoARE
Sudan: Top UN aid official warns of ‘abandoned crisis’ as war enters fourth year
source
Conflict/Security26h agoHTI
COI Query - Haiti: Security Situation in Port-au-Prince
source
Conflict/Security26h agoIDN
Indonesia - Earthquake and floods (ADINet, GDACS, BMKG) (ECHO Daily Flash of 13 April 2026)
source
Conflict/Security27h agoMMR
Myanmar Crisis Situation Analysis (Period: 30/03/26 - 05/04/26)
source
Conflict/Security24h agoCOG
World: HCI Condemns the Tragic Killing of More Than 1,000 Humanitarian Workers
source
Structural friction layer(macro score, impact boards, corridor drag and global brief)
Impact
Structural friction cluster
Macro pressure, corridor drag and infrastructure stress now belong to one tighter structural-friction cluster.
Friction flow: macro pressure → corridor drag → utilities → sourcing
Global Crisis Index
64
Composite (activity + stress + weather + corridors). Descriptive only.
Trend: stable
Top drivers
  • Activity signals (72h) — avg(top10)=93.9
  • Corridor disruptions — non-normal ratio=100%
  • Infrastructure stress — score=27.0

Ops Disruption Risk (Beta)

Probabilistic, evidence-linked signals (official + indicators). Descriptive only.

So what: LAS: 31 / 100 risk score
Why: airport_closure
Confidence: HIGH
Updated: 2026-04-14T13:48:56.503Z
View ops
LAS
airporthigh
p(restricted): 0.31
Evidence: link!LAS 01/129 LAS AD AP CLSD TO NON SKED TRANSIENT GA ACFT EXC 24HR PPR 702-261-7775 2601271912-2604292300 · Start Jan 27
31
score (0–100)
SNA
airporthigh
p(restricted): 0.31
Evidence: link!SNA 04/027 SNA AD AP CLSD DLY 0630-1315 2604140630-2604151315 · Start Apr 14 at 06:30 UTC. · Reopen Apr 15 at 13:15 UTC
31
score (0–100)
SAN
airporthigh
p(restricted): 0.31
Evidence: link!SAN 03/071 SAN AD AP CLSD TO NON SKED TRANSIENT GA ACFT EXC PPR 619-298-7704 2603181300-2610010800 · Start Mar 18 at 13
31
score (0–100)
IAH
airporthigh
p(restricted): 0.14
Evidence: linkVOL:Compacted Demand · Max 30 minutes
14
score (0–100)
FLL
airporthigh
p(restricted): 0.14
Evidence: linkTM Initiatives:MIT:VOL · Max 30 minutes
14
score (0–100)
Confidence reflects source kind + freshness + agreement; not a guarantee of ground truth.

Global Infrastructure Stress

Descriptive status board for monitoring context. No predictions or tactical guidance.

So what: Highest pressure: Recent conflict activity (72h) (SEVERE)
Why: top country: ARE
Confidence: —
Updated: 2026-04-14T13:48:56.503Z
Maritime
Red Sea
no major signals
NORMAL
Suez Canal
no major signals
NORMAL
Panama Canal
source
HIGH
Global maritime
no major signals
ELEVATED
Airspace
Global mobility
no major signals
NORMAL
Eastern Mediterranean air
no major signals
NORMAL
Persian Gulf air
no major signals
NORMAL
Recent conflict activity (72h)
top country: ARE
SEVERE
Energy
Energy
source
NORMAL
Weather
Weather
no major signals
NORMAL

Global Impact Signals

Interpretability layer: descriptive links between signals and potential impact pathways. No predictions.

So what: Top corridor signal: Suez Canal / Eastern Med ↔ Red Sea (DISRUPTED)
Why: source
Confidence: —
Updated: 2026-04-14T13:48:56.503Z
Top corridor disruptions
Suez Canal / Eastern Med ↔ Red Sea
source
DISRUPTED
Strait of Hormuz
source
DISRUPTED
Red Sea / Bab-el-Mandeb
source
DISRUPTED
Panama Canal
source
DISRUPTED
Strait of Malacca
source
DISRUPTED
Infrastructure stress drivers
Infrastructure exposure
no local exposure selected
NORMAL

Note: exposure-style view (counts), not a forecast or real-time status.

Humanitarian hotspots (vH)
United Arab Emirates (ARE)
Lebanon: Middle East: We witness how civilians are suffering | NRCvH is descriptive (signals-based), not a forecast
49.4
vH
Lebanon (LBN)
Lebanon: Middle East Regional Response Situation Report #1 | March 3, 2026vH is descriptive (signals-based), not a forecast
45.5
vH
Israel (ISR)
Israel tightens siege on Gaza amid Iran warvH is descriptive (signals-based), not a forecast
42.6
vH
30.0
vH
28.7
vH
Global Situation Brief(collapsed)
Situation brief remains downstream of the current shared focus on Red Sea corridor.

Global Situation Brief

Descriptive summary only. No predictions or operational guidance.

Last updated: 2026-04-14T13:48:56.503Z
Stress-proof brief scan
Conflict / Activity → Maritime corridors → Airspace / Mobility → Local verification
Scan order locked: world → region → country → near you → now.
This compact read should still help under degraded attention, sparse time, and conflicting signal density.
Stress mode: Read top line, then verify the strongest driverPublic usefulness under uncertainty
  • • Scan posture: Conflict / Activity
  • • Anchor location: Airspace / Mobility
  • • Use local fallback: Local verification
  • • Execute now: Read top line, then verify the strongest driver
Formation trace
Provenance density: strong
global output formed from 3 visible driver(s), evidence quality context and global brief sections 5
This read exposes a stronger visible formation path and is easier to inspect quickly.
Public provenance contract: important brief outputs should keep a visible formation path instead of reading like unsupported summary language.
Conflict / Activity
Recent activity signals indicate elevated reporting intensity (score 100 / 100). Top country by recent activity signal: ARE.
Maritime corridors
earthquake.usgs.gov
Signals indicate elevated disruption levels affecting: Panama Canal, Global maritime.
Airspace / Mobility
Signals indicate elevated mobility constraints in: Recent conflict activity (72h).
Weather disruption
No data available.
Energy
stooq.com
No major signals detected.
Context consequence layer(personal/contextual consequences and follow-through)
Context

Context action cluster

Personal consequence, next checks and prepared follow-through should read as one deferred action cluster.

Context action cluster
Personal impact, next checks and prepared action now compress into one context-action cluster.
Context flow: consequence → checks → lens → playbook
Role-fit check: the cockpit remains anchored on Red Sea corridor without collapsing back into a generic dashboard read.
Impact for your context

Set your country to personalize this view

This panel is context-dependent. Use “Use my context” or select a country to enable personalized impact interpretation.

Next checks

Short follow-up checks for the current context.

Audit path: Sources · Methodology · Corrections
Set a country in your context to enable Next Checks.

Operational lens

Set your country to enable this view.

Set your country or use your location to personalize.

Recommended playbook

Set your country to enable context-aware recommendations.

Set your country or use your location to personalize.