AS202572 SI-PL-CLOUD Jacek Kowalski trading as SI.pl
🇵🇱Org handle: ORG-JKTA3-RIPE
-----BEGIN TOKEN-----5abbce5e55102d4e149a76de1c67f827e6d8a119c61050556b9ebf184f9ac0152b711f9671da974f9ba131d3e2a8a5d0cabc5d655916305d3a49cd252591c7b1-----END TOKEN-----
RIPE NCCallocated
Announced Prefixes (BGP)
1total
1 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)256
Announced (BGP)256
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Announced Prefixes
(BGP)1|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)1Prefix | Country | RIR | Status |
|---|---|---|---|
| 185.254.64.0/24 | 🇵🇱 PL | RIPENCC | allocated |
All 1 announced prefix of AS202572 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS202572 hands its own prefixes to: transit providers, or peers at an exchange.
- AS16276OVH SAS1
ASPA
No ASPA
Abuse Contact
External Links
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 AS202572 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 https://api.ipctl.io/v1/asn/202572Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/202572" | jq