bgpreport

Network · data from 2026-11-12

AS209048 VTEL Vcareconnect B.V.

Registry name: VTEL Vcareconnect B.V., NL · not in PeeringDB

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

Announced routes

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

45.8.246.0/27 Invalid: maxLength Nonecovered by 45.8.244.0/22 1 0%low visibility 1
45.8.246.32/27 Invalid: maxLength Nonecovered by 45.8.244.0/22 1 0%low visibility 1
45.8.246.192/27 Invalid: maxLength Nonecovered by 45.8.244.0/22 1 0%low visibility 1
45.8.247.0/24 Valid Nonecovered by 45.8.244.0/22 672 100% 66
45.8.246.0/24 Valid Nonecovered by 45.8.244.0/22 670 100% 66

AS-SET

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

  • ROA: maxLength3
  • Route object: none5
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: maxLength45.8.246.0/27ROA 45.8.244.0/22 AS209048 has maxLength 22; ROA 45.8.246.0/24 AS209048 has maxLength 24; the route is a /27. Raise the maxLength, or add a ROA for 45.8.246.0/27.1 of 673
Route object: none45.8.246.0/27No route object for it. A route object for 45.8.244.0/22 with origin AS209048 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS209048 in the RIR database for the space.1 of 673
ROA: maxLength45.8.246.32/27ROA 45.8.244.0/22 AS209048 has maxLength 22; ROA 45.8.246.0/24 AS209048 has maxLength 24; the route is a /27. Raise the maxLength, or add a ROA for 45.8.246.32/27.1 of 673
Route object: none45.8.246.32/27No route object for it. A route object for 45.8.244.0/22 with origin AS209048 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS209048 in the RIR database for the space.1 of 673
ROA: maxLength45.8.246.192/27ROA 45.8.244.0/22 AS209048 has maxLength 22; ROA 45.8.246.0/24 AS209048 has maxLength 24; the route is a /27. Raise the maxLength, or add a ROA for 45.8.246.192/27.1 of 673
Route object: none45.8.246.192/27No route object for it. A route object for 45.8.244.0/22 with origin AS209048 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS209048 in the RIR database for the space.1 of 673
Route object: none45.8.247.0/24No route object for it. A route object for 45.8.244.0/22 with origin AS209048 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209048 in the RIR database for the space.672 of 673
Route object: none45.8.246.0/24No route object for it. A route object for 45.8.244.0/22 with origin AS209048 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209048 in the RIR database for the space.670 of 673

Route objects not announced

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

45.8.244.0/22RIPEValid
2a0e:a200::/29RIPENo 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.