CompaniesLinode (Akamai)Incidents
Linode (Akamai): Packet Loss in Tokyo
Timeline of updates
- resolved
Our upstream provider identified the cause of this as temporary congestion with a neighboring ISP. This issue should now be resolved.
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-09-17 02:02 UTC, resolved after 10 h, 1 update(s).
- Title
- Packet Loss in Tokyo
- Vendor
- Linode (Akamai)
- Date
- URL
- https://rewindex.com/company/linode-akamai/incidents/dvjf67nrb5nj
Linode (Akamai) profileRecent Linode (Akamai) incidentsAll outages on September 17, 2015Linode (Akamai) in September 2015MarkdownJSON