- Level
- confirmed
- Worst impact
- Major outage
- Components
- Coveralls.io Web, Coveralls.io API
- Down Index
- 46of 100
What to do
Check whether you use Coveralls Coveralls.io Web, Coveralls.io API. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 2h 17m it lasted.
Anything that failed between 2024-08-22 19:56 UTC and 2024-08-22 22:13 UTC may need a replay.Subscribe to Coveralls's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=coveralls works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Coveralls 8
- investigating
We have received reports of 500 errors received as responses from the Coveralls API upon coverage report uploads. We are investigating.
provider
- identified
The issue has been identified and a fix is being implemented.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- monitoring
We are continuing to monitor for any further issues.
provider
- monitoring
We will come out of maintenance mode as soon as we confirm the fix.
provider
- monitoring
We are resolving a remaining issue.
provider
- resolved
This incident has been resolved.
provider
- postmortem
**Reason for the incident**: We failed to upgrade to a new RDS CA and update complementary SSL certs on all clients by the expiration date for the previous CA. We misunderstood the potential impact of not making this change in time and planned to make the changes as housekeeping with normal to low priority. In doing so, we failed to prioritize the ticket and make the changes necessary in time to avoid this incident. **Reason for the response time**: While trying to implement the fix, we confronted very verbose documentation that made it hard to understand how to apply the fix in our context, especially while under pressure. When we did identify the correct procedure for our context, and implemented a fix, for some reason we could not get our database clients to establish a connection in production with a freshly downloaded cert that worked in tests from local machines. In the end, we manually copied the contents of the cert into an existing file before our app recognized it. We still don’t know why, but the confusion surrounding this added at least an extra hour to our response time as we cycled through other applicable certs and recovered from failed deployments. **How to avoid the incident in the future**: We will consider all notices from infrastructure providers as requiring review by multiple stakeholders at different levels, and will apply an already established procedure for handling priority infrastructure upgrades in a timely manner, as scheduled events, with review and sign-off.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-1c59d15ce0
Is Coveralls still down?
No, this incident was resolved 2024-08-22 22:13 UTC. For Coveralls's live state, see https://down.guide/coveralls.
How long did it last?
2h 17m, from 2024-08-22 19:56 UTC to 2024-08-22 22:13 UTC, by the times Coveralls posted.
What was affected?
Coveralls named Coveralls.io Web, Coveralls.io API.
What caused it?
Coveralls hasn't published a root cause. If it does, it shows here.
Where does this come from?
Coveralls's official status page, https://status.coveralls.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.