Authorize.Net has sent out a few reminders about their impending switch to Akamai occurring on June 30th, but the other day they sent out an update stating that using Akamai will no longer be required by that date.
JUNE 30TH MIGRATION TO AKAMAI SUREROUTE IS NOW VOLUNTARY, BUT REMAINS HIGHLY RECOMMENDED
As communicated over the past nine months, Akamai SureRoute technology has been introduced into our network environment as a new connection option. This technology automatically routes transaction requests around issues that may occur on the Internet, thus helping to ensure transactions are received by Authorize.Net, quickly, securely and reliably. Many Authorize.Net customers have already adopted this connection option and are taking advantage of the benefits offered by Akamai SureRoute technology. If your merchants are not yet connecting to Authorize.Net via Akamai, we encourage them to do so.
WHILE WE CONTINUE TO ENCOURAGE ALL CUSTOMERS TO USE AKAMAI SUREROUTE, THE MIGRATION IS NO LONGER MANDATORY BY JUNE 30, 2016. During the course of migration planning, a few of our customers have reported unique implementations or constraints that prevent them from adopting the Akamai enhancement within the timeframe originally planned. As such, we will continue to support both legacy and Akamai SureRoute connection options. Your merchants may now migrate to the recommended Akamai URLs at their own pace.
For more information on how to upgrade to Akamai SureRoute, please visit the Authorize.Net website at http://www.authorize.net/support/akamaifaqs/.
If you would still like to begin using Akamai with your Authorize.Net gateway, you will need to connect with a web developer in order to implement it. They will likely be able to complete this task for you without much hassle.
If you do not have a developer that you work with, most likely you are using a website service that helps you build the website through their own system, such as WordPress or Wix. If you are using one of these services, it is actually possible that they will be making this change automatically for all of their users, since Authorize.Net is so widely used around the world. We recommend reaching out to this service in order to confirm whether any action is needed on your part or not. It is also possible you will need to reach out to the provider of your actual firewall plugin, instead.