Home ASN LookupAS35773

AS35773 ICONNECT-AS iConnect Ltd.

🇧🇬

Org handle: ORG-iL50-RIPE

Pazardjik, Bulgaria

RIPE NCCallocated

Announced Prefixes (BGP)

6total

5 IPv41 IPv6

IPv4 Addresses

Allocated (RIR)2,560

Announced (BGP)3,072

IPv6 Addresses

Allocated (RIR)6.3×10²⁹

Announced (BGP)6.3×10²⁹

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

🇧🇬 BG

RIR

RIPE NCC

Status

allocated

Allocated

2005-10-24

Announced Prefixes

(BGP)6

Prefix	RPKI	IRR	Last Seen
46.245.237.0/24	Valid	RIPE	2026-10-11
84.54.148.0/24	Valid	RIPE	2026-10-11
84.54.150.0/24	Valid	RIPE	2026-10-11
109.160.112.0/24	Valid	RIPE	2026-10-11
195.214.248.0/21	Valid	RIPE	2026-10-11
2a13:d880::/29	Valid	RIPE	2026-10-11

Allocated Prefixes

(RIR)4

Prefix	Country	RIR	Status
46.245.237.0/24	🇧🇬 BG	RIPENCC	allocated
109.160.112.0/24	🇧🇬 BG	RIPE	assigned
195.214.248.0/21	🇧🇬 BG	RIPENCC	assigned
2a13:d880::/29	🇧🇬 BG	RIPENCC	allocated

All 6 announced prefixes of AS35773 →

BGP Neighbours

(seen in AS paths)

Upstreams (2)

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

AS12615GCN Global Communication Net Plc3
AS61071NETBOX3

Downstreams (1)

Networks whose own prefixes AS35773 passes on: usually its customers.

AS49773DEIMOS1

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 AS35773 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/35773

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

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