bgpreport

Network · data from 2026-11-12

AS49134 10VPN Research Network

Registry name: AS_10VPN 10VPN Research Network LTD, GB · PeeringDB

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

Announced routes

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

2602:fed2:fd0::/46 Valid Nonecovered by 2602:fed2:fd0::/44 6 1%low visibility 4
2602:fd60:11::/48 Valid RIR databaseALTDB, ARIN 634 100% 69
2602:fed2:31::/48 Valid RIR databaseARIN 634 100% 69
2602:fed2:fd0::/44 Valid RIR databaseARIN 6 1%low visibility 4

AS-SET

PeeringDB's irr_as_set for AS49134: RIPE::AS-10VPN-RESEARCH. 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 (AS49134 isn't in the set, or no route object for AS49134 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 objectsAS49134 in itNot covered
RIPE::AS-10VPN-RESEARCH RIPE 41427 Yes 0

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

  • Route object: none1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: none2602:fed2:fd0::/46No route object for it. A route object for 2602:fed2:fd0::/44 with origin AS49134 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49134 in the RIR database for the space.6 of 636

Route objects not announced

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

158.51.112.0/24ARINInvalid: origin
2a0c:9a40:8200::/48RIPEValid
2a0c:9a40:8201::/48RIPEValid
2a0e:b107:278::/46RIPENo 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.