rewindex

CompaniesLinode (Akamai)Incidents

Linode (Akamai): Increased Latency in Fremont

No impact listedStatus: resolvedStarted Resolved (23 h)1 updatestatus.linode.com (opens in new tab)

Timeline of updates

  1. resolved

    All service has returned to normal at this time.

From Linode (Akamai)’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

Impact, status and times are the vendor’s own, as last archived. View on status.linode.com (opens in new tab).

Cite this

Status incident (vendor impact label: none) posted by Linode (Akamai), started 2015-05-19 20:05 UTC, resolved after 23 h, 1 update(s).

Title
Increased Latency in Fremont
Vendor
Linode (Akamai)
Date
URL
https://rewindex.com/company/linode-akamai/incidents/dcs24842jv97

Linode (Akamai) profileRecent Linode (Akamai) incidentsAll outages on May 19, 2015Linode (Akamai) in May 2015MarkdownJSON