CHYP.ai · ORBIT // Cloudy_Day Security Suite

CDN & edge

Degraded / minor incident Akamai status

akamai.com · Official status page (Statuspage-compatible JSON)

FROM ALL SOURCES

Akamai's status page shows “Degraded / minor incident” in Customer Security Advisory and Reporting; the vendor is resolved. User reports haven't spiked, so wide impact isn't visible yet.

confidence: medium Vendor: minor issue · users: normal · routing: no data.

Vendor status vs. reality: Vendor reports an issue we don't see in crowd or routing data (it may be partial or internal)

Regions mentioned: Customer Security Advisory, Reporting, Edge Delivery

The four clocks
ClockStartedRunning
Vendor clock when the vendor's open incident started29 days
Crowd clock when user reports began rising above normalnot seenn/a
Network clock when routing anomaly data first flagged itnot seenn/a
ORBIT clock when our checker first recorded the change6 h 37 min

Evidence

  • Official page: Degraded / minor incident (“Partially Degraded Service”). evidence confidence: high
  • Vendor stage: resolved on “Customer Security Advisory: Critical F5/NGINX Out-of-Band Vulnerabilities”. evidence confidence: high
  • User reports are within normal range (0 in 15 min). evidence confidence: low
  • 1 active network-weather event mentions Akamai. Overlap in time is coincidence, not causation. evidence confidence: low

What we don't know: what is happening inside Akamai's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp, providers it may run on (inferred). Routing data shows reachability, not whether the app works.

Coincidence, not causation: signals that overlap in time are shown side by side, not as proof of cause.

Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .

Cloudy_Day's take

Stage vs. health

The vendor's stage is “resolved”. Stage tells you where they are in their process; health is what users experience. Right now vendor: minor issue · users: normal · routing: no data. Vendor reports an issue we don't see in crowd or routing data (it may be partial or internal).

Who depends on whom

1 other service in our catalog may lean on Akamai, so trouble here can show up elsewhere first. Dependency chains are where single points of failure hide.

Identity & trust lens

Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.

For users

Check the official status page before changing settings or reinstalling. If you must act, use known-good bookmarks. Reporting what's broken on ORBIT helps everyone see the real footprint.

For security teams

Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on Akamai, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).

What to watch next

The vendor stage moving to “monitoring”, then “resolved”; the user-report curve falling back under baseline; and whether dependents start reporting issues.

Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with Akamai. No blame or attack claims without an official source. Generated .

INCIDENT REPLAY

Customer Security Advisory: Critical F5/NGINX Out-of-Band Vulnerabilities

none resolved · started · resolved

5 updates

  1. investigating

    Akamai is aware of the recently published F5/NGINX vulnerabilities (CVE-2026-15176, CVE-2026-97205, and CVE-2026-93479), and our teams are investigating their potential impact across our platform and infrastructure.F5 has released out-of-band security patches addressing three critical severity vulnerabilities in NGINX Open Source and NGINX Plus. These vulnerabilities may allow unauthenticated attackers to trigger heap buffer overflows, which could cause a denial of service or potential remote code execution if ASLR is bypassed.If you are running a vulnerable version of NGINX Open Source or NGINX Plus, we recommend following guidance from F5/NGINX and applying available patches.We will post more details for customers and partners with a valid Control Center login at https://community.akamai.com/customers/s/group/0F90f000000DFgx/service-incident-notifications as additional information beco

  2. identified

    Akamai continues to investigate the potential impact of the recently published F5/NGINX vulnerabilities (CVE-2026-15176, CVE-2026-97205, and CVE-2026-93479) across our platform and infrastructure. Our teams are taking action where necessary and will provide additional updates as more information becomes available.Customers and partners with a valid Control Center login can find more details at https://community.akamai.com/customers/s/group/0F90f000000DFgx/service-incident-notifications.If you have questions or are experiencing impact related to this issue, please use the Support Center on Akamai Community or Akamai Control Center to contact Akamai Technical Support. Contact information is available at https://www.akamai.com/us/en/support/.

  3. monitoring

    Akamai continues to investigate the potential impact of the recently published F5/NGINX vulnerabilities (CVE-2026-15176, CVE-2026-97205, and CVE-2026-93479) across our platform and infrastructure.As part of our initial assessment, we included EAA, MFA, and SIA in the affected component selection. Based on our investigation to date, we have determined that these offerings are not vulnerable to these CVEs and have updated the affected component selection accordingly. We apologize for any concern this may have caused.Our teams continue to monitor the situation closely and respond where necessary. We will update the affected components as our investigation progresses.Customers and partners with a valid Control Center login can find more details at https://community.akamai.com/customers/s/group/0F90f000000DFgx/service-incident-notifications.If you have questions or are experiencing impact rel

  4. monitoring

    Akamai continues to investigate the potential impact of the recently published F5/NGINX vulnerabilities (CVE-2026-15176, CVE-2026-97205, and CVE-2026-93479) across our platform and infrastructure. Customers and partners with a valid Control Center login can find more details at https://community.akamai.com/customers/s/group/0F90f000000DFgx/service-incident-notifications. If you have questions or are experiencing impact related to this issue, please use the Support Center on Akamai Community or Akamai Control Center to contact Akamai Technical Support. Contact information is available at https://www.akamai.com/us/en/support/.

  5. resolved

    Akamai has completed its investigation of the recently published F5/NGINX vulnerabilities (CVE-2026-15176, CVE-2026-97205, and CVE-2026-93479). We have not identified any impact to Akamai’s platform or infrastructure, and services remain operating normally.If you run a vulnerable version of NGINX Open Source or NGINX Plus on a Linode instance, follow F5/NGINX guidance and apply the available patches.Customers and partners with a valid Control Center login can find more details at https://community.akamai.com/customers/s/group/0F90f000000DFgx/service-incident-notifications, or by reaching out to Akamai Support. Thank you for your patience and continued support.

Official incident page ↗

Community comments (0)

Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.

No approved comments yet.

How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.

Where to next