bgpreport

Network · data from 2026-11-12

AS47119 VL-Telecom Ltd

Registry name: VLTELECOM JSC "Ufanet", RU · PeeringDB

22IPv4 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
74Route objects not announced registered with origin AS47119, seen from no peer

Announced routes

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

79.174.32.0/19 Valid RIR databaseRIPE 673 100% 66
79.174.32.0/20 Valid RIR databaseRIPE 673 100% 66
79.174.32.0/22 Valid RIR databaseRIPE 673 100% 66
79.174.40.0/22 Valid RIR databaseRIPE 673 100% 66
79.174.44.0/22 Valid RIR databaseRIPE 673 100% 66
79.174.48.0/20 Valid RIR databaseRIPE 673 100% 66
79.174.48.0/22 Valid RIR databaseRIPE 673 100% 66
79.174.50.0/24 Valid RIR databaseRIPE 673 100% 66
79.174.56.0/22 Valid RIR databaseRIPE 673 100% 66
79.174.60.0/22 Valid RIR databaseRIPE 673 100% 66
136.169.220.0/22 Valid RIR databaseRIPE 673 100% 66
188.191.112.0/20 Valid RIR databaseRIPE 673 100% 66
188.191.112.0/21 Valid RIR databaseRIPE 673 100% 66
188.191.112.0/22 Valid RIR databaseRIPE 673 100% 66
188.191.116.0/22 Valid RIR databaseRIPE 673 100% 66
188.191.120.0/22 Valid RIR databaseRIPE 673 100% 66
188.191.124.0/22 Valid RIR databaseRIPE 673 100% 66
79.174.47.0/24 Valid RIR databaseRIPE 671 100% 66
79.174.63.0/24 Valid RIR databaseRIPE 671 100% 66
136.169.220.0/24 Valid RIR databaseRIPE 671 100% 66
188.191.121.0/24 Valid RIR databaseRIPE 671 100% 66
188.191.126.0/23 Valid RIR databaseRIPE 671 100% 66

AS-SET

AS47119'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 74 are in fix.csv.

  • Route object: not announced74

Route objects not announced

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

79.174.32.0/23RIPEValid
79.174.32.0/24RIPEValid
79.174.33.0/24RIPEValid
79.174.34.0/23RIPEValid
79.174.34.0/24RIPEValid
79.174.35.0/24RIPEValid
79.174.36.0/22RIPEInvalid: maxLength
79.174.36.0/23RIPEValid
79.174.36.0/24RIPEValid
79.174.37.0/24RIPEValid
79.174.38.0/23RIPEValid
79.174.38.0/24RIPEValid
79.174.39.0/24RIPEValid
79.174.40.0/23RIPEValid
79.174.40.0/24RIPEValid
79.174.41.0/24RIPEValid
79.174.42.0/23RIPEValid
79.174.42.0/24RIPEValid
79.174.43.0/24RIPEValid
79.174.44.0/23RIPEValid
79.174.44.0/24RIPEValid
79.174.45.0/24RIPEValid
79.174.46.0/23RIPEValid
79.174.46.0/24RIPEValid
79.174.48.0/23RIPEValid
79.174.48.0/24RIPEValid
79.174.49.0/24RIPEValid
79.174.50.0/23RIPEValid
79.174.51.0/24RIPEValid
79.174.52.0/22RIPEInvalid: maxLength
79.174.52.0/23RIPEValid
79.174.52.0/24RIPEValid
79.174.53.0/24RIPEValid
79.174.54.0/23RIPEValid
79.174.54.0/24RIPEValid
79.174.55.0/24RIPEValid
79.174.56.0/23RIPEValid
79.174.56.0/24RIPEValid
79.174.57.0/24RIPEValid
79.174.58.0/23RIPEValid
79.174.58.0/24RIPEValid
79.174.59.0/24RIPEValid
79.174.60.0/23RIPEValid
79.174.60.0/24RIPEValid
79.174.61.0/24RIPEValid
79.174.62.0/23RIPEValid
79.174.62.0/24RIPEValid
136.169.220.0/23RIPEValid
136.169.221.0/24RIPEValid
136.169.222.0/23RIPEValid
136.169.222.0/24RIPEValid
136.169.223.0/24RIPEValid
188.191.112.0/23RIPEValid
188.191.112.0/24RIPEValid
188.191.113.0/24RIPEValid
188.191.114.0/23RIPEValid
188.191.114.0/24RIPEValid
188.191.115.0/24RIPEValid
188.191.116.0/23RIPEValid
188.191.116.0/24RIPEValid
188.191.117.0/24RIPEValid
188.191.118.0/23RIPEValid
188.191.118.0/24RIPEValid
188.191.119.0/24RIPEValid
188.191.120.0/23RIPEValid
188.191.120.0/24RIPEValid
188.191.122.0/23RIPEValid
188.191.122.0/24RIPEValid
188.191.123.0/24RIPEValid
188.191.124.0/23RIPEValid
188.191.124.0/24RIPEValid
188.191.125.0/24RIPEInvalid: maxLength
188.191.126.0/24RIPEValid
188.191.127.0/24RIPEInvalid: maxLength

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.