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
Update - After 1-hour of monitoring, we are cautiously optimistic that service is fully restored in all regions.
Feel free to confirm service in your area (with thanks): ops@coveralls.io
And please let us know if you are still having any issues: support@coveralls.io
We will continue to monitor throughout the rest of the day, and weekend.
Finally, please come back for our post-mortem. We are aiming for Mon, Mar 2, but of course our priority is making sure service is stable and getting back to those of you who contacted us directly.
For all of the kindness and support, we thank you.
To everyone, thanks for your patience. We'll be in touch.
Feb 27, 2026 - 12:23 PST
Feel free to confirm service in your area (with thanks): ops@coveralls.io
And please let us know if you are still having any issues: support@coveralls.io
We will continue to monitor throughout the rest of the day, and weekend.
Finally, please come back for our post-mortem. We are aiming for Mon, Mar 2, but of course our priority is making sure service is stable and getting back to those of you who contacted us directly.
For all of the kindness and support, we thank you.
To everyone, thanks for your patience. We'll be in touch.
Feb 27, 2026 - 12:23 PST
Update - We would love to hear from anyone outside of the US as to whether service has been restored for you: ops@coveralls.io
We have no reason to believe service hasn't been restored to all regions, but we want to make sure.
We will continue monitoring.
Feb 27, 2026 - 11:19 PST
We have no reason to believe service hasn't been restored to all regions, but we want to make sure.
We will continue monitoring.
Feb 27, 2026 - 11:19 PST
Update - We are back, for at least some users.
We’ll stay at “partial outage” until we confirm full restoration.
Feb 27, 2026 - 11:11 PST
We’ll stay at “partial outage” until we confirm full restoration.
Feb 27, 2026 - 11:11 PST
Update - We are seeing systems coming back online. We assume service has been restored at some level.
We will assess and update you here ASAP.
Feb 27, 2026 - 11:02 PST
We will assess and update you here ASAP.
Feb 27, 2026 - 11:02 PST
Update - Day 3 | Morning
Status: Unresolved — No ETA
It's the morning of Day 3, and service has still not been restored. We want you to know we're here, fully aware, and have not stopped working on this.
We remain in constant communication with our hosting provider's account team, who we have every reason to believe is continuing to advocate for us internally. But the reality remains the same: we do not have an ETA, and we do not have direct control over the outcome we need: restoration of our services and access to our infrastructure.
As we pass milestones in this outage that we never imagined we would see (and haven't in 15 years of operation) the path forward is becoming clearer. We need to find a new provider, at minimum for failover, and potentially as our primary host. We've been reading the tweets, watching the YouTubes, and evaluating options. But if anyone in a position similar to ours has migrated away from a primary tier host and successfully manages a write-intensive service with hundreds of thousands of daily uploads, we would genuinely love to hear from you about your experience. Please reach out: ops@coveralls.io
Because if our services are not restored by the end of today, we will be standing up new infrastructure over the weekend.
We will continue to post updates as we have them.
Feb 27, 2026 - 07:41 PST
Status: Unresolved — No ETA
It's the morning of Day 3, and service has still not been restored. We want you to know we're here, fully aware, and have not stopped working on this.
We remain in constant communication with our hosting provider's account team, who we have every reason to believe is continuing to advocate for us internally. But the reality remains the same: we do not have an ETA, and we do not have direct control over the outcome we need: restoration of our services and access to our infrastructure.
As we pass milestones in this outage that we never imagined we would see (and haven't in 15 years of operation) the path forward is becoming clearer. We need to find a new provider, at minimum for failover, and potentially as our primary host. We've been reading the tweets, watching the YouTubes, and evaluating options. But if anyone in a position similar to ours has migrated away from a primary tier host and successfully manages a write-intensive service with hundreds of thousands of daily uploads, we would genuinely love to hear from you about your experience. Please reach out: ops@coveralls.io
Because if our services are not restored by the end of today, we will be standing up new infrastructure over the weekend.
We will continue to post updates as we have them.
Feb 27, 2026 - 07:41 PST
Update - Day 2 | Evening
Status: Unresolved — No ETA
We want to be transparent with you: after two full days of working directly with our hosting provider’s account team, we still do not have an ETA for service restoration. Despite having internal sponsorship within our provider’s organization, we have been unable to get the traction needed to resolve what appears to have been an automated action, one that no one on their side has taken ownership of causing or fixing.
We understand the severity of this disruption. Your CI workflows depend on Coveralls, and we can see the impact this outage is having on your teams. That is not lost on us for a single moment.
This experience has made something painfully clear: no matter how trusted or established a cloud provider may be, a single vendor dependency without a failover plan is an unacceptable risk, for us and for you. We are already evaluating backup infrastructure options to ensure that nothing like this can take our service offline this way again. We’ll share more in our full postmortem.
In the meantime, to those of you who have stayed patient and stuck with us through this, thank you. We see you, we appreciate you, and we are committed to making this right. If there is anything we can do to help in the interim, please reach out.
We will continue to post updates as we have them.
Feb 26, 2026 - 17:13 PST
Status: Unresolved — No ETA
We want to be transparent with you: after two full days of working directly with our hosting provider’s account team, we still do not have an ETA for service restoration. Despite having internal sponsorship within our provider’s organization, we have been unable to get the traction needed to resolve what appears to have been an automated action, one that no one on their side has taken ownership of causing or fixing.
We understand the severity of this disruption. Your CI workflows depend on Coveralls, and we can see the impact this outage is having on your teams. That is not lost on us for a single moment.
This experience has made something painfully clear: no matter how trusted or established a cloud provider may be, a single vendor dependency without a failover plan is an unacceptable risk, for us and for you. We are already evaluating backup infrastructure options to ensure that nothing like this can take our service offline this way again. We’ll share more in our full postmortem.
In the meantime, to those of you who have stayed patient and stuck with us through this, thank you. We see you, we appreciate you, and we are committed to making this right. If there is anything we can do to help in the interim, please reach out.
We will continue to post updates as we have them.
Feb 26, 2026 - 17:13 PST
Update - As of 6am PST Thu, Feb 26, we are still waiting on restoration. We thought this would be resolved by this morning. We are in touch with our account team and are doing what we can to restore service. We apologize for the ongoing inconvenience.
Feb 26, 2026 - 06:53 PST
Feb 26, 2026 - 06:53 PST
Update - 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.
Feb 25, 2026 - 17:56 PST
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.
Feb 25, 2026 - 17:56 PST
Update - We are continuing to communicate with our hosting provider around any updates or ETA.
Feb 25, 2026 - 09:49 PST
Feb 25, 2026 - 09:49 PST
Monitoring - 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.
Feb 25, 2026 - 09:48 PST
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.
Feb 25, 2026 - 09:48 PST
Update - 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`
Feb 24, 2026 - 19:28 PST
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`
Feb 24, 2026 - 19:28 PST
Identified - The issue has been identified and a fix is being implemented.
Feb 24, 2026 - 17:36 PST
Feb 24, 2026 - 17:36 PST
Update - We are continuing to investigate this issue.
Feb 24, 2026 - 14:58 PST
Feb 24, 2026 - 14:58 PST
Investigating - We are currently investigating this issue.
Feb 24, 2026 - 14:52 PST
Feb 24, 2026 - 14:52 PST
Coveralls.io Web
Operational
Coveralls.io API
Operational
GitHub
Operational
Travis CI API
Operational
Pusher Presence channels
Operational
Pusher WebSocket client API
Operational
Stripe API
Operational
New Relic Metric API : US
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance