bgpreport

Network · data from 2026-11-12

AS35645 INFOCENTER Limited Liability Company "VLADINFO"

Registry name: INFOCENTER Limited Liability Company "VLADINFO", RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS35645, 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.
193.232.204.0/23 No ROA RIR databaseRIPE 670 100% 66
194.190.210.0/23 No ROA RIR databaseRIPE 670 100% 66
194.85.235.0/24 Valid Nonecovered by 194.85.232.0/22 673 100% 66
62.76.212.0/22 Valid RIR databaseRIPE 673 100% 66
95.66.128.0/19 Valid RIR databaseRIPE 673 100% 66
95.66.160.0/19 Valid RIR databaseRIPE 673 100% 66
95.66.192.0/22 Valid RIR databaseRIPE 673 100% 66
95.66.196.0/23 Valid RIR databaseRIPE 673 100% 66
95.66.200.0/23 Valid RIR databaseRIPE 673 100% 66
95.66.202.0/23 Valid RIR databaseRIPE 673 100% 66
95.66.204.0/23 Valid RIR databaseRIPE 673 100% 66
95.66.206.0/23 Valid RIR databaseRIPE 673 100% 66
95.66.208.0/22 Valid RIR databaseRIPE 673 100% 66
95.66.212.0/22 Valid RIR databaseRIPE 673 100% 66
95.66.216.0/22 Valid RIR databaseRIPE 673 100% 66
95.66.220.0/23 Valid RIR databaseRIPE 673 100% 66
95.66.222.0/23 Valid RIR databaseRIPE 673 100% 66
95.66.224.0/23 Valid RIR databaseRIPE 673 100% 66
95.66.227.0/24 Valid RIR databaseRIPE 673 100% 66
95.66.228.0/23 Valid RIR databaseRIPE 673 100% 66
95.66.230.0/23 Valid RIR databaseRIPE 673 100% 66
95.66.237.0/24 Valid RIR databaseRIPE 673 100% 66
95.66.238.0/23 Valid RIR databaseRIPE 673 100% 66
95.66.240.0/22 Valid RIR databaseRIPE 673 100% 66
95.66.244.0/24 Valid RIR databaseRIPE 673 100% 66
95.66.245.0/24 Valid RIR databaseRIPE 673 100% 66
95.66.246.0/23 Valid RIR databaseRIPE 673 100% 66
95.66.248.0/23 Valid RIR databaseRIPE 673 100% 66
95.66.250.0/23 Valid RIR databaseRIPE 673 100% 66
95.66.252.0/23 Valid RIR databaseRIPE 673 100% 66
95.66.254.0/23 Valid RIR databaseRIPE 673 100% 66
193.232.8.0/24 Valid RIR databaseRIPE 673 100% 66
194.85.202.0/23 Valid RIR databaseRIPE 673 100% 66
194.85.204.0/23 Valid RIR databaseRIPE 673 100% 66
194.85.232.0/22 Valid RIR databaseRIPE 673 100% 66
194.190.90.0/23 Valid RIR databaseRIPE 673 100% 66

AS-SET

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

  • ROA: none2
  • Route object: none1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none193.232.204.0/23No ROA covers it. Add a ROA for AS35645, maxLength 23.670 of 673
ROA: none194.190.210.0/23No ROA covers it. Add a ROA for AS35645, maxLength 23.670 of 673
Route object: none194.85.235.0/24No route object for it. A route object for 194.85.232.0/22 with origin AS35645 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35645 in the RIR database for the space.673 of 673

Route objects not announced

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

95.66.128.0/18RIPENo ROA
95.66.188.0/24RIPEInvalid: maxLength
95.66.192.0/20RIPENo ROA
95.66.208.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.