Coveralls Incident History

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We will be undergoing scheduled maintenance at this time. We do not expect to use the full window. We will close the window / post when complete.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We will be undergoing staged infrastructure migration described here:https://status.coveralls.io/incidents/ph6p14vg1fyr

This incident has been resolved.

We are continuing to monitor for any further issues.

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring the results.

We are continuing to work on a fix for this issue.

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

We are continuing to investigate this issue.

We are currently investigating this issue.

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring the results.

We are continuing to work on a fix for this issue.

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

We are continuing to investigate this issue.

We are currently investigating this issue.

We are currently investigating this issue.

We are continuing to investigate this issue.

We are currently investigating this issue.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We will be undergoing major infrastructure maintenance related to an infrastructure upgrade in progress for many weeks. We apologize for the length of this maintenance window, but it is absolutely crucial that we give ourselves enough time to complete this effort without new data coming into the system.

A fix has been implemented and we are monitoring the results.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We will be undergoing infrastructure upgrades and maintenance during this window.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We will be performing what we hope is the last of several weekends of database infrastructure maintenance this weekend. Due to the complexity of the remaining tasks, we have created a longer-than-normal maintenance window of eight (8) hours running from Saturday night at 8pm PDT to Sunday morning at 4a PDT. We apologize for any inconvenience this may cause customers working on projects over the weekend. For those customers, we advise as follows:- During this work, Coveralls will be in maintenance mode, and requests to our API, like coverage report uploads will be rejected. - To avoid this breaking your CI builds with step failures, users of our official integrations can enable the following "Do not fail on error" settings:"Do not fail on error" settings:1. `fail-on-error: false` for Coveralls GitHub Action2. `fail_on_error: false` for Coveralls Orb for CircleCI3. `--no-fail` flag for Coveralls Universal Coverage ReporterNote that in cases (1) and (2), both CI extensions are ultimately passing the `--no-fail` flag to Coverage Reporter, which is our main integration running under-the-hood of both CI extensions (Action & Orb).