Coveralls is in Read Only mode while we work on updating the system. Sorry for the inconvenience.
VIGILANCE! Check this page any time you notice a problem with coveralls
Recent GitHub incident may affect Coveralls users
Incident
Report for Coveralls
Resolved
Because of how closely tied Coveralls is to GitHub for our GitHub users, Coveralls users will have experienced some follow-on issues from the GitHub incident yesterday:
https://www.githubstatus.com/incidents/zjchv3zvfg50
For instance, we received a few reports yesterday of failed logins with the error message: “Sorry, there was a GitHub server error. Please try again shortly.”
In addition to this, it seems that other issues at GitHub related to the same incident may have caused other unusual behavior, including (temporarily) missing source files.
If you think you may have been affected by such issues, please check the GitHub status report to help determine if these GitHub issues were the cause:
https://www.githubstatus.com/incidents/zjchv3zvfg50
And of course please reach out and we’ll help you determine if that, or something else, is the cause.
https://www.githubstatus.com/incidents/zjchv3zvfg50
For instance, we received a few reports yesterday of failed logins with the error message: “Sorry, there was a GitHub server error. Please try again shortly.”
In addition to this, it seems that other issues at GitHub related to the same incident may have caused other unusual behavior, including (temporarily) missing source files.
If you think you may have been affected by such issues, please check the GitHub status report to help determine if these GitHub issues were the cause:
https://www.githubstatus.com/incidents/zjchv3zvfg50
And of course please reach out and we’ll help you determine if that, or something else, is the cause.
This incident affected: Coveralls.io Web and GitHub.