AS41307 TPP Telepark Passau GmbH
🇩🇪Org handle: ORG-TPG1-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
5total
4 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)13,312
Announced (BGP)13,312
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)6.3×10²⁹
Announced Prefixes
(BGP)5|
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 |
Allocated Prefixes
(RIR)5Prefix | Country | RIR | Status |
|---|---|---|---|
| 88.133.192.0/19 | 🇩🇪 DE | RIPENCC | allocated |
| 89.28.136.0/21 | 🇩🇪 DE | RIPENCC | allocated |
| 109.69.96.0/21 | 🇩🇪 DE | RIPENCC | allocated |
| 185.39.64.0/22 | 🇩🇪 DE | RIPENCC | allocated |
| 2a02:ca00::/29 | 🇩🇪 DE | RIPENCC | allocated |
All 5 announced prefixes of AS41307 →
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS41307 hands its own prefixes to: transit providers, or peers at an exchange.
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 AS41307 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/41307Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/41307" | jq