Skip to main content

AS6735

SDTNET

We are currently available for public peering at

Registry

Authoritative registration data

AS number
6735
Name
SDTNET
Organisation
We are currently available for public peering at
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

0

Total announced

4

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS6735
195.245.0.0/18 IPv4 /18 not checked
194.88.160.0/19 IPv4 /19 not checked
62.68.0.0/19 IPv4 /19 not checked
194.113.117.0/24 IPv4 /24 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS6735
Address families
KleyReX: Peering LAN 100 Mbps IPv4 · IPv6
Stuttgart-IX: PeeringLAN 10,000 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS6735 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS6735 in AS paths

Observed upstreams
Families
AS13101 TNG-AS 514 3,627
v4
AS5405 INTERDOTLINK 20 91
v4
AS33891 CORE-BACKBONE 15 77
v4
AS47147 AS-ANX 4 56
v4

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS6735 in AS paths

Observed downstreams
Families
AS8405 SONTHEIMER-IT 287 2,492
v4

No rows match “”.

Showing – of

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS553 BELWUE 2 13
v4

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.