AS25081 HDiT-AS Heidelberg IT Management GmbH & Co.KG
๐ฉ๐ชOrg handle: ORG-MKG1-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
4total
3 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)5,632
Announced (BGP)5,632
IPv6 Addresses
Allocated (RIR)6.3ร10ยฒโน
Announced (BGP)6.3ร10ยฒโน
Prefix Limit (IPv4)
10
Prefix Limit (IPv6)
5
Country
๐ฉ๐ช DERIR
RIPE NCCStatus
allocated
Allocated
2002-07-22
Announced Prefixes
(BGP)4|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-09 | |
195.234.216.0/22MOAS | Valid | RIPE | 2026-10-09 |
195.248.252.0/23MOAS | Valid | RIPE | 2026-10-09 |
| Valid | RIPE | 2026-10-09 |
Allocated Prefixes
(RIR)4Prefix | Country | RIR | Status |
|---|---|---|---|
| 81.89.192.0/20 | ๐ฉ๐ช DE | RIPENCC | allocated |
| 185.213.96.0/22 | ๐ฉ๐ช DE | RIPENCC | allocated |
| 195.248.252.0/23 | ๐ฉ๐ช DE | RIPENCC | assigned |
| 2a04:c940::/29 | ๐ฉ๐ช DE | RIPENCC | allocated |
All 4 announced prefixes of AS25081 โ
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS25081 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (2)
Networks whose own prefixes AS25081 passes on: usually its customers.
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 AS25081 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/25081Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/25081" | jq