bgpreport

Network · data from 2026-11-12

AS202 CENTURYLINK-LEGACY-LVLT-202 - Level 3 Parent, LLC

Registry name: CENTURYLINK-LEGACY-LVLT-202 - Level 3 Parent, LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS202, 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.

8.44.80.0/22 No ROA None 666 99% 67

AS-SET

AS202 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 86 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: not announced84
ChangePrefix or setDetailFull-table peers
ROA: none8.44.80.0/22No ROA covers it. Add a ROA for AS202, maxLength 22.666 of 673
Route object: none8.44.80.0/22No route object for it. Add a route object with origin AS202 in the RIR database for the space.666 of 673

Route objects not announced

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

45.146.162.0/23RADBNo ROA
45.230.20.0/24LACNICValid
45.232.116.0/22LACNICValid
50.218.230.0/24RADBValid
66.84.146.0/24ARINValid
74.115.129.0/24ARINValid
104.219.104.0/21ARINValid
104.219.104.0/24ARINValid
104.219.105.0/24ARINValid
104.219.106.0/24ARINValid
104.219.107.0/24ARINValid
104.219.108.0/24ARINValid
104.219.109.0/24ARINValid
104.219.110.0/24ARINValid
104.219.111.0/24ARINValid
107.191.67.0/24ARINValid
129.3.0.0/16RADBNo ROA
135.84.120.0/23ARINValid
142.249.96.0/22ARINValid
143.112.0.0/17ARINValid
143.112.128.0/18ARINValid
143.112.192.0/19ARINValid
143.112.224.0/19ARINValid
143.202.252.0/22LACNICValid
143.255.140.0/22LACNICValid
154.197.52.0/22RADBNo ROA
157.25.130.0/23RIPEValid
157.25.174.0/23RIPEValid
159.212.0.0/16ARINValid
167.250.208.0/22LACNICValid
167.250.208.0/24LACNICValid
167.250.209.0/24LACNICValid
167.250.210.0/24LACNICValid
167.250.211.0/24LACNICValid
170.137.215.0/24ARINValid
170.137.219.0/24ARINValid
170.137.223.0/24ARINValid
170.137.224.0/24ARINValid
170.188.0.0/16ARINValid
170.239.48.0/22LACNICValid
170.239.48.0/24LACNICValid
170.239.49.0/24LACNICValid
170.239.50.0/24LACNICValid
170.239.51.0/24LACNICValid
170.239.168.0/24LACNICValid
174.136.185.0/24ARINValid
181.16.212.0/24LACNICValid
181.193.0.0/16LACNICValid
181.194.0.0/15LACNICValid
185.151.64.0/22RIPEValid
185.151.64.0/23RIPEValid
185.151.66.0/23RIPEValid
185.151.67.0/24RIPEValid
186.0.152.0/22LACNICValid
190.112.56.0/21LACNICValid
190.112.56.0/24LACNICValid
190.112.57.0/24LACNICValid
190.112.58.0/24LACNICValid
190.112.59.0/24LACNICValid
190.112.60.0/24LACNICValid
190.112.61.0/24LACNICValid
190.112.62.0/24LACNICValid
190.112.63.0/24LACNICValid
190.216.110.0/24LACNICValid
198.160.147.0/24ARINValid
198.160.149.0/24ARINValid
198.160.150.0/24ARINValid
199.242.26.0/23ARINValid
199.249.238.0/24ARINValid
200.91.64.0/18LACNICValid
200.91.128.0/18LACNICValid
201.191.0.0/16LACNICValid
201.192.0.0/12LACNICValid
201.237.0.0/16LACNICValid
205.233.244.0/22ARINValid
206.203.78.0/24ARINValid
216.112.49.0/24RADBNo ROA
216.112.50.0/24RADBNo ROA
216.168.136.0/23ARINValid
2001:1330::/29LACNICValid
2800:d300::/29LACNICValid
2801:15:b000::/48LACNICValid
2803:9140::/32LACNICValid
2803:9b20::/32LACNICValid

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.