
npm status
@npmstatus
Followers
4K
Following
0
Media
0
Statuses
943
Having trouble with npm? Visit https://t.co/9gnLPkmmLh for status or https://t.co/itIpSbF82w for help.
Joined June 2016
[status] Resolved: This incident has been resolved.
status.npmjs.org
This incident has been resolved.
0
0
0
[status] Monitoring: We are continuing to monitor for any further issues.
status.npmjs.org
We are continuing to monitor for any further issues.
1
0
0
[status] Monitoring: A fix has been implemented and we are monitoring the results.
status.npmjs.org
A fix has been implemented and we are monitoring the results.
1
0
0
[status] Identified: The issue has been identified and a fix is being implemented.
status.npmjs.org
The issue has been identified and a fix is being implemented.
1
0
0
[status] Investigating: We are continuing to investigate this issue.
status.npmjs.org
We are continuing to investigate this issue.
1
0
0
[status] Investigating: We are investigating an issue where users are experiencing failures during npm install. Errors observed include 429 Too Many Requests and 403 Forbidden for GitHub Actions.
status.npmjs.org
We are investigating an issue where users are experiencing failures during npm install. Errors observed include 429 Too Many Requests and 403 Forbidden for GitHub Actions.
1
5
13
[status] Resolved: This incident has been resolved.
status.npmjs.org
This incident has been resolved.
0
0
1
[status] Monitoring: The issue has been identified and a remediation is being put into place.
status.npmjs.org
The issue has been identified and a remediation is being put into place.
1
0
0
[status] Investigating: We are currently investigating this issue.
status.npmjs.org
We are currently investigating this issue.
1
0
2
[status] Resolved: This incident has been resolved.
status.npmjs.org
This incident has been resolved.
0
0
2
[status] Investigating: We are seeing issues with package publish with provenance due to an outage of a key third party dependency.
status.npmjs.org
We are seeing issues with package publish with provenance due to an outage of a key third party dependency.
1
0
2
[status] Resolved: This incident has been resolved.
status.npmjs.org
This incident has been resolved.
1
0
5
[status] Monitoring: A fix has been implemented and we are monitoring the results.
status.npmjs.org
A fix has been implemented and we are monitoring the results.
4
1
10
[status] Identified: The issue has been identified and a fix is being implemented.
17
2
16
[status] Investigating: We are continuing to investigate this issue.
status.npmjs.org
We are continuing to investigate this issue.
1
0
2
[status] Investigating: We are currently investigating this issue.
status.npmjs.org
We are currently investigating this issue.
45
16
135
[status] Resolved: This incident was caused due to an internal bug during regular database maintenance, its resolved now.
status.npmjs.org
This incident was caused due to an internal bug during regular database maintenance, its resolved now.
0
0
2
[status] Identified: We are continuing to work on a fix to restore older access tokens.
status.npmjs.org
We are continuing to work on a fix to restore older access tokens.
2
0
0
[status] Identified: The issue has been identified and a fix is being implemented.
status.npmjs.org
The issue has been identified and a fix is being implemented.
1
0
2