# Can an ISP License Network Operations Records to AI?

> What ISPs, WISPs and telecom operators can license to AI buyers: NOC tickets, routing changes, outage records, and why CPNI and subscriber data stay out.

Canonical: https://origindatapartners.com/guides/isp-network-operations-data-ai
By: Origin Data Partners
Status: Published
Published: 2026-11-17
Updated: 2026-11-17
Sources checked: 2026-11-17

## Quick answer

Yes, for the operator's own network engineering records. An ISP, WISP or telecom operator can license NOC tickets, routing and config changes, outage timelines and postmortems about its own network. Subscriber data stays out: customer proprietary network information (CPNI) under 47 U.S.C. 222, EU traffic data under the ePrivacy Directive, and subscriber traffic captures. Outage reports filed with the FCC are presumed confidential and stay out too.

## Key points

- The line is network engineering versus subscribers: the first is the candidate, the second stays out.
- CPNI covers how, where and how much a customer uses a telecom service, and call detail records.
- EU traffic data must be erased or made anonymous when no longer needed for transmission.
- FCC outage reports are presumed confidential; the operator's internal record of the same outage is a separate document.

## Can an ISP license its network operations records to AI?

Yes, for records about engineering and running its own network, and no for records about its subscribers. NOC tickets, routing and configuration changes, maintenance records, outage timelines and postmortems describe the operator's own work. Subscriber identities, usage, call detail, traffic and the information protected as CPNI stay out of any license.

The table shows the usual split for ISPs, wireless ISPs (WISPs) and telecom operators. This page is general information, not legal advice.

| Record | Candidate? | Condition |
| --- | --- | --- |
| NOC tickets and outage timelines | Yes | Remove subscriber names, accounts, addresses and circuit IDs tied to one customer |
| Routing (BGP) and device config history | Yes | Remove passwords, keys and SNMP communities; check peering agreements |
| Maintenance and change records | Yes | Same checks |
| Postmortems of network outages | Yes | Remove anything copied from filed FCC outage reports |
| Abuse and security incident tickets | Often | Remove complainants and subscribers |
| CPNI, call detail, subscriber usage | No | 47 U.S.C. 222 and FCC rules |
| Subscriber traffic, flow records tied to subscribers, EU traffic data | No | Privacy and ePrivacy rules |
| Filed FCC outage reports | No | Presumed confidential under 47 CFR 4.2 |


## What is CPNI and why does it stay out?

