bgpreport

Network · data from 2026-11-12

AS8030 WORLDNET5-10 - AT&T WorldNet

Registry name: WORLDNET5-10 - AT&T WorldNet, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS8030, 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.
12.194.0.0/16 No ROA None 673 100% 67
135.42.0.0/23 No ROA None 673 100% 67
135.42.1.0/24 No ROA None 673 100% 67
135.42.2.0/24 No ROA None 673 100% 67
135.42.11.0/24 No ROA None 673 100% 67
135.42.12.0/24 No ROA None 673 100% 67
170.141.165.0/24 No ROA None 673 100% 67
170.141.221.0/24 No ROA None 673 100% 67
192.20.122.0/23 No ROA None 673 100% 67
192.20.124.0/22 No ROA None 673 100% 67
192.20.128.0/21 No ROA None 673 100% 67
12.253.0.0/18 Valid RIR databaseARIN 673 100% 67
32.2.128.0/18 Valid RIR databaseARIN 673 100% 67
32.7.32.0/20 Valid RIR databaseARIN 673 100% 67
32.10.0.0/18 Valid RIR databaseARIN 673 100% 67
32.21.160.0/21 Valid RIR databaseARIN 673 100% 67
32.21.168.0/21 Valid RIR databaseARIN 673 100% 67
32.21.176.0/20 Valid RIR databaseARIN 673 100% 67
32.29.128.0/18 Valid RIR databaseARIN 673 100% 67
32.29.224.0/20 Valid RIR databaseARIN 673 100% 67
32.34.252.0/23 Valid RIR databaseARIN 673 100% 67
32.34.254.0/23 Valid RIR databaseARIN 673 100% 67
32.35.64.0/22 Valid RIR databaseARIN 673 100% 67
32.35.68.0/22 Valid RIR databaseARIN 673 100% 67
32.35.72.0/21 Valid RIR databaseARIN 673 100% 67
32.35.80.0/22 Valid RIR databaseARIN 673 100% 67
32.35.84.0/22 Valid RIR databaseARIN 673 100% 67
32.35.88.0/21 Valid RIR databaseARIN 673 100% 67
32.35.104.0/21 Valid RIR databaseARIN 673 100% 67
32.35.152.0/22 Valid RIR databaseARIN 673 100% 67
32.35.156.0/24 Valid RIR databaseARIN 673 100% 67
32.37.192.0/19 Valid RIR databaseARIN 673 100% 67
32.39.128.0/19 Valid RIR databaseARIN 673 100% 67
32.49.116.0/23 Valid RIR databaseARIN 673 100% 67
32.49.118.0/23 Valid RIR databaseARIN 673 100% 67
32.49.240.0/22 Valid RIR databaseARIN 673 100% 67
32.49.244.0/23 Valid RIR databaseARIN 673 100% 67
32.245.192.0/23 Valid RIR databaseARIN 673 100% 67
32.245.200.0/21 Valid RIR databaseARIN 673 100% 67
32.245.208.0/20 Valid RIR databaseARIN 673 100% 67

AS-SET

AS8030 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 25 are in fix.csv.

  • ROA: none11
  • Route object: none11
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none12.194.0.0/16No ROA covers it. Add a ROA for AS8030, maxLength 16.673 of 673
Route object: none12.194.0.0/16No route object for it. Add a route object with origin AS8030 in the RIR database for the space.673 of 673
ROA: none135.42.0.0/23No ROA covers it. Add a ROA for AS8030, maxLength 23.673 of 673
Route object: none135.42.0.0/23No route object for it. Add a route object with origin AS8030 in the RIR database for the space.673 of 673
ROA: none135.42.1.0/24No ROA covers it. Add a ROA for AS8030, maxLength 24.673 of 673
Route object: none135.42.1.0/24No route object for it. Add a route object with origin AS8030 in the RIR database for the space.673 of 673
ROA: none135.42.2.0/24No ROA covers it. Add a ROA for AS8030, maxLength 24.673 of 673
Route object: none135.42.2.0/24No route object for it. Add a route object with origin AS8030 in the RIR database for the space.673 of 673
ROA: none135.42.11.0/24No ROA covers it. Add a ROA for AS8030, maxLength 24.673 of 673
Route object: none135.42.11.0/24No route object for it. Add a route object with origin AS8030 in the RIR database for the space.673 of 673
ROA: none135.42.12.0/24No ROA covers it. Add a ROA for AS8030, maxLength 24.673 of 673
Route object: none135.42.12.0/24No route object for it. Add a route object with origin AS8030 in the RIR database for the space.673 of 673
ROA: none170.141.165.0/24No ROA covers it. Add a ROA for AS8030, maxLength 24.673 of 673
Route object: none170.141.165.0/24No route object for it. Add a route object with origin AS8030 in the RIR database for the space.673 of 673
ROA: none170.141.221.0/24No ROA covers it. Add a ROA for AS8030, maxLength 24.673 of 673
Route object: none170.141.221.0/24No route object for it. Add a route object with origin AS8030 in the RIR database for the space.673 of 673
ROA: none192.20.122.0/23No ROA covers it. Add a ROA for AS8030, maxLength 23.673 of 673
Route object: none192.20.122.0/23No route object for it. Add a route object with origin AS8030 in the RIR database for the space.673 of 673
ROA: none192.20.124.0/22No ROA covers it. Add a ROA for AS8030, maxLength 22.673 of 673
Route object: none192.20.124.0/22No route object for it. Add a route object with origin AS8030 in the RIR database for the space.673 of 673
ROA: none192.20.128.0/21No ROA covers it. Add a ROA for AS8030, maxLength 21.673 of 673
Route object: none192.20.128.0/21No route object for it. Add a route object with origin AS8030 in the RIR database for the space.673 of 673

Route objects not announced

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

32.65.224.0/23RADBNo ROA
32.65.228.0/23RADBNo ROA
32.65.230.0/23RADBNo ROA

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.