Home ASN LookupAS203667

AS203667 zipnet ZIPnet sp. z o.o.

🇵🇱

Org handle: ORG-PGTA1-RIPE

RIPE NCCallocated

Announced Prefixes (BGP)

3total

3 IPv40 IPv6

IPv4 Addresses

Allocated (RIR)3,072

Announced (BGP)5,120

IPv6 Addresses

Allocated (RIR)6.3×10²⁹

Announced (BGP)0

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

🇵🇱 PL

RIR

RIPE NCC

Status

allocated

Allocated

2018-04-19

Announced Prefixes

(BGP)3

Prefix	RPKI	IRR	Last Seen
38.41.200.0/21	Valid	ARIN	2026-10-09
155.133.40.0/21	Valid	RIPE	2026-10-09
185.233.72.0/22	Valid	RIPE	2026-10-09

Allocated Prefixes

(RIR)3

Prefix	Country	RIR	Status
155.133.40.0/21	🇵🇱 PL	RIPENCC	assigned
185.233.72.0/22	🇵🇱 PL	RIPENCC	allocated
2a0c:d700::/29	🇵🇱 PL	RIPENCC	allocated

All 3 announced prefixes of AS203667 →

BGP Neighbours

(seen in AS paths)

Upstreams (1)

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

AS29535MIX2 OpenPeering Orange Polska Spolka Akcyjna3

Transfer History

Registry transfers of AS203667 between organisations.

AS203667M&A · 2023-09-12
Piotr Gadomski trading as PC Service Piotr Gadomski, Bartosz Gadomski S.C.
RIPE NCC
→
ZIPnet sp. z o.o.
RIPE NCC

Date	Resource	From	To	Type
2023-09-12	AS203667	Piotr Gadomski trading as PC Service Piotr Gadomski, Bartosz Gadomski S.C. RIPE NCC	ZIPnet 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 AS203667 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/203667

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

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