Skip to main content

AS210685

netlease1

Netlease JSC

Registry

Authoritative registration data

AS number
210685
Name
netlease1
Organisation
Netlease JSC
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

0

Total announced

2

Announced prefixes

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

Prefixes announced by AS210685
85.8.194.0/24 IPv4 /24 not checked
91.217.163.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 AS210685 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS210685 in AS paths

Observed upstreams
Families
AS56534 Comfortel 109 253
v4
AS50509 TRANSROUTE 97 217
v4
AS6939 HURRICANE 20 42
v4
AS25091 IP-Max 6 18
v4
AS49434 FBWNETWORKS 2 4
v4
AS9198 KAZTELECOM-AS 1 2
v4
AS21030 CDNNOW-AS 1 2
v4
AS137409 GSLNETWORKS-AS-AP 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS210685 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 16
v4
AS28910 INTAL-ASN 1 2
v4
AS37721 ORG-VTS1-AFRINIC 1 2
v4
AS41722 MIRAN-AS 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.