AS56696 ASLIQUID-MPLS Liquid Telecommunications Ltd

🇬🇧

Org handle: ORG-ESSL1-RIPE

RIPE NCCallocated

Announced Prefixes (BGP)

21total

21 IPv40 IPv6

IPv4 Addresses

Allocated (RIR)1,024

Announced (BGP)5,376

IPv6 Addresses

Allocated (RIR)0

Announced (BGP)0

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

RIR

Status

allocated

Allocated

2011-04-28

Announced Prefixes

(BGP)21

Prefix	RPKI	IRR	Last Seen
41.60.53.0/24	No ROA	-	2026-10-10
77.246.48.0/24	Valid	-	2026-10-10
77.246.49.0/24	Valid	-	2026-10-10
77.246.50.0/24	Valid	-	2026-10-10
77.246.51.0/24	Valid	-	2026-10-10
77.246.52.0/24	Valid	-	2026-10-10
77.246.53.0/24	Valid	-	2026-10-10
77.246.54.0/24	Valid	-	2026-10-10
77.246.55.0/24	Valid	-	2026-10-10
197.221.253.0/24MOAS	Invalid	-	2026-10-10

1-10 of 21

1 / 3

(RIR)4

Prefix	Country	RIR	Status
217.15.117.0/24	🇿🇼 ZW	RIPE	assigned
217.15.123.0/24	🇿🇼 ZW	RIPE	assigned
217.74.224.0/24	🇿🇼 ZW	RIPE	assigned
217.74.225.0/24	🇱🇸 LS	RIPE	assigned

(seen in AS paths)

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

ASPA

No ASPA

Abuse Contact

External Links

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 AS56696 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

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

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