Skip to main content

AS35271

AVIEL-AS

Network in Ramenskoye city

Registry

Authoritative registration data

AS number
35271
Name
AVIEL-AS
Organisation
Network in Ramenskoye city
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

1

Total announced

3

Announced prefixes

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

Prefixes announced by AS35271
31.10.64.0/18 IPv4 /18 not checked
93.185.192.0/20 IPv4 /20 not checked
2a03:700::/32 IPv6 /32 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 AS35271
Address families
MSK-IX Moscow: MSK-IX peering network 20,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 AS35271 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

11 networks seen before AS35271 in AS paths

Observed upstreams
Families
AS21453 FLEX-AS 213 291
v4 v6
AS3216 SOVAM-AS 100 268
v4
AS42861 FOTONTELECOM-TRANSIT-AS 80 183
v4 v6
AS57304 RETNRU-AS 61 146
v4
AS28917 Fiord-AS 30 68
v4
AS6939 HURRICANE 16 32
v4
AS25091 IP-Max 5 24
v4 v6
AS29076 CITYTELECOM-AS 7 20
v4
AS41327 FIBERTELECOM-AS 2 5
v4 v6
AS1299 TWELVE99 1 2
v4
AS9198 KAZTELECOM-AS 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS35271 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

6 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 9
v4 v6
AS28910 INTAL-ASN 1 3
v4 v6
AS36236 NETACTUATE 1 3
v4 v6
AS41722 MIRAN-AS 1 3
v4 v6
AS35598 INETCOM 1 2
v4
AS49673 TRUENETWORK 1 2
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.