Publishing Packages Degraded Performance

At a glance · npm's status

ResolvedLasted 21 min

First posted
on npm Status
Ended
· marked resolved
Affects
npm package publishing
Edited
Not since we first saw it
Source
npm Status · checked 1 min ago

In short

npm reported degraded service affecting npm package publishing, starting 16:13 UTC on 15 Sep. npm marked it resolved at 16:35 UTC after 21 min.

npm says

npm's latest update, , in short excerpts.

This incident has been resolved.

npm,

Read the full update on npm's status page

Timeline

Times in UTC, npm's own where it gives them.

  1. 15 Sep

    npmFirst public postFrom npm's own incident history, before our archive started.

  2. +22 min

    npmResolved

What npm changed

npm adds updates to its incidents. We save every version (checked every minute) and list what changed. Quotes are short excerpts. The full text is on npm's page.

One version so far. If npm edits it, each change shows here with what was removed and added.

  1. First version we captured ·

    As first seen: resolved · 1 service
    Status
    resolved
    Services
    npm package publishing

    Seen by us · npm's timestamp · npm's page

Affected services

Official updates

Posted by npm Status, newest first. The newest are quoted in their first sentence; the full text of each is on npm's page.

  1. Resolved ·

    This incident has been resolved.

  2. Investigating ·

    We are investigating delays affecting npm package publishing.

Read the full update on npm's status page

Last updated