AS16110 PODKARPACKI-NET-AS Podkarpacki.net Rafal Czarny
🇵🇱Org handle: ORG-PA413-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
8total
8 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)512
Announced (BGP)2,048
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Announced Prefixes
(BGP)8|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 5.63.185.0/24 | 🇵🇱 PL | RIPENCC | allocated |
| 46.174.211.0/24 | 🇵🇱 PL | RIPENCC | assigned |
All 8 announced prefixes of AS16110 →
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS16110 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (4)
Networks whose own prefixes AS16110 passes on: usually its customers.
Other adjacent networks (1)
Adjacent to AS16110 in the transit part of AS paths: peers, providers or customers.
- AS20804ASN TELENERGO Exatel S.A2
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 AS16110 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/16110Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/16110" | jq