# npm: We are currently investigating an uptick of 503 and 504 return codes

> npm status incident “We are currently investigating an uptick of 503 and 504 return codes” on 2018-06-13: impact none (vendor’s label), 3.1 h, 1 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/npm/incidents/4nzcjzn1f2pn
Last updated: 2018-06-13T19:11:00Z

- Impact (vendor’s label): none
- Status: resolved
- Started: 2018-06-13 16:04 UTC · Resolved: 2018-06-13 19:11 UTC · Duration: 3.1 h
- Updates: 1
- [Vendor status page: https://status.npmjs.org/incidents/4nzcjzn1f2pn](https://status.npmjs.org/incidents/4nzcjzn1f2pn)
- [Company: npm](https://rewindex.com/company/npm.md)

## Timeline of updates

- **resolved** 2018-06-13 19:11 UTC: This incident has been resolved.

_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: none) posted by npm, started 2018-06-13 16:04 UTC, resolved after 3.1 h, 1 update(s).

- Canonical URL: https://rewindex.com/company/npm/incidents/4nzcjzn1f2pn
- Citation: npm, “We are currently investigating an uptick of 503 and 504 return codes” (2018-06-13 16:04 UTC). Archived by Rewindex: https://rewindex.com/company/npm/incidents/4nzcjzn1f2pn (CC BY 4.0).
- Markdown link: `[npm: We are currently investigating an uptick of 503 and 504 return codes (2018-06-13)](https://rewindex.com/company/npm/incidents/4nzcjzn1f2pn)`


---
Canonical: https://rewindex.com/company/npm/incidents/4nzcjzn1f2pn · Markdown: https://rewindex.com/company/npm/incidents/4nzcjzn1f2pn.md · JSON: https://rewindex.com/api/v1/companies/npm/incidents/4nzcjzn1f2pn · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-04T13:44:17.425Z