AS6735 SDTNET TNG Stadtnetz GmbH
🇩🇪Org handle: ORG-TSG19-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
4total
4 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)33,024
Announced (BGP)33,024
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Announced Prefixes
(BGP)4|
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 |
Allocated Prefixes
(RIR)4Prefix | Country | RIR | Status |
|---|---|---|---|
| 62.68.0.0/19 | 🇩🇪 DE | RIPENCC | allocated |
| 194.88.160.0/19 | 🇩🇪 DE | RIPENCC | allocated |
| 194.113.117.0/24 | 🇩🇪 DE | RIPENCC | assigned |
| 195.245.0.0/18 | 🇩🇪 DE | RIPENCC | allocated |
All 4 announced prefixes of AS6735 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS6735 hands its own prefixes to: transit providers, or peers at an exchange.
- AS13101TNG Stadtnetz4
Downstreams (1)
Networks whose own prefixes AS6735 passes on: usually its customers.
- AS8405SONTHEIMER IT PE Sontheimer Bernd9
Other adjacent networks (1)
Adjacent to AS6735 in the transit part of AS paths: peers, providers or customers.
- AS5405INTERDOTLINK Inter.Link2
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 AS6735 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/6735Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/6735" | jq