bgpreport

Network · data from 2026-11-12

AS59877 VA telecom

Registry name: vatelecom VA TELECOM SAS, FR · PeeringDB

9IPv4 routes 100.0% RPKI valid · 100.0% with a route object
2IPv6 routes 100.0% RPKI valid · 100.0% with a route object
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
0Route objects not announced registered with origin AS59877, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS59877, 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.
31.223.190.0/24 Valid RIR databaseRIPE 673 100% 67
62.68.65.0/24 Valid RIR databaseRIPE 673 100% 67
91.212.33.0/24 Valid RIR databaseRIPE 673 100% 67
185.61.176.0/22 Valid RIR databaseRIPE 673 100% 67
185.160.52.0/22 Valid RIR databaseRIPE 673 100% 67
193.39.0.0/22 Valid RIR databaseRIPE 673 100% 67
193.56.146.0/24 Valid RIR databaseRIPE 673 100% 67
217.197.108.0/24 Valid RIR databaseRIPE 673 100% 67
45.67.253.0/24 Valid RIR databaseRIPE 668 99% 67
2a02:7b20::/32 Valid RIR databaseRIPE 636 100% 67
2a03:9260::/32 Valid RIR databaseRIPE 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS59877: AS59877:AS-VA-TELECOM. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS59877 isn't in the set, or no route object for AS59877 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS59877 in itNot covered
AS59877:AS-VA-TELECOM RIPE 6123 Yes 0

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

Every route object with origin AS59877 is announced.

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.