Follow the recent outages and downtime for NPM Package publishing in the table below.
Start Time |
Type |
Length |
Message |
Details |
|||||
---|---|---|---|---|---|---|---|---|---|
December 08, 2023 19:14 UTC |
WARN |
about 1 hour |
Issue installing and publishing private packages |
See more
|
|||||
September 27, 2023 21:59 UTC |
WARN |
about 2 hours |
Degraded performance when publishing packages |
See more
|
|||||
September 27, 2023 15:59 UTC |
WARN |
about 1 hour |
Degraded performance when publishing packages |
See more
|
|||||
September 25, 2023 20:39 UTC |
WARN |
about 21 hours |
Degradation of service when trying to access private packages |
See more
|
|||||
July 25, 2023 21:04 UTC |
WARN |
5 minutes |
Increased error rate in both npmjs.org and npmjs.com |
See more
|
|||||
2024-05-03 12:07:37 UTC UTC |
STATUS |
? minutes |
Sign in to view more status history. |
See more | |||||
2024-05-03 12:07:37 UTC UTC |
STATUS |
? minutes |
Sign in to view more status history. |
See more | |||||
2024-05-03 12:07:37 UTC UTC |
STATUS |
? minutes |
Sign in to view more status history. |
See more | |||||
2024-05-03 12:07:37 UTC UTC |
STATUS |
? minutes |
Sign in to view more status history. |
See more | |||||
2024-05-03 12:07:37 UTC UTC |
STATUS |
? minutes |
Sign in to view more status history. |
See more |
Sign Up for More NPM Package publishing History
StatusGator has over 8 years of NPM Package publishing status history.
NPM Package publishing status, last 24 hours:
Up: 24 hours
Warn: 0 minutes
Down: 0 minutes
Maintenance: 0 minutes
We've been monitoring NPM Package publishing outages since October 7, 2015.
Here's the history of service outages we've observed from the NPM Package publishing Status Page:
NPM Package publishing is a Development solution that StatusGator has been monitoring since October 2015. Over the past over 8 years, we have collected data on on more than 562 outages that affected NPM Package publishing users. When NPM Package publishing publishes downtime on their status page, they do so across 6 components using 4 different statuses: up, warn, down, and maintenance which we use to provide granular uptime metrics and notifications.
More than 100 StatusGator users monitor NPM Package publishing to get notified when it's down, is under maintenance, or has an outage. This makes it one of the most popular development services monitored on our platform. We've sent more than 9,100 notifications to our users about NPM Package publishing incidents, providing transparency and peace of mind. You can get alerts by signing up for a free StatusGator account.
If NPM Package publishing is having system outages or experiencing other critical issues, red down notifications appear on the status page. In most cases, it means that core functions are not working properly, or there is some other serious customer-impacting event underway.
Warn notifications are used when NPM Package publishing is undergoing a non-critical issue like minor service issues, performance degradation, non-core bugs, capacity issues, or problems affecting a small number of users.
NPM Package publishing posts separate notifications for planned maintenance work. StatusGator will notify subscribers when NPM Package publishing enters a pre-planned maintenance window, keeping you up to date.
Since NPM Package publishing publishes a feed of proactive maintenance events on their status page, StatusGator will collect information about these events. Maintenance events for all your services can be viewed within StatusGator as a unified feed.
When NPM Package publishing posts issues on their status page, we collect the main headline message and include that brief information or overview in notifications to StatusGator subscribers.
When NPM Package publishing has outages or other service-impacting events on their status page, we pull down the detailed informational updates and include them in notifications. These messages often include the current details about how the problem is being mitigated, or when the next update will occur.
Because NPM Package publishing has several components, each with their individual statuses, StatusGator can differentiate the status of each component in our notifications to you. This means, you can filter your status page notifications based on the services, regions, or components you utilize. This is an essential feature for complex services with many components or services spread out across many regions.
Can’t find your question? Email us to arrange a time to discuss. We’d love to chat!
Are you experiencing issues with NPM Package publishing? Sign up to receive notifications when NPM Package publishing publishes outages.
NPM Package publishing Down or not working? Never be taken by surprise again.
StatusGator tells you when your cloud services have problems or their statuses change. We monitor the official status pages of more than 3,580 cloud services in real-time, aggregate the data, and send you alerts via email, Slack, Teams, SMS, and more.
Looking for recent downtime and outages of NPM Package publishing?
Sign up for StatusGator and see all historical information about NPM Package publishing outages and performance issues. Get free, instant notifications when NPM Package publishing goes down.