Skip to main content

AS34265

SILVERTELECOM-AS

SilverTelecom Ltd.

Registry

Authoritative registration data

AS number
34265
Name
SILVERTELECOM-AS
Organisation
SilverTelecom Ltd.
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

13

IPv6 prefixes

0

Total announced

13

Announced prefixes

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

Prefixes announced by AS34265
176.106.0.0/21 IPv4 /21 not checked
176.112.120.0/21 IPv4 /21 not checked
213.108.72.0/21 IPv4 /21 not checked
193.138.184.0/22 IPv4 /22 not checked
176.106.0.0/24 IPv4 /24 not checked
176.106.1.0/24 IPv4 /24 not checked
176.112.120.0/24 IPv4 /24 not checked
176.112.121.0/24 IPv4 /24 not checked
176.112.127.0/24 IPv4 /24 not checked
193.138.186.0/24 IPv4 /24 not checked
193.138.187.0/24 IPv4 /24 not checked
213.108.75.0/24 IPv4 /24 not checked
213.108.78.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

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS34265 in AS paths

Observed upstreams
Families
AS199995 OT-AS 485 1,982
v4
AS6663 281 1,887
v4
AS21497 518 991
v4
AS6939 HURRICANE 22 85
v4
AS3326 5 20
v4

No rows match “”.

Showing of

Observed downstreams

1 networks seen after AS34265 in AS paths

Observed downstreams
Families
AS6663 77 99
v4

No rows match “”.

Showing of

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 1 18
v4
AS48919 1 9
v4
AS59514 1 9
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.