Skip to main content

AS43297

VDS-TELECOM

VDS-Telecom LLC.

Registry

Authoritative registration data

AS number
43297
Name
VDS-TELECOM
Organisation
VDS-Telecom LLC.
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

14

IPv6 prefixes

0

Total announced

14

Announced prefixes

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

Prefixes announced by AS43297
178.57.64.0/24 IPv4 /24 not checked
178.57.69.0/24 IPv4 /24 not checked
178.57.70.0/24 IPv4 /24 not checked
185.13.32.0/24 IPv4 /24 not checked
185.13.35.0/24 IPv4 /24 not checked
188.68.4.0/24 IPv4 /24 not checked
193.3.185.0/24 IPv4 /24 not checked
194.32.231.0/24 IPv4 /24 not checked
45.145.1.0/24 IPv4 /24 not checked
46.17.252.0/24 IPv4 /24 not checked
5.133.111.0/24 IPv4 /24 not checked
79.133.98.0/24 IPv4 /24 not checked
95.85.86.0/24 IPv4 /24 not checked
95.85.87.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 AS43297
Address families
Eurasia Peering IX: Peering LAN 1,000 Mbps IPv4

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 AS43297 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS43297 in AS paths

Observed upstreams
Families
AS12695 DINET-AS 267 2,049
v4
AS35598 INETCOM 601 1,269
v4
AS62255 BEMYLINK 222 502
v4
AS41327 FIBERTELECOM-AS 5 8
v4
AS31500 GNM-AS 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS43297 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 3 7
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.