Breaking

View Evidence Brief What changed, who says so and when, and what was known at each revision.

Four clocks

Began (provider)Tue, 17 Nov 2026 12:46:32 GMT
Latest update published (provider)Tue, 17 Nov 2026 12:47:04 GMT
Seen by SpikeWed, 18 Nov 2026 03:34:25 GMT
DeliveredPer customer, in each Spike Pro workspace's delivery receipts.

What the provider states

ClaimValueEvidence
service statusinvestigatingDirect: Akamai status page · source ↗
affected servicesCustomer Security AdvisoryDirect: Akamai status page · source ↗
CauseAkamai has not stated a cause in a structured field. Read the provider's updates.
Customer impactDepends on what you run. Spike Pro matches this incident to the services a workspace lists.

Revisions, newest first

  • Revision 1 · First recorded by Spike
    Published by Akamai 2026-11-17 12:47 UTC · seen by Spike 887 min later (first read of this status page)

    Akamai said: “Akamai continues to investigate the potential impact of this vulnerability across our platform and infrastructure. As of this time, we have no evidence that this vulnerability has been exploited on any Akamai platform/products. Customers and partners with a valid Control Center…”

This record as JSON · All outages