Resolved after 29 minutes, affecting Coveralls.io Web and Coveralls.io API, on March 10, 2025.
Performance in terms of latency of background jobs has been restored to normal. The only customers who may continue experiencing latencies are "outlier" customers with builds that exceeded fair use policies earlier this morning. Latencies on the secondary queues we use to process these excess jobs remains at about 40-min. If you wonder whether your latencies were caused by excess usage, reach out to [email protected] and we'll confirm for you either way.
Affected components
Update timeline
- identified Mar 10, 2025, 04:20 PM UTC
We have detected elevated latency during a period of high traffic. We are deploying resources to address and bring those down. ETA ~20-min.
- monitoring Mar 10, 2025, 04:29 PM UTC
We are monitoring the results of scaled resources. ETA 15-20 min.
- resolved Mar 10, 2025, 04:49 PM UTC
Performance in terms of latency of background jobs has been restored to normal. The only customers who may continue experiencing latencies are "outlier" customers with builds that exceeded fair use policies earlier this morning. Latencies on the secondary queues we use to process these excess jobs remains at about 40-min. If you wonder whether your latencies were caused by excess usage, reach out to [email protected] and we'll confirm for you either way.
Your product runs on more than Coveralls
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services