Skip to main content

AS40328

ACENTEK-MN

AcenTek

Registry

Authoritative registration data

AS number
40328
Name
ACENTEK-MN
Organisation
AcenTek
Country
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

11

IPv6 prefixes

3

Total announced

14

Announced prefixes

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

Prefixes announced by AS40328
205.185.128.0/19 IPv4 /19 not checked
108.59.96.0/20 IPv4 /20 not checked
205.185.128.0/20 IPv4 /20 not checked
205.185.144.0/20 IPv4 /20 not checked
162.249.96.0/21 IPv4 /21 not checked
208.74.240.0/21 IPv4 /21 not checked
108.59.108.0/22 IPv4 /22 not checked
108.59.106.0/23 IPv4 /23 not checked
162.249.100.0/23 IPv4 /23 not checked
162.249.102.0/23 IPv4 /23 not checked
162.249.98.0/23 IPv4 /23 not checked
2606:ec00:1000::/36 IPv6 /36 not checked
2606:ec00:1000::/40 IPv6 /40 not checked
2606:ec00:a100::/40 IPv6 /40 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 AS40328
Address families
MICE: Shared Peering 10,000 Mbps IPv4 · IPv6
QCIX: Main 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 AS40328 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS40328 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 998 17,817
v4 v6
AS174 COGENT-174 282 2,088
v4 v6
AS32621 TCV-511 1 5
v4

No rows match “”.

Showing of

Observed downstreams

2 networks seen after AS40328 in AS paths

Observed downstreams
Families
AS394099 470 12,214
v4
AS395855 271 2,667
v4

No rows match “”.

Showing of

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS394414 AS394414 1 6
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.