Live  /  Akamai  /  Incident

Akamai: Enterprise Application Access (EAA) Connector Issues

Akamai · akamai.comMinor incidentResolved2026-10-27 15:52 UTC
Public — what happened

Summary

Akamai said a problem with its Enterprise Application Access service affected some Unified EAA Connectors, and that it began around 01:25 UTC on October 27, 2026. The company posted its first notice at 09:58 UTC, and by 11:44 UTC it said it had identified the cause and was putting a fix in place. In its final update at 15:52 UTC, Akamai said the issue had been mitigated at 08:30 UTC and the service was back to normal operation. It pointed customers to a community page and Akamai Support for further details.

Affected

Enterprise Application Access

As listed on Akamai’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

What SquidGrid measured

SquidGrid measured 259 internet paths into Akamai’s network during this incident. 1 of them ran 25 ms or more slower than the same paths at the same time the day before (on an ordinary day, 0 did).

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Akamai against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Akamai: paths off baseline right now, where on the route conditions change, and its full incident track record.

Included with any paid plan.

Open the Akamai report →

More from Akamai

Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.

The full archive is on the Akamai status & history page.

Related: Akamai status & history. SquidGrid is not affiliated with Akamai.