AS15945 PfalzKom-Net PFALZKOM GmbH
🇩🇪Org handle: ORG-PGfT1-RIPE
Koschatplatz 1
RIPE NCCallocatedASPA Published
Announced Prefixes (BGP)
2total
1 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)0
Announced (BGP)256
IPv6 Addresses
Allocated (RIR)1.2×10²⁴
Announced (BGP)1.2×10²⁴
Routing hygiene
Score 10/100 · Low riskRPKI ROA coverage
100%
no RPKI invalid prefixes
IRR route objects
100%
no origin mismatches
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
1
diversity 0/100
- Only one upstream seen in the AS paths of its routes
Based on 2 announced prefixes, updated daily (2026-10-25). How the score works · RPKI explained
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-25 | |
| Valid | RIPE | 2026-10-25 |
Allocated Prefixes
(RIR)1Prefix | Country | RIR | Status |
|---|---|---|---|
| 2a02:24d8:ffff::/48 | 🇩🇪 DE | RIPE | assigned |
All 2 announced prefixes of AS15945 →
Upstream Providers(2)
Downstream Customers(1)
| ASN | Name |
|---|---|
| AS56368 | 🇩🇪NICODUCK Nicola von Thadden |
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS15945 hands its own prefixes to: transit providers, or peers at an exchange.
- AS174Cogent Communications2
Downstreams (8)
Networks whose own prefixes AS15945 passes on: usually its customers.
Other adjacent networks (1)
Adjacent to AS15945 in the transit part of AS paths: peers, providers or customers.
- AS33891CORE BACKBONE Core Backbone14
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
- How to run an ASPA checkVerify the upstream providers listed above
- 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/15945Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/15945" | jq