bgpreport

Network · data from 2026-11-12

AS13979 ATT-IPFR - AT&T Enterprises, LLC

Registry name: ATT-IPFR - AT&T Enterprises, LLC, US · not in PeeringDB

7IPv4 routes 0.0% RPKI valid · 0.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
7No ROA 7 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS13979, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS13979, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
15.0.64.0/18 No ROA None 651 97% 67
15.4.64.0/18 No ROA None 651 97% 67
15.12.64.0/18 No ROA None 651 97% 67
198.152.17.0/24 No ROA Other origin only 642 95% 67
204.10.158.0/24 No ROA Other origin only 123 18% 48
204.10.159.0/24 No ROA Other origin only 123 18% 48
137.164.35.76/30 No ROA None 1 0%low visibility 1

AS-SET

AS13979 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 15 are in fix.csv.

  • ROA: none7
  • Route object: none7
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none15.0.64.0/18No ROA covers it. Add a ROA for AS13979, maxLength 18.651 of 673
Route object: none15.0.64.0/18No route object for it. Add a route object with origin AS13979 in the RIR database for the space.651 of 673
ROA: none15.4.64.0/18No ROA covers it. Add a ROA for AS13979, maxLength 18.651 of 673
Route object: none15.4.64.0/18No route object for it. Add a route object with origin AS13979 in the RIR database for the space.651 of 673
ROA: none15.12.64.0/18No ROA covers it. Add a ROA for AS13979, maxLength 18.651 of 673
Route object: none15.12.64.0/18No route object for it. Add a route object with origin AS13979 in the RIR database for the space.651 of 673
ROA: none198.152.17.0/24No ROA covers it. Add a ROA for AS13979, maxLength 24.642 of 673
Route object: none198.152.17.0/24Route objects for it name AS18676. Add a route object with origin AS13979 in the RIR database for the space.642 of 673
ROA: none204.10.158.0/24No ROA covers it. Add a ROA for AS13979, maxLength 24.123 of 673
Route object: none204.10.158.0/24Route objects for it name AS30016. Add a route object with origin AS13979 in the RIR database for the space.123 of 673
ROA: none204.10.159.0/24No ROA covers it. Add a ROA for AS13979, maxLength 24.123 of 673
Route object: none204.10.159.0/24Route objects for it name AS30016. Add a route object with origin AS13979 in the RIR database for the space.123 of 673
ROA: none137.164.35.76/30No ROA covers it. Add a ROA for AS13979, maxLength 30.1 of 673
Route object: none137.164.35.76/30No route object for it. Add a route object with origin AS13979 in the RIR database for the space.1 of 673

Route objects not announced

Route objects with origin AS13979 whose prefix no peer sees AS13979 announce. Many are kept on purpose (backup routes, space announced only in some places).

204.228.175.0/24ARINValid

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.