AS205103 TELEGRAPH-AS Telegraph42 Management GmbH
🇩🇪Org handle: ORG-TMG9-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
2total
1 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)2,048
Announced (BGP)1,024
IPv6 Addresses
Allocated (RIR)3.1×10²⁹
Announced (BGP)3.1×10²⁹
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)6Prefix | Country | RIR | Status |
|---|---|---|---|
| 185.230.68.0/22 | 🇩🇪 DE | RIPENCC | allocated |
| 185.230.68.0/24 | 🇩🇪 DE | RIPE | assigned |
| 185.230.69.0/24 | 🇩🇪 DE | RIPE | assigned |
| 185.230.70.0/24 | 🇩🇪 DE | RIPE | assigned |
| 185.230.71.0/24 | 🇩🇪 DE | RIPE | assigned |
| 2a0c:500::/30 | 🇩🇪 DE | RIPENCC | allocated |
All 2 announced prefixes of AS205103 →
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS205103 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (6)
Networks whose own prefixes AS205103 passes on: usually its customers.
Other adjacent networks (10)
Adjacent to AS205103 in the transit part of AS paths: peers, providers or customers.
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/205103Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/205103" | jq