public · delayed · sanitized

EVE MONITOR · Intel Network

Public, delayed and sanitized summary from the sensor network. Not live intel.

Minimum delay: 10 min

Updated: 8/6/2026, 5:04:51 PM
Refresh ~10 min
Operational view (alliance · SSO) →
OPSEC: Public showcase with a minimum delay. No pilot names, no raw logs, no live position. Operational intel requires EVE SSO + alliance role.
Regions with active coverage
No regions with active sensor coverage in this window.
More regions will appear as more pilots keep EVE MONITOR open on their intel channels.

Overview

Events 24h
0
Hostile 24h
0
WH/Camp 24h
0
Clear 24h
0

7d window matches 24h: the sensor network does not have enough history yet, full 7-day context unavailable.

Hot systems · 24h

No active systems in this window.

Hot systems · 7d

No active systems in this window.

How the sensor network works

  • · Anyone running EVE MONITOR can act as a sensor: it locally reads the alliance/local intel channels already open in their client.
  • · The server dedupes and aggregates by system/region: multiple sensors on the same channel = same data, never duplicated.
  • · Regions only appear here once sensor coverage is active. No sensors = no public data.
Event heartbeat (advanced, delayed)0 · delay 10m

Delayed, sanitized event stream: system, kind and approximate age only. No pilot names, no snippets, no operational tags. Useful only if you want to see baseline noise.

No delayed events available in this window.

  • · Nessuna attività aggregata recente. Il report pubblico parte dalle intel condivise dal Radar 0.0.
EVE MONITOR · Intel Network · public showcase. Data from intel channels read by authorized pilots. Not a replacement for the alliance intel bridge.