bgpreport

Network · data from 2026-11-12

AS29664 RGCOM-VANCO-HAI Flag Telecom UK Limited

Registry name: RGCOM-VANCO-HAI Flag Telecom UK Limited, GB · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS29664, 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.
82.196.32.0/20 Valid RIR databaseRIPE 673 100% 67
82.196.52.0/23 Valid RIR databaseRIPE 673 100% 67
82.196.56.0/24 Valid RIR databaseRIPE 673 100% 67
81.52.199.0/24 Valid RIR databaseRIPE 672 100% 67
82.196.57.0/24 Valid RIR databaseRIPE 672 100% 67

AS-SET

AS29664 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 9 are in fix.csv.

  • Route object: not announced9

Route objects not announced

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

82.196.46.0/24RIPEValid
82.196.56.0/23RIPENo ROA
82.196.58.0/23RIPENo ROA
82.196.58.0/24RIPENo ROA
94.125.32.0/21RIPENo ROA
94.125.32.0/22RIPENo ROA
94.125.36.0/22RIPENo ROA
168.252.96.0/22RIPE-NONAUTHNo ROA
193.43.25.0/24RIPENo 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.