bgpreport

Network · data from 2026-11-12

AS51792 GIGAINTERNET

Registry name: GIGA-AS GIGAINTERNET Sp z o.o., PL · PeeringDB

25IPv4 routes 72.0% RPKI valid · 72.0% with a route object
0IPv6 routes
7RPKI invalid 0 origin · 7 maxLength
0No ROA 7 with no route object for this origin
7Low visibility seen by under 10% of full-table peers
16Route objects not announced registered with origin AS51792, seen from no peer

Announced routes

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

91.123.176.253/32 Invalid: maxLength Nonecovered by 91.123.176.0/24 3 0%low visibility 6
91.123.181.200/32 Invalid: maxLength Nonecovered by 91.123.181.0/24 3 0%low visibility 6
91.123.188.0/32 Invalid: maxLength Nonecovered by 91.123.188.0/24 3 0%low visibility 6
91.123.188.205/32 Invalid: maxLength Nonecovered by 91.123.188.0/24 3 0%low visibility 6
91.123.188.246/32 Invalid: maxLength Nonecovered by 91.123.188.0/24 3 0%low visibility 6
91.123.191.216/32 Invalid: maxLength Nonecovered by 91.123.191.0/24 3 0%low visibility 6
91.123.191.222/32 Invalid: maxLength Nonecovered by 91.123.191.0/24 3 0%low visibility 6
83.175.128.0/21 Valid RIR databaseRIPE 671 100% 68
83.175.140.0/23 Valid RIR databaseRIPE 671 100% 68
91.123.176.0/20 Valid RIR databaseRIPE 671 100% 68
91.123.184.0/24 Valid RIR databaseRIPE 671 100% 68
91.219.112.0/22 Valid RIR databaseRIPE 671 100% 68
91.219.112.0/24 Valid RIR databaseRIPE 671 100% 68
91.219.113.0/24 Valid RIR databaseRIPE 671 100% 68
91.219.114.0/24 Valid RIR databaseRIPE 671 100% 68
91.219.115.0/24 Valid RIR databaseRIPE 671 100% 68
91.123.182.0/24 Valid RIR databaseRIPE 137 20% 45
91.123.183.0/24 Valid RIR databaseRIPE 137 20% 45
91.123.188.0/24 Valid RIR databaseRIPE 137 20% 45
91.123.189.0/24 Valid RIR databaseRIPE 115 17% 44
91.123.191.0/24 Valid RIR databaseRIPE 115 17% 44
91.123.181.0/24 Valid RIR databaseRIPE 97 14% 40
91.123.178.0/24 Valid RIR databaseRIPE 78 12% 36
91.123.180.0/24 Valid RIR databaseRIPE 78 12% 36
91.123.185.0/24 Valid RIR databaseRIPE 78 12% 36

AS-SET

AS51792'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 30 are in fix.csv.

  • ROA: maxLength7
  • Route object: none7
  • Route object: not announced16
ChangePrefix or setDetailFull-table peers
ROA: maxLength91.123.176.253/32ROA 91.123.176.0/20 AS51792 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 91.123.176.253/32.3 of 673
Route object: none91.123.176.253/32No route object for it. A route object for 91.123.176.0/24 with origin AS51792 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS51792 in the RIR database for the space.3 of 673
ROA: maxLength91.123.181.200/32ROA 91.123.176.0/20 AS51792 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 91.123.181.200/32.3 of 673
Route object: none91.123.181.200/32No route object for it. A route object for 91.123.181.0/24 with origin AS51792 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS51792 in the RIR database for the space.3 of 673
ROA: maxLength91.123.188.0/32ROA 91.123.176.0/20 AS51792 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 91.123.188.0/32.3 of 673
Route object: none91.123.188.0/32No route object for it. A route object for 91.123.188.0/24 with origin AS51792 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS51792 in the RIR database for the space.3 of 673
ROA: maxLength91.123.188.205/32ROA 91.123.176.0/20 AS51792 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 91.123.188.205/32.3 of 673
Route object: none91.123.188.205/32No route object for it. A route object for 91.123.188.0/24 with origin AS51792 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS51792 in the RIR database for the space.3 of 673
ROA: maxLength91.123.188.246/32ROA 91.123.176.0/20 AS51792 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 91.123.188.246/32.3 of 673
Route object: none91.123.188.246/32No route object for it. A route object for 91.123.188.0/24 with origin AS51792 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS51792 in the RIR database for the space.3 of 673
ROA: maxLength91.123.191.216/32ROA 91.123.176.0/20 AS51792 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 91.123.191.216/32.3 of 673
Route object: none91.123.191.216/32No route object for it. A route object for 91.123.191.0/24 with origin AS51792 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS51792 in the RIR database for the space.3 of 673
ROA: maxLength91.123.191.222/32ROA 91.123.176.0/20 AS51792 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 91.123.191.222/32.3 of 673
Route object: none91.123.191.222/32No route object for it. A route object for 91.123.191.0/24 with origin AS51792 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS51792 in the RIR database for the space.3 of 673

Route objects not announced

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

83.175.128.0/24RIPEValid
83.175.129.0/24RIPEValid
83.175.130.0/24RIPEValid
83.175.131.0/24RIPEValid
83.175.132.0/24RIPEValid
83.175.133.0/24RIPEValid
83.175.134.0/24RIPEValid
83.175.135.0/24RIPEValid
83.175.140.0/24RIPEValid
83.175.141.0/24RIPEValid
91.123.176.0/24RIPEValid
91.123.177.0/24RIPEValid
91.123.179.0/24RIPEValid
91.123.186.0/24RIPEValid
91.123.187.0/24RIPEValid
91.123.190.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.