bgpreport

Network · data from 2026-11-12

AS197225 Airnet UAB "Airnet TV"

Registry name: Airnet UAB "Airnet TV", LT · not in PeeringDB

4IPv4 routes 50.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
2No 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 AS197225, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS197225, 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.
78.31.224.0/21 No ROA RIR databaseRIPE 671 100% 68
94.232.120.0/21 No ROA RIR databaseRIPE 671 100% 68
77.90.103.0/24 Valid RIR databaseRIPE 671 100% 68
77.90.92.0/24 Valid RIR databaseRIPE 102 15% 38

AS-SET

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

  • ROA: none2
ChangePrefix or setDetailFull-table peers
ROA: none78.31.224.0/21No ROA covers it. Add a ROA for AS197225, maxLength 21.671 of 673
ROA: none94.232.120.0/21No ROA covers it. Add a ROA for AS197225, maxLength 21.671 of 673

Route objects not announced

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