Home ASN LookupAS59611

AS59611 GIGANET-AS INTERKAM sp. z o.o.

🇵🇱

Org handle: ORG-SZKS1-RIPE

RIPE NCCallocated

Announced Prefixes (BGP)

2total

2 IPv40 IPv6

IPv4 Addresses

Allocated (RIR)2,560

Announced (BGP)2,560

IPv6 Addresses

Allocated (RIR)0

Announced (BGP)0

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

🇵🇱 PL

RIR

RIPE NCC

Status

allocated

Allocated

2012-08-21

Announced Prefixes

(BGP)2

Prefix	RPKI	IRR	Last Seen
91.245.80.0/21	Valid	RIPE	2026-10-11
195.20.200.0/23	Valid	RIPE	2026-10-11

Allocated Prefixes

(RIR)2

Prefix	Country	RIR	Status
91.245.80.0/21	🇵🇱 PL	RIPENCC	assigned
195.20.200.0/23	🇵🇱 PL	RIPENCC	assigned

All 2 announced prefixes of AS59611 →

BGP Neighbours

(seen in AS paths)

Upstreams (2)

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

AS201054EPIX PolMix Stowarzyszenie E Poludnie8
AS50607EPIX KTW GlobalMix Stowarzyszenie E Poludnie2

Transfer History

Registry transfers of AS59611 between organisations.

AS59611M&A · 2025-11-20
GigaNet Sp. z o.o.
🇵🇱 PL RIPE NCC
→
INTERKAM sp. z o.o.
🇵🇱 PL RIPE NCC
AS59611M&A · 2024-04-18
GigaNet Pawel Jastrzebski
RIPE NCC
→
GigaNet Sp. z o.o.
RIPE NCC

Date	Resource	From	To	Type
2025-11-20	AS59611	GigaNet Sp. z o.o. 🇵🇱 PL RIPE NCC	INTERKAM sp. z o.o. 🇵🇱 PL RIPE NCC	M&A
2024-04-18	AS59611	GigaNet Pawel Jastrzebski RIPE NCC	GigaNet Sp. z o.o. RIPE NCC	M&A

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 AS59611 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/59611

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

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