bgpreport

Network · data from 2026-11-12

AS209980 Marlink-EU-OMNIACCESS Marlink AS

Registry name: Marlink-EU-OMNIACCESS Marlink AS, NO · not in PeeringDB

6IPv4 routes 66.7% 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
3Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS209980, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS209980, 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.
154.62.77.0/24 No ROA Other IRR onlyRADB 19 3%low visibility 13
154.58.196.0/24 No ROA Other IRR onlyRADB 18 3%low visibility 13
89.185.140.0/24 Valid RIR databaseRIPE 671 100% 68
193.220.160.0/24 Valid RIR databaseRIPE 671 100% 68
193.220.161.0/24 Valid RIR databaseRIPE 671 100% 68
92.43.224.0/21 Valid RIR databaseRIPE 16 2%low visibility 12

AS-SET

AS209980 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 5 are in fix.csv.

  • ROA: none2
  • Route object: RIR2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none154.62.77.0/24No ROA covers it. Add a ROA for AS209980, maxLength 24.19 of 673
Route object: RIR154.62.77.0/24Route object only in RADB. Add it in the RIR database for the space.19 of 673
ROA: none154.58.196.0/24No ROA covers it. Add a ROA for AS209980, maxLength 24.18 of 673
Route object: RIR154.58.196.0/24Route object only in RADB. Add it in the RIR database for the space.18 of 673

Route objects not announced

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

193.220.160.0/23RIPEInvalid: origin

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.