Home ASN LookupAS8264

AS8264 MARLINK-SK Marlink AS

🇳🇴

Org handle: ORG-MEA38-RIPE

RIPE NCCallocated

Announced Prefixes (BGP)

3total

2 IPv41 IPv6

IPv4 Addresses

Allocated (RIR)40,960

Announced (BGP)40,960

IPv6 Addresses

Allocated (RIR)6.3×10²⁹

Announced (BGP)6.3×10²⁹

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

🇳🇴 NO

RIR

RIPE NCC

Status

allocated

Allocated

1997-04-09

Announced Prefixes

(BGP)3

Prefix	RPKI	IRR	Last Seen
195.20.160.0/19	Valid	RIPE	2026-10-10
212.197.0.0/17	Valid	RIPE	2026-10-10
2a00:ff80::/29	Valid	RIPE	2026-10-10

Allocated Prefixes

(RIR)3

Prefix	Country	RIR	Status
195.20.160.0/19	🇳🇴 NO	RIPENCC	allocated
212.197.0.0/17	🇳🇴 NO	RIPENCC	allocated
2a00:ff80::/29	🇳🇴 NO	RIPENCC	allocated

All 3 announced prefixes of AS8264 →

BGP Neighbours

(seen in AS paths)

Upstreams (2)

Networks AS8264 hands its own prefixes to: transit providers, or peers at an exchange.

AS29405VNET A.S2
AS5578BENESTRA SWAN, A.S1

Transfer History

Registry transfers of AS8264 between organisations.

AS8264M&A · 2018-10-19
Marlink Enterprise AS
RIPE NCC
→
Marlink AS
RIPE NCC
AS8264Transfer · 2016-09-23
Astrium Services Enterprises AS
RIPE NCC
→
Marlink Enterprise AS
RIPE NCC

Date	Resource	From	To	Type
2018-10-19	AS8264	Marlink Enterprise AS RIPE NCC	Marlink AS RIPE NCC	M&A
2016-09-23	AS8264	Astrium Services Enterprises AS RIPE NCC	Marlink Enterprise AS RIPE NCC	Transfer

ASPA

No ASPA

Abuse Contact

External Links

RIPE Whois RIPEstat

Learn more

What is an ASN?Autonomous systems, ASN ranges and how they are assigned
RPKI and route origin validationWhat the RPKI badges on the prefix list mean
ASPA explainedWhy AS8264 should publish an ASPA object
IPv4 transfers in the RIPE NCC regionMonthly volume and the latest registry transfers
ASN data in AI agents and SIEMMCP server and API integrations

API

Open

GEThttps://api.ipctl.io/v1/asn/8264

Returns ASN details, announced prefixes, and BGP routing data.

curl -s "https://api.ipctl.io/v1/asn/8264" | jq