bgpreport

Network · data from 2026-11-12

AS36032 WBD-AS36032 - WARNER BROS ENTERTAINMENT INC

Registry name: WBD-AS36032 - WARNER BROS ENTERTAINMENT INC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS36032, 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.
168.161.199.0/24 No ROA Nonecovered by 168.161.192.0/21 673 100% 67
168.161.212.0/24 No ROA None 673 100% 67
168.161.213.0/24 No ROA None 673 100% 67
168.161.224.0/24 No ROA None 673 100% 67
168.161.204.0/24 No ROA Other origin only 672 100% 67
168.161.192.0/21 No ROA Other IRR onlyRADB 673 100% 67
168.161.211.0/24 No ROA Other IRR onlyRADB 673 100% 67
168.161.220.0/24 No ROA Other IRR onlyRADB 673 100% 67
168.161.203.0/24 No ROA Other IRR onlyRADB 672 100% 67
168.161.217.0/24 No ROA Other IRR onlyRADB 672 100% 67
168.161.239.0/24 No ROA Other IRR onlyRADB 671 100% 67

AS-SET

AS36032 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: none11
  • Route object: none5
  • Route object: RIR6
  • Route object: not announced22
ChangePrefix or setDetailFull-table peers
ROA: none168.161.199.0/24No ROA covers it. Add a ROA for AS36032, maxLength 24.673 of 673
Route object: none168.161.199.0/24No route object for it. A route object for 168.161.192.0/21 with origin AS36032 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36032 in the RIR database for the space.673 of 673
ROA: none168.161.212.0/24No ROA covers it. Add a ROA for AS36032, maxLength 24.673 of 673
Route object: none168.161.212.0/24No route object for it. Add a route object with origin AS36032 in the RIR database for the space.673 of 673
ROA: none168.161.213.0/24No ROA covers it. Add a ROA for AS36032, maxLength 24.673 of 673
Route object: none168.161.213.0/24No route object for it. Add a route object with origin AS36032 in the RIR database for the space.673 of 673
ROA: none168.161.224.0/24No ROA covers it. Add a ROA for AS36032, maxLength 24.673 of 673
Route object: none168.161.224.0/24No route object for it. Add a route object with origin AS36032 in the RIR database for the space.673 of 673
ROA: none168.161.204.0/24No ROA covers it. Add a ROA for AS36032, maxLength 24.672 of 673
Route object: none168.161.204.0/24Route objects for it name AS40703. Add a route object with origin AS36032 in the RIR database for the space.672 of 673
ROA: none168.161.192.0/21No ROA covers it. Add a ROA for AS36032, maxLength 21.673 of 673
Route object: RIR168.161.192.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none168.161.211.0/24No ROA covers it. Add a ROA for AS36032, maxLength 24.673 of 673
Route object: RIR168.161.211.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none168.161.220.0/24No ROA covers it. Add a ROA for AS36032, maxLength 24.673 of 673
Route object: RIR168.161.220.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none168.161.203.0/24No ROA covers it. Add a ROA for AS36032, maxLength 24.672 of 673
Route object: RIR168.161.203.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none168.161.217.0/24No ROA covers it. Add a ROA for AS36032, maxLength 24.672 of 673
Route object: RIR168.161.217.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none168.161.239.0/24No ROA covers it. Add a ROA for AS36032, maxLength 24.671 of 673
Route object: RIR168.161.239.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

168.161.200.0/23RADBNo ROA
168.161.200.0/24RADBNo ROA
168.161.201.0/24RADBNo ROA
168.161.202.0/23RADBNo ROA
168.161.202.0/24ARIN, RADBValid
168.161.205.0/24ARINValid
168.161.206.0/24RADBNo ROA
168.161.210.0/24RADBNo ROA
168.161.215.0/24RADBNo ROA
168.161.216.0/23RADBNo ROA
168.161.216.0/24RADBNo ROA
168.161.218.0/23RADBNo ROA
168.161.218.0/24RADBNo ROA
168.161.219.0/24RADBNo ROA
168.161.228.0/24RADBNo ROA
168.161.251.0/24RADBValid
204.140.3.0/24RADBNo ROA
204.140.5.0/24NTTCOM, RADBNo ROA
204.140.6.0/24RADBNo ROA
204.140.7.0/24RADBNo ROA
204.140.8.0/23RADBNo ROA
204.140.10.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.