Home ASN LookupAS201714

AS201714 LinkIPNetworks Link IP Networks Ltd

🇬🇧

Org handle: ORG-LINL1-RIPE

RIPE NCCallocated

Announced Prefixes (BGP)

6total

6 IPv40 IPv6

IPv4 Addresses

Allocated (RIR)2,304

Announced (BGP)2,304

IPv6 Addresses

Allocated (RIR)6.3×10²⁹

Announced (BGP)0

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

🇬🇧 GB

RIR

RIPE NCC

Status

allocated

Allocated

2014-08-05

Announced Prefixes

(BGP)6

Prefix	RPKI	IRR	Last Seen
45.85.100.0/24	Valid	RIPE	2026-10-11
45.85.101.0/24	Valid	RIPE	2026-10-11
185.66.4.0/22	Valid	RIPE	2026-10-11
185.66.5.0/24	Valid	RIPE	2026-10-11
185.66.6.0/24	Valid	RIPE	2026-10-11
185.66.7.0/24	Valid	RIPE	2026-10-11

Allocated Prefixes

(RIR)4

Prefix	Country	RIR	Status
45.85.100.0/22	🇬🇧 GB	RIPENCC	allocated
45.85.100.0/24	🇬🇧 GB	RIPE	assigned
185.66.4.0/22	🇬🇧 GB	RIPENCC	allocated
2a03:1ea0::/29	🇬🇧 GB	RIPENCC	allocated

All 6 announced prefixes of AS201714 →

BGP Neighbours

(seen in AS paths)

Upstreams (2)

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

AS6939Hurricane Electric4
AS9002RETN Limited2

Transfer History

Registry transfers of AS201714 between organisations.

AS201714Transfer · 2019-05-27
Simply IP Limited
RIPE NCC
→
Link IP Networks Ltd
RIPE NCC

Date	Resource	From	To	Type
2019-05-27	AS201714	Simply IP Limited RIPE NCC	Link IP Networks Ltd 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 AS201714 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/201714

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

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