bgpreport

Network · data from 2026-11-12

AS33371 WMA-BEVERLY-HILLS - WME

Registry name: WMA-BEVERLY-HILLS - WME, US · not in PeeringDB

18IPv4 routes 27.8% RPKI valid · 16.7% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
13No ROA 15 with no route object for this origin
3Low visibility seen by under 10% of full-table peers
5Route objects not announced registered with origin AS33371, seen from no peer

Announced routes

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

143.223.5.0/24 No ROA None 673 100% 67
143.223.8.0/24 No ROA None 673 100% 67
143.223.9.0/24 No ROA None 673 100% 67
143.223.25.0/24 No ROA None 673 100% 67
143.223.102.0/24 No ROA None 673 100% 67
143.223.135.0/24 No ROA None 673 100% 67
143.223.162.0/24 No ROA None 673 100% 67
143.223.176.0/24 No ROA None 673 100% 67
143.223.178.0/24 No ROA None 673 100% 67
143.223.101.0/24 No ROA None 2 0%low visibility 2
143.223.103.0/24 No ROA None 2 0%low visibility 2
193.240.142.128/26 No ROA None 2 0%low visibility 2
143.223.0.0/24 No ROA Other IRR onlyRADB 673 100% 67
143.223.10.0/24 Valid Nonecovered by 143.223.10.0/23 673 100% 67
143.223.11.0/24 Valid Nonecovered by 143.223.10.0/23 673 100% 67
217.79.174.0/24 Valid None 673 100% 67
143.223.10.0/23 Valid RIR databaseARIN 673 100% 67
143.223.12.0/24 Valid RIR databaseARIN 673 100% 67

AS-SET

AS33371 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 34 are in fix.csv.

  • ROA: none13
  • Route object: none15
  • Route object: RIR1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none143.223.5.0/24No ROA covers it. Add a ROA for AS33371, maxLength 24.673 of 673
Route object: none143.223.5.0/24No route object for it. Add a route object with origin AS33371 in the RIR database for the space.673 of 673
ROA: none143.223.8.0/24No ROA covers it. Add a ROA for AS33371, maxLength 24.673 of 673
Route object: none143.223.8.0/24No route object for it. Add a route object with origin AS33371 in the RIR database for the space.673 of 673
ROA: none143.223.9.0/24No ROA covers it. Add a ROA for AS33371, maxLength 24.673 of 673
Route object: none143.223.9.0/24No route object for it. Add a route object with origin AS33371 in the RIR database for the space.673 of 673
ROA: none143.223.25.0/24No ROA covers it. Add a ROA for AS33371, maxLength 24.673 of 673
Route object: none143.223.25.0/24No route object for it. Add a route object with origin AS33371 in the RIR database for the space.673 of 673
ROA: none143.223.102.0/24No ROA covers it. Add a ROA for AS33371, maxLength 24.673 of 673
Route object: none143.223.102.0/24No route object for it. Add a route object with origin AS33371 in the RIR database for the space.673 of 673
ROA: none143.223.135.0/24No ROA covers it. Add a ROA for AS33371, maxLength 24.673 of 673
Route object: none143.223.135.0/24No route object for it. Add a route object with origin AS33371 in the RIR database for the space.673 of 673
ROA: none143.223.162.0/24No ROA covers it. Add a ROA for AS33371, maxLength 24.673 of 673
Route object: none143.223.162.0/24No route object for it. Add a route object with origin AS33371 in the RIR database for the space.673 of 673
ROA: none143.223.176.0/24No ROA covers it. Add a ROA for AS33371, maxLength 24.673 of 673
Route object: none143.223.176.0/24No route object for it. Add a route object with origin AS33371 in the RIR database for the space.673 of 673
ROA: none143.223.178.0/24No ROA covers it. Add a ROA for AS33371, maxLength 24.673 of 673
Route object: none143.223.178.0/24No route object for it. Add a route object with origin AS33371 in the RIR database for the space.673 of 673
ROA: none143.223.101.0/24No ROA covers it. Add a ROA for AS33371, maxLength 24.2 of 673
Route object: none143.223.101.0/24No route object for it. Add a route object with origin AS33371 in the RIR database for the space.2 of 673
ROA: none143.223.103.0/24No ROA covers it. Add a ROA for AS33371, maxLength 24.2 of 673
Route object: none143.223.103.0/24No route object for it. Add a route object with origin AS33371 in the RIR database for the space.2 of 673
ROA: none193.240.142.128/26No ROA covers it. Add a ROA for AS33371, maxLength 26.2 of 673
Route object: none193.240.142.128/26No route object for it. Add a route object with origin AS33371 in the RIR database for the space.2 of 673
ROA: none143.223.0.0/24No ROA covers it. Add a ROA for AS33371, maxLength 24.673 of 673
Route object: RIR143.223.0.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: none143.223.10.0/24No route object for it. A route object for 143.223.10.0/23 with origin AS33371 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33371 in the RIR database for the space.673 of 673
Route object: none143.223.11.0/24No route object for it. A route object for 143.223.10.0/23 with origin AS33371 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33371 in the RIR database for the space.673 of 673
Route object: none217.79.174.0/24No route object for it. Add a route object with origin AS33371 in the RIR database for the space.673 of 673

Route objects not announced

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

143.223.20.0/23RADBNo ROA
143.223.20.0/24RADBNo ROA
143.223.21.0/24RADBNo ROA
143.223.30.0/23RADBNo ROA
143.223.30.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.