AS41103 CLEARIP-AS teleBIZZ Ltd

🇬🇧

Org handle: ORG-TL327-RIPE

teleBIZZ Ltd

RIPE NCCallocated

Announced Prefixes (BGP)

4total

2 IPv42 IPv6

IPv4 Addresses

Allocated (RIR)1,576

Announced (BGP)1,280

IPv6 Addresses

Allocated (RIR)7.9×10²⁸

Announced (BGP)7.9×10²⁸

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

RIR

Status

allocated

Allocated

2006-06-15

Announced Prefixes

(BGP)4

Prefix	RPKI	IRR	Last Seen
185.91.100.0/22	Valid	RIPE	2026-10-11
195.95.187.0/24	Valid	RIPE	2026-10-11
2001:67c:15f4::/48	Valid	RIPE	2026-10-11
2a03:8920::/32	Valid	RIPE	2026-10-11

(RIR)8

Prefix	Country	RIR	Status
185.91.100.0/22	🇬🇧 GB	RIPENCC	allocated
185.91.102.0/27	🇬🇧 GB	RIPE	assigned
185.91.102.48/29	🇬🇧 GB	RIPE	assigned
185.91.103.0/25	🇬🇧 GB	RIPE	assigned
185.91.103.128/25	🇬🇧 GB	RIPE	assigned
195.95.187.0/24	🇬🇧 GB	RIPENCC	assigned
2001:67c:15f4::/48	🇬🇧 GB	RIPENCC	assigned
2a03:8920::/32	🇬🇧 GB	RIPENCC	allocated

(seen in AS paths)

Networks AS41103 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 AS41103 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/41103" | jq