bgpreport

Network · data from 2026-11-12

AS50864 IT TeleNet

Registry name: TeleNet-AS IT TeleNet Ltd., UA · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS50864, 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.220.235.0/24 Valid RIR databaseRIPE 671 100% 68
185.160.88.0/24 Valid RIR databaseRIPE 671 100% 68
185.160.89.0/24 Valid RIR databaseRIPE 671 100% 68
195.162.88.0/22 Valid RIR databaseRIPE 671 100% 68
195.162.88.0/24 Valid RIR databaseRIPE 671 100% 68
195.162.89.0/24 Valid RIR databaseRIPE 671 100% 68
195.162.90.0/24 Valid RIR databaseRIPE 671 100% 68
195.162.91.0/24 Valid RIR databaseRIPE 671 100% 68
2a07:bbc2::/48 Valid RIR databaseRIPE 635 100% 69
2a07:bbc2:1::/48 Valid RIR databaseRIPE 635 100% 69
185.160.91.0/24 Valid RIR databaseRIPE 3 0%low visibility 3

AS-SET

AS50864's PeeringDB record names no AS-SET.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

Every route object with origin AS50864 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.