CPNI is customer proprietary network information: "information that relates to the quantity, technical configuration, type, destination, location, and amount of use of a telecommunications service subscribed to by any customer of a telecommunications carrier", plus information in telephone bills ([47 U.S.C. 222](https://www.law.cornell.edu/uscode/text/47/222)). A carrier "shall only use, disclose, or permit access to individually identifiable customer proprietary network information in its provision of" the service and related services, unless the law requires it or the customer approves.

The FCC's CPNI rules extend "carrier" to "an entity that provides interconnected VoIP service", and define call detail information as "any information that pertains to the transmission of specific telephone calls" ([47 CFR 64.2003](https://www.law.cornell.edu/cfr/text/47/64.2003)). An operator that sells voice or VoIP service holds CPNI and must keep it out.

There is a narrow opening for aggregates. A carrier "may use, disclose, or permit access to aggregate customer information" for other purposes, and aggregate customer information means "collective data that relates to a group or category of services or customers, from which individual customer identities and characteristics have been removed" ([47 U.S.C. 222](https://www.law.cornell.edu/uscode/text/47/222)). Network-wide counts can fall here; per-customer records cannot.

For broadband internet access the federal picture has moved. In January 2025 the Sixth Circuit held that "Broadband Internet Service Providers offer only an" information service, not a telecommunications service ([Sixth Circuit](https://www.opn.ca6.uscourts.gov/opinions.pdf/25a0002p-06.pdf)). That does not make subscriber data free to license: privacy notices, state privacy laws and contracts still apply, so treat subscriber data as out either way.


## What does the ePrivacy Directive say about traffic data?

It says EU subscriber traffic data must not be kept for new uses. The directive defines traffic data as "any data processed for the purpose of the conveyance of a communication on an electronic communications network or for the billing thereof". Article 6 says traffic data about subscribers and users "must be erased or made anonymous when it is no longer needed for the purpose of the transmission of a communication", with limited exceptions for billing and consented services ([ePrivacy Directive](https://eur-lex.europa.eu/eli/dir/2002/58/oj/eng)).

Each EU country applies the directive through its own law, and the GDPR applies on top. For an operator with EU subscribers, flow records, connection logs and session data tied to subscribers are out of scope for a data license. Device configs, routing history and the engineering record of an outage, with subscriber details removed, are the candidate.


## What are FCC outage reports and can they be shared?

They are filings in the FCC's Network Outage Reporting System (NORS), and they stay out. An outage is "a significant degradation in the ability of an end user to establish and maintain a channel of communications as a result of failure or degradation in the performance of a communications provider's network" ([47 CFR 4.5](https://www.law.cornell.edu/cfr/text/47/4.5)). Covered providers file a notification, then an initial and a final report.

For cable providers, for example, the notification is due "within 120 minutes of discovering" a qualifying outage "of at least 30 minutes duration", the initial report "not later than 72 hours after discovering the outage" and the final report "not later than 30 days after discovering the outage" ([47 CFR 4.9](https://www.law.cornell.edu/cfr/text/47/4.9)). Thresholds differ by service type. "Reports filed under this part will be presumed to be confidential" ([47 CFR 4.2](https://www.law.cornell.edu/cfr/text/47/4.2)).

The filed report is one document. The NOC ticket, the chat thread, the config change and the internal postmortem of the same outage are the operator's own engineering records. Keep the filed report and text copied from it out, and review the internal records like any other.


## Which network operations records are the candidate?

The operator's own engineering trail. RFC 2142 lists the NOC mailbox for network operations and network infrastructure, next to the ABUSE mailbox for customer relations ([RFC 2142](https://www.rfc-editor.org/rfc/rfc2142.html)). The NOC side of that split is what buyers asked for: what broke, what the engineers saw, what they changed and what happened next.

| Record | What it shows | Remove first |
| --- | --- | --- |
| NOC tickets | Alarm, triage, escalation, fix, closure | Subscriber names, accounts and service addresses |
| Routing and BGP change history | Policy changes, prefix filters, the change that caused or fixed an outage | Passwords and keys; peer details covered by peering agreements |
| Device config archives | Router, switch and firewall configs over years | Credentials, SNMP communities, customer circuit descriptions |
| Maintenance windows and change tickets | Planned work, rollback plans, results | Customer notification lists |
| Outage timelines and postmortems | Cause, impact, repair and follow-up | Text copied from filed FCC reports |
| Security incident tickets | Attacks on the network and the response | Subscriber addresses; payloads |

For how changes are tracked and checked, see [config drift](https://origindatapartners.com/guides/config-drift); for postmortem structure, see [incident postmortem examples](https://origindatapartners.com/guides/incident-postmortem-examples).


## Example: a regional fiber cut, sorted into piles

A fictional regional ISP with 60,000 subscribers loses a fiber route during road work. Traffic shifts to a backup path, which overloads, and service degrades for about two hours. Afterward its network lead sorts the records of that outage.

| Pile | Records | Decision |
| --- | --- | --- |
| Never | The filed FCC notification and reports, the list of affected subscriber accounts, call detail and usage data for the period, flow records tied to subscribers | Excluded |
| Only after work | NOC ticket with chat transcript, router configs before and after, the BGP policy change that rebalanced traffic, syslog from core routers | Subscriber references, passwords and SNMP communities removed; addresses replaced with documentation ranges such as 192.0.2.0/24 |
| Ready first | Internal postmortem, the runbook for fiber cuts, the maintenance ticket for the repair | Checked for text copied from the FCC filing, then joined to the ticket by time and ID |

Fictional example written for this page, not a real operator's records. The cleaned outage, with its config changes and postmortem, is one incident end to end.


## Common mistakes when an ISP reviews its records

Most problems come from subscriber data hiding inside engineering records.

- Leaving circuit descriptions in router configs that name a business customer or a home address.
- Treating flow records as network data when they can be tied to subscribers.
- Pasting the filed FCC outage report into the internal postmortem and then exporting the postmortem.
- Leaving SNMP communities, TACACS keys or BGP passwords in config archives.
- Assuming a per-customer list is aggregate data because names were removed. Aggregates group customers; they are not de-named rows.
- Forgetting that EU traffic data had to be erased or anonymized long before any license was discussed.


## What do AI data buyers want from an ISP?

AI data buyers have asked Origin for the records of a company running and defending its own infrastructure: incidents joined to the change that fixed them (the ticket, the chat thread, the config diff or pull request, and the outcome), configuration and infrastructure-as-code history with commits and reviews going back years, ordered logs or captures of what happened and what was done, and the runbooks, SOC tickets, on-call records and postmortems of the same period. ISPs were named among the companies that hold them. For an operator, the candidate is the network engineering record: NOC tickets, routing and config history, outage timelines and postmortems. Subscriber traffic, CPNI and filed outage reports stay out.

The first step buyers asked for is small: two or three incidents end to end, plus a slice of the configuration history from the same months. For an ISP that could be one outage like the example above, one security incident and the config history of the routers involved, cleaned of subscriber data and credentials. See the [hub guide](https://origindatapartners.com/guides/license-infrastructure-incident-data-ai) for the other kinds of holder and [audit log examples](https://origindatapartners.com/guides/audit-log-examples) for the logs around them. Origin is an independent data partner. Your company decides what is shared and signs any license itself, and a buyer may pay Origin when a deal closes.

Does your company hold records like these? [See what your data is worth](https://origindatapartners.com/check-fit).


## Questions and answers

### Can an ISP license its network operations and outage records for AI training?

Yes, for its own network engineering records: NOC tickets, routing and config changes, outage timelines and postmortems, after subscriber details and credentials are removed. Subscriber traffic, CPNI and EU traffic data stay out, and outage reports filed with the FCC are presumed confidential. The internal record of an outage is a separate document.

### Is CPNI allowed in an AI training data license?

No, not when it identifies a customer. Under 47 U.S.C. 222 a carrier may use individually identifiable CPNI only to provide the service, unless the law requires otherwise or the customer approves. Aggregate customer information, with individual identities and characteristics removed, is treated differently.

### Does CPNI apply to broadband internet providers?

The CPNI section covers telecommunications carriers, and the FCC rules add interconnected VoIP. In January 2025 the Sixth Circuit held that broadband internet access is an information service. Privacy notices, state privacy laws and contracts still apply, so subscriber data should stay out of any license either way.

### Are FCC outage reports confidential?

Yes. Under 47 CFR 4.2, reports filed in the outage reporting system are presumed confidential. Keep the filed notification, initial and final reports, and any text copied from them, out of a data license. The NOC ticket, config changes and internal postmortem of the same outage are separate engineering records.

### Can a telecom operator share traffic data from EU subscribers?

Not for a new use such as model training. The ePrivacy Directive requires traffic data about subscribers and users to be erased or made anonymous when it is no longer needed to transmit a communication, with limited billing and consent exceptions. Each EU country applies the rule through its own law.

### What should a WISP remove from router configs before licensing them?

Passwords, keys, SNMP communities and other credentials; circuit or interface descriptions that name customers or addresses; and any subscriber IP assignments. Replace addresses with consistent stand-ins so routing changes still make sense, and check peering and upstream agreements for confidentiality terms about the network.

## Sources

- [47 U.S.C. 222: privacy of customer information](https://www.law.cornell.edu/uscode/text/47/222)
- [47 CFR 64.2003: definitions for the CPNI rules](https://www.law.cornell.edu/cfr/text/47/64.2003)
- [U.S. Court of Appeals for the Sixth Circuit: Ohio Telecom Association v. FCC (January 2, 2025)](https://www.opn.ca6.uscourts.gov/opinions.pdf/25a0002p-06.pdf)
- [Directive 2002/58/EC (ePrivacy Directive), Articles 2 and 6](https://eur-lex.europa.eu/eli/dir/2002/58/oj/eng)
- [47 CFR 4.5: definition of outage](https://www.law.cornell.edu/cfr/text/47/4.5)
- [47 CFR 4.9: outage reporting thresholds and deadlines](https://www.law.cornell.edu/cfr/text/47/4.9)
- [47 CFR 4.2: availability of outage reports](https://www.law.cornell.edu/cfr/text/47/4.2)
- [RFC 2142: Mailbox Names for Common Services, Roles and Functions](https://www.rfc-editor.org/rfc/rfc2142.html)

## Related reading

- [Can a Company License Its Incident and Config Data to AI?](https://origindatapartners.com/guides/license-infrastructure-incident-data-ai)
- [Audit Log Examples: Fields, SIEM Logs and CloudTrail](https://origindatapartners.com/guides/audit-log-examples)
- [How to de-identify company data before licensing it](https://origindatapartners.com/guides/de-identify-company-data-before-licensing)
- [Can a security company license alerts and incident data to AI?](https://origindatapartners.com/guides/license-security-incident-data-ai)
- [Config Drift: How to Detect It in Terraform and Networks](https://origindatapartners.com/guides/config-drift)
- [Incident Postmortem Examples: Outage, Security and Template](https://origindatapartners.com/guides/incident-postmortem-examples)
- [Anonymize PCAP Files and Logs Without Breaking Analysis](https://origindatapartners.com/guides/anonymize-pcap-files-logs)
