AS8391 KNIPP-AS Knipp Medien und Kommunikation GmbH
๐ฉ๐ชOrg handle: ORG-KMuK1-RIPE
Knipp Medien und Kommunikation GmbH
RIPE NCCallocated
Announced Prefixes (BGP)
17total
15 IPv42 IPv6
IPv4 Addresses
Allocated (RIR)19,968
Announced (BGP)63,744
IPv6 Addresses
Allocated (RIR)7.9ร10ยฒโธ
Announced (BGP)7.9ร10ยฒโธ
Prefix Limit (IPv4)
50
Prefix Limit (IPv6)
10
Country
๐ฉ๐ช DERIR
RIPE NCCStatus
allocated
Allocated
1997-07-22
Announced Prefixes
(BGP)17|
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 | - | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
1-10 of 17
1 / 2
Allocated Prefixes
(RIR)11Prefix | Country | RIR | Status |
|---|---|---|---|
| 195.138.32.0/22 | ๐ฉ๐ช DE | RIPENCC | allocated |
| 195.138.38.0/24 | ๐ฉ๐ช DE | RIPENCC | allocated |
| 195.138.54.0/24 | ๐ฉ๐ช DE | RIPENCC | allocated |
| 195.138.61.0/24 | ๐ฉ๐ช DE | RIPENCC | allocated |
| 195.138.62.0/24 | ๐ฉ๐ช DE | RIPENCC | allocated |
| 195.253.20.0/24 | ๐ฉ๐ช DE | RIPE | assigned |
| 195.253.31.0/24 | ๐จ๐ญ CH | RIPE | assigned |
| 195.253.128.0/18 | ๐ฉ๐ช DE | RIPENCC | allocated |
| 195.253.128.0/22 | ๐ณ๐ฑ NL | RIPE | assigned |
| 2a01:5b0::/32 | ๐ฉ๐ช DE | RIPENCC | allocated |
1-10 of 11
1 / 2
All 17 announced prefixes of AS8391 โ
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS8391 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (2)
Networks whose own prefixes AS8391 passes on: usually its customers.
Other adjacent networks (1)
Adjacent to AS8391 in the transit part of AS paths: peers, providers or customers.
- AS15763ASDOKOM DOKOM Gesellschaft Fuer Telekommunikation MbH1
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 AS8391 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/8391Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/8391" | jq