CompaniesLinode (Akamai)Incidents
Linode (Akamai): Connectivity Issue - Newark
Timeline of updates
- resolved
No further interruption has been seen in the last hour, and we believe that we have identified and mitigated the root cause of this network incident, which was a hardware failure. Our logging and monitoring systems indicate that this degradation occurred at 19:01 UTC and was resolved for the majority of customers by 19:16 UTC. If any customers are still experiencing issues after this timeframe, please contact support.
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: minor) posted by Linode (Akamai), started 2015-10-15 19:11 UTC, resolved after 2.4 h, 1 update(s).
- Title
- Connectivity Issue - Newark
- Vendor
- Linode (Akamai)
- Date
- URL
- https://rewindex.com/company/linode-akamai/incidents/vf7fmy2rrqxx
Linode (Akamai) profileRecent Linode (Akamai) incidentsAll outages on October 15, 2015Linode (Akamai) in October 2015MarkdownJSON