PON Outage Notification Model

This document describes the structure of PON outage notifications sent to customer webhook endpoints when network issues are detected or resolved.

Overview

When a PON outage is detected, updated, or cleared, the system sends a message to configured webhook endpoint. The request body contains a JSON payload conforming to the structure described below.

Model Structure

Root Object: Pon Outage Notification Model

Field	Type	Required	Description
issue	string	Yes	Always set to "pon-outage" for PON outage notifications
timestamp	string (ISO 8601)	Yes	Timestamp when the network issue was registered (UTC)
tenant	string	No	Tenant name/identifier. May be null
outage_status	string	Yes	Current status of the outage (see Outage Status Values)
affected_subscribers	array	Yes	List of subscribers affected by this PON outage (see Affected Subscribers)

Affected Subscribers

Each entry in the affected_subscribers array has defined structure:

Field	Type	Required	Description
account_id	string	Yes	Unique identifier for the affected subscriber's account
onu_serial_number	string	Yes	Serial number of the Optical Network Unit (ONT) device
city	string	No	Geographic city where the affected subscriber is located. May be null
pon_port	string	No	PON port identifier (e.g., "1/0/1@1/1/1"). May be null

Outage Status Values

The outage_status field can have one of the following values:

Value	Description
"detected"	A new outage has been detected or an existing outage has been updated
"cleared"	The outage has been resolved
"undefined"	The outage status could not be determined

Note: Both "raised" and "updated" statuses from the upstream system are mapped to "detected" in the notification.

Example Payload

{
  "issue": "pon-outage",
  "timestamp": "2025-10-06T12:28:08.958256Z",
  "tenant": "adtran",
  "outage_status": "detected",
  "affected_subscribers": [
    {
      "account_id": "123",
      "onu_serial_number": "serial-number",
      "city": "Huntsville",
      "pon_port": "1/0/1@1/1/1"
    }
  ]
}