Skip to main content

AS402366

SOHEIL-DS

Soheil Digital Solutions Ltd.

Registry

Authoritative registration data

AS number
402366
Name
SOHEIL-DS
Organisation
Soheil Digital Solutions Ltd.
Country
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

1

Total announced

4

Announced prefixes

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

Prefixes announced by AS402366
199.242.219.0/24 IPv4 /24 not checked
208.71.255.0/24 IPv4 /24 not checked
23.158.36.0/24 IPv4 /24 not checked
2602:f3c4::/36 IPv6 /36 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 AS402366
Address families
SIX Seattle: MTU 1500 1,000 Mbps IPv4 · IPv6
YYCIX 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 AS402366 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS402366 in AS paths

Observed upstreams
Families
AS174 COGENT-174 189 751
v4 v6
AS6939 HURRICANE 225 373
v4 v6
AS263812 263812 38 145
v4 v6
AS137409 GSLNETWORKS-AS-AP 4 15
v4
AS9002 RETN-AS 2 7
v4 v6
AS394256 CLOUDSINGULARITY 1 4
v4 v6
AS7575 1 3
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS402366 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 36
v4 v6
AS49544 i3Dnet 1 8
v4 v6
AS36236 NETACTUATE 1 4
v4 v6
AS18106 VIEWQWEST-SG-AP 1 3
v4
AS35280 F5 1 3
v4
AS1828 UNITAS 1 1
v6

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.