bgpreport

Network · data from 2026-11-12

AS49352 LOGOL-AS "Domain names registrar REG.RU", Ltd

Registry name: LOGOL-AS "Domain names registrar REG.RU", Ltd, RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS49352, 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.
178.21.12.0/32 Invalid: maxLength Nonecovered by 178.21.12.0/24 2 0%low visibility 2
213.189.199.0/32 Invalid: maxLength Nonecovered by 213.189.199.0/24 2 0%low visibility 2
193.227.134.0/32 No ROA Nonecovered by 193.227.134.0/24 2 0%low visibility 2
193.227.134.0/24 No ROA RIR databaseRIPE 673 100% 66
176.99.5.190/32 Valid Nonecovered by 176.99.5.0/24 2 0%low visibility 2
188.93.208.172/32 Valid Nonecovered by 188.93.208.0/23 2 0%low visibility 2
188.93.209.127/32 Valid Nonecovered by 188.93.208.0/23 2 0%low visibility 2
176.99.8.0/24 Valid RIR databaseRIPE 673 100% 66
185.38.18.0/24 Valid RIR databaseRIPE 673 100% 66
188.93.213.0/24 Valid RIR databaseRIPE 673 100% 66
194.67.76.0/24 Valid RIR databaseRIPE 673 100% 66
194.67.77.0/24 Valid RIR databaseRIPE 673 100% 66
213.189.199.0/24 Valid RIR databaseRIPE 673 100% 66
176.99.4.0/24 Valid RIR databaseRIPE 672 100% 67
176.99.5.0/24 Valid RIR databaseRIPE 672 100% 67
176.99.6.0/24 Valid RIR databaseRIPE 672 100% 67
176.99.7.0/24 Valid RIR databaseRIPE 672 100% 67
176.99.9.0/24 Valid RIR databaseRIPE 672 100% 67
178.21.9.0/24 Valid RIR databaseRIPE 672 100% 67
178.21.12.0/22 Valid RIR databaseRIPE 672 100% 67
178.21.12.0/24 Valid RIR databaseRIPE 672 100% 67
178.21.13.0/24 Valid RIR databaseRIPE 672 100% 67
178.21.14.0/23 Valid RIR databaseRIPE 672 100% 67
185.38.16.0/24 Valid RIR databaseRIPE 672 100% 67
185.38.19.0/24 Valid RIR databaseRIPE 672 100% 67
188.93.208.0/23 Valid RIR databaseRIPE 672 100% 67
188.93.214.0/24 Valid RIR databaseRIPE 672 100% 67
188.93.215.0/24 Valid RIR databaseRIPE 672 100% 67
194.67.64.0/24 Valid RIR databaseRIPE 672 100% 67
194.67.76.0/23 Valid RIR databaseRIPE 672 100% 67
194.67.106.0/24 Valid RIR databaseRIPE 672 100% 67
213.189.195.0/24 Valid RIR databaseRIPE 672 100% 67
62.113.93.0/24 Valid RIR databaseRIPE 669 99% 67
194.67.75.0/24 Valid RIR databaseRIPE 96 14% 39

AS-SET

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

  • ROA: maxLength2
  • ROA: none2
  • Route object: none6
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: maxLength178.21.12.0/32ROA 178.21.12.0/22 AS49352 has maxLength 22; ROA 178.21.12.0/24 AS49352 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 178.21.12.0/32.2 of 673
Route object: none178.21.12.0/32No route object for it. A route object for 178.21.12.0/24 with origin AS49352 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS49352 in the RIR database for the space.2 of 673
ROA: maxLength213.189.199.0/32ROA 213.189.199.0/24 AS49352 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 213.189.199.0/32.2 of 673
Route object: none213.189.199.0/32No route object for it. A route object for 213.189.199.0/24 with origin AS49352 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS49352 in the RIR database for the space.2 of 673
ROA: none193.227.134.0/32No ROA covers it. Add a ROA for AS49352, maxLength 32.2 of 673
Route object: none193.227.134.0/32No route object for it. A route object for 193.227.134.0/24 with origin AS49352 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS49352 in the RIR database for the space.2 of 673
ROA: none193.227.134.0/24No ROA covers it. Add a ROA for AS49352, maxLength 24.673 of 673
Route object: none176.99.5.190/32No route object for it. A route object for 176.99.5.0/24 with origin AS49352 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS49352 in the RIR database for the space.2 of 673
Route object: none188.93.208.172/32No route object for it. A route object for 188.93.208.0/23 with origin AS49352 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS49352 in the RIR database for the space.2 of 673
Route object: none188.93.209.127/32No route object for it. A route object for 188.93.208.0/23 with origin AS49352 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS49352 in the RIR database for the space.2 of 673

Route objects not announced

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

176.99.0.0/20RIPENo ROA
178.21.8.0/21RIPENo ROA
178.21.14.0/24RIPEInvalid: maxLength
185.38.17.0/24RIPEValid
188.93.208.0/21RIPENo ROA
188.93.210.0/23RIPENo ROA
188.93.212.0/24RIPEInvalid: origin
213.189.193.0/24RIPEValid
213.189.194.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.