AS209846 swpforzheim SWP Stadtwerke Pforzheim GmbH & Co. KG
🇩🇪Org handle: ORG-SSPG2-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
6total
5 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)9,472
Announced (BGP)1,280
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)7.9×10²⁸
Announced Prefixes
(BGP)6|
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 |
Allocated Prefixes
(RIR)4Prefix | Country | RIR | Status |
|---|---|---|---|
| 89.58.128.0/19 | 🇩🇪 DE | RIPENCC | allocated |
| 185.227.156.0/22 | 🇩🇪 DE | RIPENCC | allocated |
| 192.16.137.0/24 | 🇩🇪 DE | RIPENCC | assigned |
| 2a0c:be00::/29 | 🇩🇪 DE | RIPENCC | allocated |
All 6 announced prefixes of AS209846 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS209846 hands its own prefixes to: transit providers, or peers at an exchange.
- AS39257LUMi6
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 AS209846 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/209846Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/209846" | jq