Akamai Technologies $AKAM Technical Update – Stock Traders Daily

This post was originally published on this site

https://lh5.googleusercontent.com/proxy/2P1w63I8rs1sJ8B23opf-SSgPJKyd0PwNmYrn4FV7l2I1VKRVd8Sg1I56ftGdbkg6JkY_Ka54IlaYNEQW3e470D2SDqtUpEWG3vQNyw=-w150-h150-c

Akamai Technologies $AKAM Technical Update

The Akamai Technologies (NASDAQ: AKAM) update and the technical summary table below can help you manage risk and optimize returns. We have day, swing, and longer-term trading plans for AKAM, and 1300 other stocks too, updated in real time for our trial subscribers. The data below is a snapshot, but updates are available now.

Review the Trading Plans:

Technical Summary

Term → Near Mid Long
Bias Strong Strong Neutral
P1 65.61 56.19 55.06
P2 67.16 62.61 62.29
P3 68.73 68.64 69.23

Long Term Trading Plans for AKAM

February 9, 2019, 1:15 am ET

The Technical Summary and Trading Plans for AKAM help you determine where to buy, sell, and set risk controls. The data is best used in conjunction with our Market Analysis and Stock Correlation Filters too, because those help us go with the flow of the market as well. Going with the flow is extremely important, so review our Market Analysis with this AKAM Report.

AKAM – (Long) Support Plan

The technical summary data tells us to buy AKAM near 62.29 with an upside target of 69.23. This data also tells us to set a stop loss @ 62.03 to protect against excessive loss in case the stock begins to move against the trade. 62.29 is the first level of support below 67.09 , and by rule, any test of support is a buy signal. In this case, support 62.29 is being tested, a buy signal would exist.

AKAM – (Short) Resistance Plan

The technical summary data is suggesting a short of AKAM as it gets near 69.23 with a downside target of 62.29. We should have a stop loss in place at 69.49 though. 69.23 is the first level of resistance above 67.09, and by rule, any test of resistance is a short signal. In this case, if resistance 69.23 is being tested, a short signal would exist.

This post was originally published on *this site*