Number of Incidents
1 outages
Since last incident
30 days
Stay on top of outages with IsDown with real-time notifications and overview dashboards. Monitor the official status pages of all your vendors, SaaS, and tools, including Coveralls.
Minor · 30 days ago · lasted about 5 hours
Processing delays for repos with 5K+ source files
We've seen a spike in build times for large repos (5K+ source files). Right now, only nine (9) repos seem to be affected. We have implemented a fix and are monitoring as build times return to normal for these repos. The root cause of this spike is elevated jobs (and therefore dequeue times) in queues dedicated to large repos which appears to have been triggered by two (2) repos sending an unusually high number of uploads over the past 1-3 hr period. We have increased resources to these queues to accelerate processing but may need to pause the above repos if uploads continue at the same level. If you think your repo was affected you can reach out to us at support@coveralls.io. We will reach out to the owners of the repos with elevated jobs.
Minor · about 1 month ago · lasted about 3 hours
We're receiving reports of slow builds due to slow dequeue times for background jobs. We are investigating and will update status here.
Minor · 2 months ago · lasted about 21 hours
We have had two reports of intermittent `403` errors this morning. We are investigating and will post updates here. If you are having this issue, please reach out to us at support@coveralls.io so we can add you to the ticket.
Major · 3 months ago · lasted about 2 hours
Some users report not being able to login to coveralls.io. The behavior is a circular redirection landing on a Reauthorization required screen with error message: > This application has made an unusually high number of requests to access your account. Please reauthorize the application to continue. If you are experiencing this issue, please let us know at support@coveralls.io.
Minor · 3 months ago · lasted 1 day
Issue affecting coverage details for some repos (Fix being implemented)
Internal testing today revealed an issue with some repos, in which coverage calculations and data for particular builds show obviously large, incorrect drops in coverage and/or missing coverage data. We have identified the root cause of the issue and a fix is being implemented. If you are wondering whether you are affected by this issue, know that, once we've resolved the issue, we will re-run as many affected builds as we can identify, but feel free to check in at support@coveralls.io and we will verify and make sure your build are recalculated.
Minor · 4 months ago · lasted about 22 hours
Drop in coverage for some parallel pull_request builds
After a recent release, we have received reports of `pull_request` builds that have suddenly dropped in coverage with no change in CI setup. Specifically, these builds have had several parallel jobs and now, suddenly, have only one build. We are aware of the issue, have identified the root cause, and are working on a fix. We will update this incident when status changes.
“If you are in SRE, IT, or Security and work in an environment with a lot of SaaS (which, let's face it, is all of them) - IsDown is your new best friend. Helpfully aggregates various Statuspages from services into a very clear dashboard. Worth every penny.”
“Your support is one of the best I have ever worked with. Thanks for having a great product AND great support.”
Get notified only when an outage impacts a certain component.
IsDown monitors Coveralls, and also its competitors (also 2500 other cloud services). Check the current status of the most popular alternatives to Coveralls.
The data and notifications you need, in the tools you already use.
SaaS rules the world, and all teams depend on them to do their most productive work. IsDown helps you monitor all your cloud services, so you can focus on what matters.
Try it out! How much time you'll save your team, by having the outages information close to them?