bgpreport

Network · data from 2026-11-12

AS51740 NetPoint

Registry name: ASZZZING NetPoint Ltd., RU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS51740, 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.
176.120.27.0/24 No ROA Nonecovered by 176.120.24.0/21 17 3%low visibility 10
176.120.28.0/23 No ROA Nonecovered by 176.120.24.0/21 17 3%low visibility 10
176.120.24.0/21 No ROA RIR databaseRIPE 673 100% 66
2001:67c:20dc::/48 No ROA RIR databaseRIPE 636 100% 67
176.120.24.0/24 No ROA RIR databaseRIPE 17 3%low visibility 10
176.120.26.0/24 No ROA RIR databaseRIPE 17 3%low visibility 10

AS-SET

AS51740'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 9 are in fix.csv.

  • ROA: none6
  • Route object: none2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none176.120.27.0/24No ROA covers it. Add a ROA for AS51740, maxLength 24.17 of 673
Route object: none176.120.27.0/24No route object for it. A route object for 176.120.24.0/21 with origin AS51740 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51740 in the RIR database for the space.17 of 673
ROA: none176.120.28.0/23No ROA covers it. Add a ROA for AS51740, maxLength 23.17 of 673
Route object: none176.120.28.0/23No route object for it. A route object for 176.120.24.0/21 with origin AS51740 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51740 in the RIR database for the space.17 of 673
ROA: none176.120.24.0/21No ROA covers it. Add a ROA for AS51740, maxLength 21.673 of 673
ROA: none2001:67c:20dc::/48No ROA covers it. Add a ROA for AS51740, maxLength 48.636 of 636
ROA: none176.120.24.0/24No ROA covers it. Add a ROA for AS51740, maxLength 24.17 of 673
ROA: none176.120.26.0/24No ROA covers it. Add a ROA for AS51740, maxLength 24.17 of 673

Route objects not announced

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

176.120.25.0/24RIPENo 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.