bgpreport

Network · data from 2026-11-12

AS45652 VPLS Asia

Registry name: VPLS - VPLS ASIA, TH · PeeringDB

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

Announced routes

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

67.43.148.0/23 No ROA None 672 100% 67
103.233.80.0/24 Valid Nonecovered by 103.233.80.0/22 672 100% 66
103.233.82.0/23 Valid Nonecovered by 103.233.80.0/22 672 100% 66
110.34.162.0/23 Valid None 672 100% 66
110.34.158.0/24 Valid Other IRR onlyRADB 672 100% 66
110.34.164.0/24 Valid Other IRR onlyRADB 672 100% 66
110.34.180.0/23 Valid Other IRR onlyRADB 672 100% 66
110.34.183.0/24 Valid Other IRR onlyRADB 672 100% 66

AS-SET

AS45652's PeeringDB record names no 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 31 are in fix.csv.

  • ROA: none1
  • Route object: none4
  • Route object: RIR4
  • Route object: not announced22
ChangePrefix or setDetailFull-table peers
ROA: none67.43.148.0/23No ROA covers it. Add a ROA for AS45652, maxLength 23.672 of 673
Route object: none67.43.148.0/23No route object for it. Add a route object with origin AS45652 in the RIR database for the space.672 of 673
Route object: none103.233.80.0/24No route object for it. A route object for 103.233.80.0/22 with origin AS45652 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45652 in the RIR database for the space.672 of 673
Route object: none103.233.82.0/23No route object for it. A route object for 103.233.80.0/22 with origin AS45652 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45652 in the RIR database for the space.672 of 673
Route object: none110.34.162.0/23No route object for it. Add a route object with origin AS45652 in the RIR database for the space.672 of 673
Route object: RIR110.34.158.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR110.34.164.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR110.34.180.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR110.34.183.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

43.252.120.0/22RADBValid
103.233.80.0/22RADBValid
110.34.139.0/24RADBValid
110.34.162.0/24RADBValid
110.34.166.0/24RADBValid
110.34.180.0/24RADBValid
110.34.181.0/24RADBValid
110.34.184.0/24RADBValid
110.34.185.0/24RADBValid
110.34.186.0/23RADBValid
110.34.188.0/23RADBValid
110.34.190.0/23RADBValid
110.34.190.0/24RADBValid
110.34.191.0/24RADBValid
110.34.220.0/22RADBValid
110.34.220.0/24RADBValid
110.34.221.0/24RADBValid
110.34.222.0/24RADBValid
110.34.223.0/24RADBValid
150.242.228.0/22RADBNo ROA
2401:4a40::/32ALTDBValid
2607:f180:7100::/40ALTDBValid

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.