# More reports of “Website under heavy load”

- Provider: [Coveralls](https://down.guide/coveralls)
- Level: confirmed
- Impact: Degraded
- lasted 6h 33m
- started 2025-08-20 15:48 UTC
- Coveralls.io Web, Coveralls.io API
- id: DWN-b4eb9711f0
- Official page: https://stspg.io/4jcpgc1b166l

## Updates from Coveralls
### 2025-08-20 15:48 UTC: investigating
We are currently investigating this issue.

### 2025-08-20 17:11 UTC: investigating
We are continuing to investigate this issue.

### 2025-08-20 17:11 UTC: identified
The issue has been identified and a fix is being implemented.

### 2025-08-20 19:08 UTC: monitoring
A fix has been implemented and we are monitoring the results.

### 2025-08-20 22:21 UTC: resolved
We have implemented an intermediate solution and believe this issue has been resolved for now. To fully resolve the root cause, we will need to implement a more long-term solution, which is currently in design. (Please read postmortem for more information.)
In the meantime, we will be doing our best to monitor for spikes in traffic from outlier repos and manually respond where our intermediate solution may not mitigate as much as we hope it will.

### 2025-08-20 22:22 UTC: postmortem
We believe this issue has been resolved for now.
The underlying cause still appears to be large spikes in incoming Web traffic from other outlier repositories that we have not yet identified or not yet paused.
\*\*Interim Solution\*\*:
To reduce the risk of recurrence, we have applied \_temporary load balancer adjustments\_ that change how requests are distributed, which should \_lower\_—if not \_eliminate\_—the frequency of \*\*503\*\* “\*\*This website is under heavy load\*\*” \*\*errors\*\*.
\*\*Permanent Solution\*\*:
We are also designing a permanent solution to \_rate-limit abnormal request patterns\_. This will require coordination at the policy/SLA level before it can be fully implemented.
In the meantime, we will continue to closely monitor traffic and use targeted load balancer and web server configurations to mitigate the impact of outlier traffic spikes.
\*\*More details\*\*:
For a more detailed assessment / RCA of this incident and its recent, related incidents, see \[this postmortem\](https://status.coveralls.io/incidents/wqbsxnzv0jsf).
\*\*Update \\(Thu, Aug 21\\)\*\*:
We have identified a \*\*different permanent solution\*\*, which does not entail changes to SLA-level details for “outlier repos.” We may still implement such a solution, but our alternative solution should avoid further 503 errors and be implemented in the next 48-72 hrs.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by Sazabi (https://sazabi.com/?utm_source=down-guide&utm_medium=markdown).