AS16316 TMT TMT GmbH & Co. KG
🇩🇪Org handle: ORG-TiG1-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
3total
2 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)20,480
Announced (BGP)20,480
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)7.9×10²⁸
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | - | |
| No ROA | RIPE | - | |
| No ROA | RIPE | - |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 88.209.0.0/18 | 🇩🇪 DE | RIPENCC | allocated |
| 217.145.96.0/20 | 🇩🇪 DE | RIPENCC | allocated |
| 2001:4dc8::/32 | 🇩🇪 DE | RIPENCC | allocated |
All 3 announced prefixes of AS16316 →
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS16316 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (2)
Networks whose own prefixes AS16316 passes on: usually its customers.
Other adjacent networks (1)
Adjacent to AS16316 in the transit part of AS paths: peers, providers or customers.
- AS4230CLARO S.A1
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 AS16316 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/16316Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/16316" | jq