AS38923 OSIEDLOWA Pawel Kowalski BGCOM
๐ต๐ฑOrg handle: ORG-PKB1-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
4total
4 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)5,120
Announced (BGP)5,120
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Prefix Limit (IPv4)
10
Prefix Limit (IPv6)
5
Country
๐ต๐ฑ PLRIR
RIPE NCCStatus
allocated
Allocated
2005-11-15
Announced Prefixes
(BGP)4|
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 |
Allocated Prefixes
(RIR)4Prefix | Country | RIR | Status |
|---|---|---|---|
| 83.142.136.0/21 | ๐ต๐ฑ PL | RIPENCC | assigned |
| 193.218.148.0/22 | ๐ต๐ฑ PL | RIPENCC | assigned |
| 194.54.16.0/22 | ๐ต๐ฑ PL | RIPENCC | assigned |
| 195.206.112.0/22 | ๐ต๐ฑ PL | RIPENCC | assigned |
All 4 announced prefixes of AS38923 โ
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS38923 hands its own prefixes to: transit providers, or peers at an exchange.
- AS52153BGCOM Pawel Kowalski BGCOM4
ASPA
No ASPA
Abuse Contact
+31205354444
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 AS38923 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/38923Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/38923" | jq