bgpreport

Network · data from 2026-11-12

AS38972 INTERSAT-AS Suhoy Log Intersat Ltd.

Registry name: INTERSAT-AS Suhoy Log Intersat Ltd., RU · not in PeeringDB

3IPv4 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
13Route objects not announced registered with origin AS38972, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS38972, 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.
46.254.24.0/22 Valid RIR databaseRIPE 672 100% 66
80.251.144.0/21 Valid RIR databaseRIPE 672 100% 66
80.251.154.0/24 Valid RIR databaseRIPE 672 100% 66

AS-SET

AS38972 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 13 are in fix.csv.

  • Route object: not announced13

Route objects not announced

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

46.254.24.0/24RIPEValid
46.254.25.0/24RIPEValid
46.254.26.0/24RIPEValid
46.254.27.0/24RIPEValid
80.251.144.0/24RIPEInvalid: maxLength
80.251.145.0/24RIPEInvalid: maxLength
80.251.146.0/24RIPEInvalid: maxLength
80.251.147.0/24RIPEValid
80.251.148.0/24RIPEInvalid: maxLength
80.251.149.0/24RIPEInvalid: maxLength
80.251.150.0/24RIPEValid
80.251.151.0/24RIPEInvalid: maxLength
2a0a:3040::/29RIPENo 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.