bgpreport

Network · data from 2026-11-12

AS216446 Insatel Sp. z o.o.

Registry name: INSATEL-AS Insatel Sp. z o.o., PL · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS216446, 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.
195.136.17.0/24 Invalid: maxLength RIR databaseRIPE 9 1%low visibility 11
195.136.16.0/23 Valid RIR databaseRIPE 671 100% 68

AS-SET

AS216446'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 2 are in fix.csv.

  • ROA: maxLength1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: maxLength195.136.17.0/24ROA 195.136.16.0/23 AS216446 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 195.136.17.0/24.9 of 673

Route objects not announced

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

195.136.16.0/24RIPEInvalid: maxLength

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.