Service outage

After a full day of working with our hosting provider's account team (who've been really helpful), we've discovered that this outage stems from an account restriction that, by all indications, shouldn't have happened (we believe the technical term is "snafu"). They are actively working to get it reversed.

This is not a technical failure — our infrastructure and all customer data are fully intact. Services will be restored as soon as account access is.

We're hopeful for resolution this evening or tomorrow morning. We'll have more to say once we're back online.

We are continuing to communicate with our hosting provider around any updates or ETA.

We are experiencing an outage that appears to have originated at our infrastructure provider. We are unable to access our account and are working with our account manager to resolve the issue. Unfortunately, due to the nature of the incident, we have no way to establish an ETA.

We are doing everything we can to restore service, and will update our status page as soon as we have a fix or an ETA.

Please follow along here:
https://status.coveralls.io/

You can subscribe for email updates by clicking SUBSCRIBE TO UPDATES button in the top right corner of this page.

Outage will be extended for at least several more hours.

To avoid further disruption to your CI workflows, we recommend employing the fail-on-error: false input option available with all official coveralls integrations.

See: https://docs.coveralls.io/integrations#official-integrations.

Official Integration: fail-on-error option
- GitHub Action: `fail-on-error: false`
- CircleCI Orb: `fail_on_error: false`
- Coverage Reporter (CLI): `--no-fail`

The issue has been identified and a fix is being implemented.

We are continuing to investigate this issue.

We are currently investigating this issue.