Network events

What you’re looking at

event_id

Stable event identifier (PK). Matches the value carried forward in saved tickets’ related_events field.

event_type

One of outage, maintenance, degradation, restoration. Restorations close out a prior outage and inherit its started_at as their resolution time.

region

City-level metro identifier from a fixed 10-region whitelist. Cluster key — most queries filter here first.

severity

critical · major · minor. Cluster key. Critical events always escalate to a NOC page even if no customer complaint arrives.

description

Free-text operator note. Read by the Network Investigator when summarising findings in the saved ticket.

started_at

UTC timestamp the event was first observed. Partition key — DAY-partitioned so multi-week scans prune cheaply.

resolved_at

UTC timestamp the event cleared. Equal to started_at for instantaneous events like restorations.

affected_customers

Best-effort impact estimate at the time of the event. Drives the customer-impact rollup card on the workspace.