Core services
Active systemd services show that core processes are running. This does not alone prove that a phone can send data.
Live network
Current state and recent history.
A small set of public aggregate signals from the stationary core. The view distinguishes active services, an intentionally disconnected radio site, and missing monitoring data.
Waiting for monitoring data
Monitoring data unavailable
The campus monitoring source is not connected to this website yet, or it cannot be reached right now.
Core services
—
active Open5GS units observed
Small cell link
—
gNB reported by the core
Registered UEs
—
current core count
PDU sessions
—
current core count
Return path and N2 connection
—The selected Core VM return route and the small cell's N2 setup state.
DirectRouterN2 upN2 downUnknown or mixedNo sample
Five-minute samples over 24 hours. Short changes can fall between samples; the route and N2 state do not measure UE data reachability.
Last 24 hours
AMF and SMF reachability
—observed core availability
No measurements available for this chart. Missing samples are not zero values.
Gray segments have no monitoring sample. A disconnected small cell can be expected between research sessions.
Devices and sessions
No measurements available for this chart. Missing samples are not zero values.
━ Registered UEs━ PDU sessions
UE traffic at ogstun
Aggregate UE traffic measured at the Open5GS core interface. The rate chart covers the last 24 hours.
UE uplink (RX)
—Total since ogstun startedLatest 5-minute rate: —
UE downlink (TX)
—Total since ogstun startedLatest 5-minute rate: —
The byte counters reset if the VM or interface restarts. They cover all UEs and do not measure radio throughput.
No measurements available for this chart. Missing samples are not zero values.
━ UE uplink (RX)━ UE downlink (TX)Mbit/s
Open5GS service states
VM uptime—
Systemd unit state on the core VM; select an abbreviation to see its function.
Per-service state is unavailable
UEgNBPDUAMFSMF
The site displays allowlisted aggregates from Prometheus. Detailed UE records and operational logs remain in the researcher tools.
Monitoring guide ↗Reading guide
What do the signals tell us?
The public dashboard shows selected aggregate observations from the core. Read these together; no single tile proves the complete application path.
Radio and sessions
A connected gNB reports the signalling relationship. Registered UEs and PDU sessions add evidence about devices and data-session setup.
Traffic at the UPF
ogstun counters and rates show aggregate UE traffic at the core. They are not per-device radio throughput or an application-quality measurement.
Why can the small cell be disconnected?
The radio site may be switched off or disconnected between supervised sessions while the stationary core remains online. A disconnected gNB is not automatically a core failure.
What does a gap or dash mean?
There is no usable observation for that value or interval. Missing or stale monitoring must not be interpreted as zero traffic, zero devices or an outage.
Are these live speed-test results?
No. These are operational counters and sampled history. They describe current network activity, not a controlled benchmark.
Does a selected backhaul route prove connectivity?
No. The return route, N2 signalling, UE data reachability and application success are separate observations. Five-minute samples can also miss brief changes.