bgpreport

Network · data from 2026-11-12

AS197663 POLANS POLANS, telekomunikacijske storitve d.o.o.

Registry name: POLANS POLANS, telekomunikacijske storitve d.o.o., SI · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS197663, 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.240.54.0/25 Invalid: maxLength Nonecovered by 91.240.54.0/24 2 0%low visibility 2
91.240.54.128/25 Invalid: maxLength Nonecovered by 91.240.54.0/24 2 0%low visibility 2
91.240.55.0/25 Invalid: maxLength Nonecovered by 91.240.55.0/24 2 0%low visibility 2
91.240.55.128/25 Invalid: maxLength Nonecovered by 91.240.55.0/24 2 0%low visibility 2
91.225.96.0/22 Valid RIR databaseRIPE 673 100% 66
91.240.52.0/24 Valid RIR databaseRIPE 673 100% 66
91.240.53.0/24 Valid RIR databaseRIPE 673 100% 66
91.240.54.0/24 Valid RIR databaseRIPE 673 100% 66
91.240.55.0/24 Valid RIR databaseRIPE 673 100% 66
193.35.111.0/24 Valid RIR databaseRIPE 673 100% 66
195.47.243.0/24 Valid RIR databaseRIPE 673 100% 66

AS-SET

AS197663 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 8 are in fix.csv.

  • ROA: maxLength4
  • Route object: none4
ChangePrefix or setDetailFull-table peers
ROA: maxLength91.240.54.0/25ROA 91.240.54.0/24 AS197663 has maxLength 24; the route is a /25. Raise the maxLength, or add a ROA for 91.240.54.0/25.2 of 673
Route object: none91.240.54.0/25No route object for it. A route object for 91.240.54.0/24 with origin AS197663 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS197663 in the RIR database for the space.2 of 673
ROA: maxLength91.240.54.128/25ROA 91.240.54.0/24 AS197663 has maxLength 24; the route is a /25. Raise the maxLength, or add a ROA for 91.240.54.128/25.2 of 673
Route object: none91.240.54.128/25No route object for it. A route object for 91.240.54.0/24 with origin AS197663 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS197663 in the RIR database for the space.2 of 673
ROA: maxLength91.240.55.0/25ROA 91.240.55.0/24 AS197663 has maxLength 24; the route is a /25. Raise the maxLength, or add a ROA for 91.240.55.0/25.2 of 673
Route object: none91.240.55.0/25No route object for it. A route object for 91.240.55.0/24 with origin AS197663 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS197663 in the RIR database for the space.2 of 673
ROA: maxLength91.240.55.128/25ROA 91.240.55.0/24 AS197663 has maxLength 24; the route is a /25. Raise the maxLength, or add a ROA for 91.240.55.128/25.2 of 673
Route object: none91.240.55.128/25No route object for it. A route object for 91.240.55.0/24 with origin AS197663 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS197663 in the RIR database for the space.2 of 673

Route objects not announced

Every route object with origin AS197663 is announced.

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.