AS57896 YNET-AS YNET MANAGEMENT PAWEL SKRODZKI

🇵🇱

Org handle: ORG-YMPS2-RIPE

RIPE NCCallocated

Announced Prefixes (BGP)

4total

4 IPv40 IPv6

IPv4 Addresses

Allocated (RIR)5,120

Announced (BGP)5,120

IPv6 Addresses

Allocated (RIR)1.2×10²⁴

Announced (BGP)0

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

RIR

Status

allocated

Allocated

2012-03-07

Announced Prefixes

(BGP)4

Prefix	RPKI	IRR	Last Seen
31.41.144.0/22	No ROA	RIPE	2026-10-11
176.109.48.0/21	No ROA	RIPE	2026-10-11
185.166.168.0/22	No ROA	RIPE	2026-10-11
194.50.156.0/22	No ROA	RIPE	2026-10-11

(RIR)5

Prefix	Country	RIR	Status
31.41.144.0/22	🇵🇱 PL	RIPENCC	assigned
176.109.48.0/21	🇵🇱 PL	RIPENCC	assigned
185.166.168.0/22	🇵🇱 PL	RIPENCC	allocated
194.50.156.0/22	🇵🇱 PL	RIPENCC	assigned
2001:67c:2e3c::/48	🇵🇱 PL	RIPENCC	assigned

(seen in AS paths)

Networks AS57896 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 AS57896 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/57896" | jq