CloudRepo

CloudRepo Status

Official source
Everything seems OK

Don't miss the next CloudRepo outage!

Get a notification when the status changes! Start your FREE account today!

Sign up with Google or with email

Easily monitor 30 service providers that your business relies on for only $7/month.
Monitor up to 5 services for free.

Stats

0 incidents in the last 7 days

0 incidents in the last 30 days

Automatic Checks

Last check: 1 minute ago

Last known issue: almost 3 years ago

Latest Incidents

Last 30 days

14/04
15/04
16/04
17/04
18/04
19/04
20/04
21/04
22/04
23/04
24/04
25/04
26/04
27/04
28/04
29/04
30/04
01/05
02/05
03/05
04/05
05/05
06/05
07/05
08/05
09/05
10/05
11/05
12/05
13/05
14/05

Resolved API Outage

During a server upgrade, there was approximately 1-2 minutes of API downtime. This was unintentional and we are looking into why this happened so we will avoid future outages in the future as we upgrade hardware.

almost 3 years ago Official incident report

Resolved Package Repository Outage

Customer Impact: Access to our storage APIs (publishing/reading packages) was returning 500 errors for some partners. This is a repeat of the May 9th outage - please refer to the incident summary for more details. Resolution: After we were alerted of this issue we were able to restore functionality to all partners. Duration: Approximately 45 minutes at approximately 11:00 CST and 20 minutes around 18:00 CST. Future Mitigation: To prevent this from happening again, we will be implementing several changes: 1) Improve our monitoring to detect 500 errors as soon as they occur. 2) Increased the size of our cluster to give us more headroom in our connection pools. 3) Continue to investigate root cause and fix anything that may be holding on to connections.

about 3 years ago Official incident report

Resolved Package Repository Outage

Customer Impact: Access to our storage APIs (publishing/reading packages) was returning 500 errors for some partners. Root Cause: Our servers exhausted their connections to the storage layer and our monitoring system did not alert us to this degraded state - a partner alerted us instead. Resolution: After we were alerted of this issue we were able to restore functionality to all partners. Duration: Approximately two hours Future Mitigation: To prevent this from happening again, we will be implementing several changes: 1) Improve our monitoring to detect 500 errors as soon as they occur. 2) Increased the size of our cluster to give us more headroom in our connection pools. 3) Continue to investigate root cause and fix anything that may be holding on to connections.

about 3 years ago Official incident report

Incidents will happen.
You just need to prepare the best for them.

We're monitoring 806 services and adding more every week.

All-in-one platform to check the status of your services

IsDown integrates with hundreds of services. Handles the hassle of going to each one of the status pages and manage it one by one. We also help control how you receive the notifications.
We monitor all problems and outages and keep you posted on their current status in almost real-time.

Get notifications in your favorite communication channel

You can easily get notifications in your email, slack, or use Webhooks and Zapier to introduce the service status in your workflows.


Email
Slack
Slack
Zapier
Zapier

Webhooks

Empower your teams with more data

IsDown collects status data from services to help you be ahead of the game.

Engineering

You already monitor internal systems. Add another dimension (external systems) to your monitoring data and complement it with the external factors.

Customer Support

Know before your clients tell you. Anticipate possible issues and make the necessary arrangements.

Marketing

One of your competitors is down? Maybe a good time to spread the word about your service.

Trusted by teams from all over the world

Services Available
806
Incidents registered
47767
Monitoring Incidents
68

Ready to dive in? Start using IsDown today.

Sign up for free