bgpreport

Network · data from 2026-11-12

AS59611 GIG@NET Internet w Twoim Domu P. Jastrzebski

Registry name: GIGANET-AS INTERKAM sp. z o.o., PL · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS59611, 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.245.83.203/32 Invalid: maxLength Nonecovered by 91.245.80.0/21 2 0%low visibility 6
91.245.84.153/32 Invalid: maxLength Nonecovered by 91.245.80.0/21 2 0%low visibility 6
91.245.84.173/32 Invalid: maxLength Nonecovered by 91.245.80.0/21 2 0%low visibility 6
91.245.85.15/32 Invalid: maxLength Nonecovered by 91.245.80.0/21 2 0%low visibility 6
91.245.86.208/32 Invalid: maxLength Nonecovered by 91.245.80.0/21 2 0%low visibility 6
195.20.200.0/32 Invalid: maxLength Nonecovered by 195.20.200.0/23 2 0%low visibility 6
195.20.200.73/32 Invalid: maxLength Nonecovered by 195.20.200.0/23 2 0%low visibility 6
195.20.201.0/32 Invalid: maxLength Nonecovered by 195.20.200.0/23 2 0%low visibility 6
91.245.80.0/21 Valid RIR databaseRIPE 671 100% 67
195.20.200.0/23 Valid RIR databaseRIPE 671 100% 67

AS-SET

AS59611'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 18 are in fix.csv.

  • ROA: maxLength8
  • Route object: none8
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: maxLength91.245.83.203/32ROA 91.245.80.0/21 AS59611 has maxLength 21; the route is a /32. Raise the maxLength, or add a ROA for 91.245.83.203/32.2 of 673
Route object: none91.245.83.203/32No route object for it. A route object for 91.245.80.0/21 with origin AS59611 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS59611 in the RIR database for the space.2 of 673
ROA: maxLength91.245.84.153/32ROA 91.245.80.0/21 AS59611 has maxLength 21; the route is a /32. Raise the maxLength, or add a ROA for 91.245.84.153/32.2 of 673
Route object: none91.245.84.153/32No route object for it. A route object for 91.245.80.0/21 with origin AS59611 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS59611 in the RIR database for the space.2 of 673
ROA: maxLength91.245.84.173/32ROA 91.245.80.0/21 AS59611 has maxLength 21; the route is a /32. Raise the maxLength, or add a ROA for 91.245.84.173/32.2 of 673
Route object: none91.245.84.173/32No route object for it. A route object for 91.245.80.0/21 with origin AS59611 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS59611 in the RIR database for the space.2 of 673
ROA: maxLength91.245.85.15/32ROA 91.245.80.0/21 AS59611 has maxLength 21; the route is a /32. Raise the maxLength, or add a ROA for 91.245.85.15/32.2 of 673
Route object: none91.245.85.15/32No route object for it. A route object for 91.245.80.0/21 with origin AS59611 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS59611 in the RIR database for the space.2 of 673
ROA: maxLength91.245.86.208/32ROA 91.245.80.0/21 AS59611 has maxLength 21; the route is a /32. Raise the maxLength, or add a ROA for 91.245.86.208/32.2 of 673
Route object: none91.245.86.208/32No route object for it. A route object for 91.245.80.0/21 with origin AS59611 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS59611 in the RIR database for the space.2 of 673
ROA: maxLength195.20.200.0/32ROA 195.20.200.0/23 AS59611 has maxLength 23; the route is a /32. Raise the maxLength, or add a ROA for 195.20.200.0/32.2 of 673
Route object: none195.20.200.0/32No route object for it. A route object for 195.20.200.0/23 with origin AS59611 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS59611 in the RIR database for the space.2 of 673
ROA: maxLength195.20.200.73/32ROA 195.20.200.0/23 AS59611 has maxLength 23; the route is a /32. Raise the maxLength, or add a ROA for 195.20.200.73/32.2 of 673
Route object: none195.20.200.73/32No route object for it. A route object for 195.20.200.0/23 with origin AS59611 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS59611 in the RIR database for the space.2 of 673
ROA: maxLength195.20.201.0/32ROA 195.20.200.0/23 AS59611 has maxLength 23; the route is a /32. Raise the maxLength, or add a ROA for 195.20.201.0/32.2 of 673
Route object: none195.20.201.0/32No route object for it. A route object for 195.20.200.0/23 with origin AS59611 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS59611 in the RIR database for the space.2 of 673

Route objects not announced

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

195.20.201.224/27RIPEInvalid: maxLength
2a10:f781:10:f5bc::/64RIPENo 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.