bgpreport

Network · data from 2026-11-12

AS40703 WBD-AS40703 - Turner Broadcasting System, Inc.

Registry name: WBD-AS40703 - Turner Broadcasting System, Inc., US · not in PeeringDB

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

Announced routes

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

157.166.0.0/24 No ROA None 673 100% 67
157.166.180.0/24 No ROA None 673 100% 67
168.161.108.0/24 No ROA Other IRR onlyRADB 673 100% 67
157.166.176.0/23 Valid None 668 99% 67
157.166.216.0/21 Valid Other IRR onlyRADB 673 100% 67
157.166.219.0/24 Valid Other IRR onlyRADB 672 100% 66
157.166.128.0/24 Valid Other IRR onlyRADB 671 100% 67
168.161.107.0/24 Valid Other IRR onlyRADB 671 100% 67
157.166.168.0/21 Valid Other IRR onlyRADB 670 100% 67
157.166.191.0/24 Valid RIR databaseARIN, RADB 672 100% 67
168.161.100.0/24 Valid RIR databaseARIN, RADB 672 100% 67

AS-SET

AS40703 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 44 are in fix.csv.

  • ROA: none3
  • Route object: none3
  • Route object: RIR6
  • Route object: not announced32
ChangePrefix or setDetailFull-table peers
ROA: none157.166.0.0/24No ROA covers it. Add a ROA for AS40703, maxLength 24.673 of 673
Route object: none157.166.0.0/24No route object for it. Add a route object with origin AS40703 in the RIR database for the space.673 of 673
ROA: none157.166.180.0/24No ROA covers it. Add a ROA for AS40703, maxLength 24.673 of 673
Route object: none157.166.180.0/24No route object for it. Add a route object with origin AS40703 in the RIR database for the space.673 of 673
ROA: none168.161.108.0/24No ROA covers it. Add a ROA for AS40703, maxLength 24.673 of 673
Route object: RIR168.161.108.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: none157.166.176.0/23No route object for it. Add a route object with origin AS40703 in the RIR database for the space.668 of 673
Route object: RIR157.166.216.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR157.166.219.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR157.166.128.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR168.161.107.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR157.166.168.0/21Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

157.166.21.0/24RADBNo ROA
157.166.129.0/24RADBNo ROA
157.166.154.0/23RADBNo ROA
157.166.160.0/21RADBValid
157.166.173.0/24RADBValid
157.166.174.0/23RADBValid
157.166.183.0/24RADBNo ROA
157.166.208.0/24RADBNo ROA
157.166.216.0/22RADBValid
157.166.216.0/23RADBValid
157.166.216.0/24RADBValid
157.166.217.0/24RADBValid
157.166.218.0/24RADBValid
157.166.220.0/23RADBValid
157.166.220.0/24RADBValid
157.166.221.0/24RADBValid
157.166.222.0/24RADBValid
157.166.223.0/24RADBValid
168.161.0.0/24RADBNo ROA
168.161.1.0/24RADBNo ROA
168.161.12.0/22RADBNo ROA
168.161.12.0/23RADBNo ROA
168.161.14.0/23RADBNo ROA
168.161.24.0/22RADBValid
168.161.96.0/24RADBNo ROA
168.161.97.0/24NTTCOM, RADBNo ROA
168.161.100.0/23RADBNo ROA
168.161.104.0/24RADBValid
168.161.105.0/24RADBValid
168.161.106.0/24RADBValid
168.161.124.0/24RADBNo ROA
168.161.204.0/24RADBNo 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.