Is Coveralls GitHub down?
Current Coveralls GitHub status is UP

Update - The backed up queue affecting all users has drained by 75%. Our fix is still being deployed across all servers, but should start taking effect in the next 15-20 min. Apr 04, 2024 - 20:38 PDT

Investigating - Several customers have reported long delays receiving status updates for new builds at GitHub, or status updates that have hung and never arrived. We are investigating the issue.If you are experiencing this issue, please reach out and let us know at support@coveralls.io so we can include your cases in our investigation.Note that there were some incidents receiving API requests at GitHub in the last 24 hrs, per this status update from GitHub: https://www.githubstatus.com/incidents/gqj5jrvzjb5hWe evaluating cases against this timeframe to understand if they align with the GitHub incident period. Apr 04, 2024 - 13:00 PDT

Investigating - Re-opening this incident from yesterday, THU, APR 14, since we are receiving more reports this morning:> We are getting reports of Github status updates not arriving at Github for repos that have been fine in this regard for a long time. We are noticing an uptick in background job failures responsible for these status updates. In most cases, these failures resolve immediately by re-trying them. But some fail a few times before succeeding. We suspect there's an issue with the Github API (though not according to https://www.githubstatus.com/), or an isolated issue between coveralls.io and github.com, that's resulting in behavior like rate limiting. There is no known basis for actual rate limiting, but this is the effect.>> Please know that any failing status updates will be retried in exponential back-off fashion (so they should eventually succeed) and that we are monitoring closely and will take any action we can to improve things. Apr 15, 10:20 PDT

Monitoring - We are getting reports of Github status updates not arriving at Github for repos that have been fine in this regard for a long time. We are noticing an uptick in background job failures responsible for these status updates. In most cases, these failures resolve immediately by re-trying them. But some fail a few times before succeeding. We suspect there's an issue with the Github API (though not according to https://www.githubstatus.com/), or an isolated issue between coveralls.io and github.com, that's resulting in behavior like rate limiting. There is no known basis for actual rate limiting, but this is the effect. Please know that any failing status updates will be retried in exponential back-off fashion (so they should eventually succeed) and that we are monitoring closely and will take any action we can to improve things. Apr 14, 13:24 PDT