AS49787 PL-STRONG-PC-AS STRONG-PC Tomasz Piekarski

🇵🇱

Org handle: ORG-SA452-RIPE

RIPE NCCallocated

Announced Prefixes (BGP)

4total

3 IPv41 IPv6

IPv4 Addresses

Allocated (RIR)3,776

Announced (BGP)3,584

IPv6 Addresses

Allocated (RIR)1.2×10²⁴

Announced (BGP)1.2×10²⁴

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

RIR

Status

allocated

Allocated

2009-09-10

Announced Prefixes

(BGP)4

Prefix	RPKI	IRR	Last Seen
91.90.112.0/21	No ROA	RIPE	2026-10-11
156.67.96.0/22	No ROA	RIPE	2026-10-11
195.242.134.0/23	No ROA	RIPE	2026-10-11
2001:67c:2ee8::/48	No ROA	RIPE	2026-10-11

(RIR)6

Prefix	Country	RIR	Status
91.90.112.0/21	🇵🇱 PL	RIPENCC	assigned
156.67.96.0/22	🇵🇱 PL	RIPE	assigned
193.34.193.0/25	🇵🇱 PL	RIPENCC	assigned
195.60.92.128/26	🇵🇱 PL	RIPENCC	assigned
195.242.134.0/23	🇵🇱 PL	RIPENCC	assigned
2001:67c:2ee8::/48	🇵🇱 PL	RIPENCC	assigned

(seen in AS paths)

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

ASPA

No ASPA

Abuse Contact

+31205354444

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 AS49787 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/49787" | jq