bgpreport

Network · data from 2026-11-12

AS41957 GLOBALTE-AS Directive LLC

Registry name: GLOBALTE-AS Directive LLC, RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS41957, 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.
45.86.169.0/24 Valid RIR databaseRIPE 673 100% 66
46.16.37.0/24 Valid RIR databaseRIPE 673 100% 66
46.253.128.0/24 Valid RIR databaseRIPE 673 100% 66
62.3.48.0/24 Valid RIR databaseRIPE 673 100% 66
77.83.94.0/24 Valid RIR databaseRIPE 673 100% 66
85.209.10.0/24 Valid RIR databaseRIPE 673 100% 66
91.242.254.0/24 Valid RIR databaseRIPE 673 100% 66
146.19.178.0/24 Valid RIR databaseRIPE 673 100% 66
146.19.180.0/24 Valid RIR databaseRIPE 673 100% 66
176.56.34.0/24 Valid RIR databaseRIPE 673 100% 66
185.21.141.0/24 Valid RIR databaseRIPE 673 100% 66
185.191.213.0/24 Valid RIR databaseRIPE 673 100% 66
193.42.114.0/24 Valid RIR databaseRIPE 673 100% 66
194.93.59.0/24 Valid RIR databaseRIPE 673 100% 66
194.147.89.0/24 Valid RIR databaseRIPE 673 100% 66
195.114.117.0/24 Valid RIR databaseRIPE 673 100% 66
195.245.238.0/24 Valid RIR databaseRIPE 673 100% 66
213.109.108.0/24 Valid RIR databaseRIPE 673 100% 66

AS-SET

AS41957 isn't in PeeringDB, where networks name their 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 AS41957 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.