bgpreport

Network · data from 2026-11-12

AS137959 VTL Network

Registry name: VTL-AS-AP - Vision Technologies Ltd., BD · PeeringDB

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

Announced routes

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

2403:2e40:2:2::/64 Invalid: maxLength Nonecovered by 2403:2e40:2::/48 6 1%low visibility 6
2403:2e40:2:3::/64 Invalid: maxLength Nonecovered by 2403:2e40:2::/48 6 1%low visibility 6
2403:2e40:2:4::/64 Invalid: maxLength Nonecovered by 2403:2e40:2::/48 6 1%low visibility 6
2403:2e40:3::/64 Invalid: maxLength Nonecovered by 2403:2e40:3::/48 6 1%low visibility 6
103.31.179.0/24 Valid RIR databaseAPNIC 671 100% 66
103.118.76.0/24 Valid RIR databaseAPNIC 671 100% 67
103.118.79.0/24 Valid RIR databaseAPNIC 671 100% 67
103.31.178.0/24 Valid RIR databaseAPNIC 670 100% 67
103.118.77.0/24 Valid RIR databaseAPNIC 670 100% 68
103.118.78.0/24 Valid RIR databaseAPNIC 670 100% 68
2403:2e40:1::/48 Valid RIR databaseAPNIC 636 100% 69
2403:2e40:2::/48 Valid RIR databaseAPNIC 636 100% 67
2403:2e40:10::/48 Valid RIR databaseAPNIC 636 100% 70
2403:2e40:3::/48 Valid RIR databaseAPNIC 635 100% 67
103.31.178.0/23 Valid RIR databaseAPNIC 0 0%low visibility 1
103.118.76.0/22 Valid RIR databaseAPNIC 0 0%low visibility 1
103.118.76.0/23 Valid RIR databaseAPNIC 0 0%low visibility 1
103.118.78.0/23 Valid RIR databaseAPNIC 0 0%low visibility 1

AS-SET

AS137959's PeeringDB record names no 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 8 are in fix.csv.

  • ROA: maxLength4
  • Route object: none4
ChangePrefix or setDetailFull-table peers
ROA: maxLength2403:2e40:2:2::/64ROA 2403:2e40:2::/48 AS137959 has maxLength 48; the route is a /64. Raise the maxLength, or add a ROA for 2403:2e40:2:2::/64.6 of 636
Route object: none2403:2e40:2:2::/64No route object for it. A route object for 2403:2e40:2::/48 with origin AS137959 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS137959 in the RIR database for the space.6 of 636
ROA: maxLength2403:2e40:2:3::/64ROA 2403:2e40:2::/48 AS137959 has maxLength 48; the route is a /64. Raise the maxLength, or add a ROA for 2403:2e40:2:3::/64.6 of 636
Route object: none2403:2e40:2:3::/64No route object for it. A route object for 2403:2e40:2::/48 with origin AS137959 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS137959 in the RIR database for the space.6 of 636
ROA: maxLength2403:2e40:2:4::/64ROA 2403:2e40:2::/48 AS137959 has maxLength 48; the route is a /64. Raise the maxLength, or add a ROA for 2403:2e40:2:4::/64.6 of 636
Route object: none2403:2e40:2:4::/64No route object for it. A route object for 2403:2e40:2::/48 with origin AS137959 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS137959 in the RIR database for the space.6 of 636
ROA: maxLength2403:2e40:3::/64ROA 2403:2e40:3::/48 AS137959 has maxLength 48; the route is a /64. Raise the maxLength, or add a ROA for 2403:2e40:3::/64.6 of 636
Route object: none2403:2e40:3::/64No route object for it. A route object for 2403:2e40:3::/48 with origin AS137959 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS137959 in the RIR database for the space.6 of 636

Route objects not announced

Every route object with origin AS137959 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.