bgpreport

Network · data from 2026-11-12

AS52422 AS52422 - Velco Globalnetwork

Registry name: AS52422 - Velco Globalnetwork, HN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS52422, 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.
200.115.188.0/24 Valid Nonecovered by 200.115.188.0/22 661 98% 67
200.115.189.0/24 Valid Nonecovered by 200.115.188.0/22 661 98% 67
200.115.190.0/24 Valid Nonecovered by 200.115.188.0/22 661 98% 67
200.115.191.0/24 Valid Nonecovered by 200.115.188.0/22 661 98% 67
2803:ce00::/32 Valid Other IRR onlyALTDB 630 99% 67

AS-SET

AS52422 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 6 are in fix.csv.

  • Route object: none4
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none200.115.188.0/24No route object for it. A route object for 200.115.188.0/22 with origin AS52422 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52422 in the RIR database for the space.661 of 673
Route object: none200.115.189.0/24No route object for it. A route object for 200.115.188.0/22 with origin AS52422 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52422 in the RIR database for the space.661 of 673
Route object: none200.115.190.0/24No route object for it. A route object for 200.115.188.0/22 with origin AS52422 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52422 in the RIR database for the space.661 of 673
Route object: none200.115.191.0/24No route object for it. A route object for 200.115.188.0/22 with origin AS52422 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52422 in the RIR database for the space.661 of 673
Route object: RIR2803:ce00::/32Route object only in ALTDB. Add it in the RIR database for the space.630 of 636

Route objects not announced

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

200.115.188.0/22ALTDB, NTTCOM, RADBValid

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.