bgpreport

Network · data from 2026-11-12

AS56707 NETCOM OOO NETCOM

Registry name: NETCOM OOO NETCOM, RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS56707, 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.
31.211.44.0/22 No ROA RIR databaseRIPE 2 0%low visibility 2
31.211.61.0/24 No ROA RIR databaseRIPE 2 0%low visibility 2
31.211.64.0/21 No ROA RIR databaseRIPE 2 0%low visibility 2
31.211.72.0/24 No ROA RIR databaseRIPE 2 0%low visibility 2
31.211.76.0/22 No ROA RIR databaseRIPE 2 0%low visibility 2
31.211.80.0/21 No ROA RIR databaseRIPE 2 0%low visibility 2
46.166.240.0/21 Valid RIR databaseRIPE 673 100% 66
193.232.40.0/22 Valid RIR databaseRIPE 673 100% 66
193.232.46.0/24 Valid RIR databaseRIPE 673 100% 66
193.232.49.0/24 Valid RIR databaseRIPE 673 100% 66
193.232.92.0/24 Valid RIR databaseRIPE 673 100% 66
193.232.107.0/24 Valid RIR databaseRIPE 673 100% 66
193.232.110.0/24 Valid RIR databaseRIPE 673 100% 66
193.232.165.0/24 Valid RIR databaseRIPE 673 100% 66
195.208.160.0/22 Valid RIR databaseRIPE 673 100% 66
212.107.240.0/21 Valid RIR databaseRIPE 673 100% 66
212.192.195.0/24 Valid RIR databaseRIPE 673 100% 66
212.192.196.0/22 Valid RIR databaseRIPE 673 100% 66
212.192.200.0/23 Valid RIR databaseRIPE 673 100% 66

AS-SET

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

  • ROA: none6
  • Route object: not announced19
ChangePrefix or setDetailFull-table peers
ROA: none31.211.44.0/22No ROA covers it. Add a ROA for AS56707, maxLength 22.2 of 673
ROA: none31.211.61.0/24No ROA covers it. Add a ROA for AS56707, maxLength 24.2 of 673
ROA: none31.211.64.0/21No ROA covers it. Add a ROA for AS56707, maxLength 21.2 of 673
ROA: none31.211.72.0/24No ROA covers it. Add a ROA for AS56707, maxLength 24.2 of 673
ROA: none31.211.76.0/22No ROA covers it. Add a ROA for AS56707, maxLength 22.2 of 673
ROA: none31.211.80.0/21No ROA covers it. Add a ROA for AS56707, maxLength 21.2 of 673

Route objects not announced

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

31.211.64.0/23RIPENo ROA
31.211.66.0/23RIPENo ROA
31.211.68.0/22RIPENo ROA
46.166.240.0/24RIPEValid
46.166.241.0/24RIPEValid
46.166.242.0/24RIPEValid
46.166.243.0/24RIPEValid
46.166.244.0/24RIPEValid
46.166.245.0/24RIPEValid
46.166.246.0/24RIPEValid
46.166.247.0/24RIPEValid
212.107.240.0/24RIPEValid
212.107.241.0/24RIPEValid
212.107.242.0/24RIPEValid
212.107.243.0/24RIPEValid
212.107.244.0/24RIPEValid
212.107.245.0/24RIPEValid
212.107.246.0/24RIPEValid
212.107.247.0/24RIPEValid

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.