# Linode (Akamai): Impacted Connectivity in Newark

> Linode (Akamai) status incident “Impacted Connectivity in Newark” on 2017-03-23: impact minor (vendor’s label), 10 d, 1 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/linode-akamai/incidents/166trmv1dv1w
Last updated: 2017-04-02T21:14:00Z

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2017-03-23 16:21 UTC · Resolved: 2017-04-02 21:14 UTC · Duration: 10 d
- Updates: 1
- [Vendor status page: https://status.linode.com/incidents/166trmv1dv1w](https://status.linode.com/incidents/166trmv1dv1w)
- [Company: Linode (Akamai)](https://rewindex.com/company/linode-akamai.md)

## Timeline of updates

- **resolved** 2017-04-02 21:14 UTC: At this time, we believe a scheduled code upgrade on Tuesday, April 4th for a core router in Newark will resolve any lingering connectivity issues.

_From the vendor’s published history: only the final update text is available for incidents before Rewindex began polling this page._

## Cite this

Status incident (vendor impact label: minor) posted by Linode (Akamai), started 2017-03-23 16:21 UTC, resolved after 10 d, 1 update(s).

- Canonical URL: https://rewindex.com/company/linode-akamai/incidents/166trmv1dv1w
- Citation: Linode (Akamai), “Impacted Connectivity in Newark” (2017-03-23 16:21 UTC). Archived by Rewindex: https://rewindex.com/company/linode-akamai/incidents/166trmv1dv1w (CC BY 4.0).
- Markdown link: `[Linode (Akamai): Impacted Connectivity in Newark (2017-03-23)](https://rewindex.com/company/linode-akamai/incidents/166trmv1dv1w)`


---
Canonical: https://rewindex.com/company/linode-akamai/incidents/166trmv1dv1w · Markdown: https://rewindex.com/company/linode-akamai/incidents/166trmv1dv1w.md · JSON: https://rewindex.com/api/v1/companies/linode-akamai/incidents/166trmv1dv1w · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-04T17:14:33.908Z