# 503 Service Unavailable / no healthy upstream **URL:** \ **Category:** Support\ **Created:** [July 20, 2022, 8:53pm UTC](https://community.codecov.com/t/503-service-unavailable-no-healthy-upstream/3762 "2022-07-20T20:53:10Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![tobyink](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/tobyink/32/2541_2.png) [@tobyink](https://community.codecov.com/u/tobyink)\ **Post date:** [July 20, 2022, 8:53pm UTC](https://community.codecov.com/t/503-service-unavailable-no-healthy-upstream/3762/1 "2022-07-20T20:53:10Z")
## Before submitting a topic, please confirm the following I have searched for similar issues before creating this topic. I have verified that my repository is using the [Codecov GitHub app](https://github.com/apps/codecov), if using GitHub I have [validated](https://docs.codecov.com/docs/codecov-yaml#validate-your-repository-yaml) my `codecov.yaml` configuration file. I have filled out the below sections to the best of my ability. ### Description Uploading coverage fails with this error: ```auto 503 Service Unavailable no healthy upstream ``` The endpoint being uploaded to is: [https://codecov.io/upload/v2](https://codecov.io/upload/v2) ### CI/CD URL [https://github.com/tobyink/p5-type-tiny/runs/7435610591](https://github.com/tobyink/p5-type-tiny/runs/7435610591) ### Expected Results Something more like this: [https://github.com/tobyink/p5-type-tiny/runs/7404544285](https://github.com/tobyink/p5-type-tiny/runs/7404544285) ### Actual Results ```auto 503 Service Unavailable no healthy upstream ``` … and the results don’t appear on the codecov website. ### Additional Information Started failing consistently about 36 hours ago. ---
**Author:** ![willgearty](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/willgearty/32/2063_2.png) [@willgearty](https://community.codecov.com/u/willgearty)\ **Post date:** [July 20, 2022, 9:38pm UTC](https://community.codecov.com/t/503-service-unavailable-no-healthy-upstream/3762/2 "2022-07-20T21:38:19Z")
I’m getting the same issue with my R repo: [Add badges to README.md · palaeoverse-community/palaeoverse@ed9f984 · GitHub](https://github.com/palaeoverse-community/palaeoverse/actions/runs/2707803182). Other R developers are also getting the same issue: [`covr::codecov()` upload to codecov.io fails with 503 error · Issue #512 · r-lib/covr · GitHub](https://github.com/r-lib/covr/issues/512). ---
**Author:** ![willgearty](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/willgearty/32/2063_2.png) [@willgearty](https://community.codecov.com/u/willgearty)\ **Post date:** [July 21, 2022, 3:08pm UTC](https://community.codecov.com/t/503-service-unavailable-no-healthy-upstream/3762/3 "2022-07-21T15:08:42Z")
Looks like this might be resolved? The codecov [status page](https://status.codecov.com/) lists multiple SSL issues over the last couple days which I’m guessing are to blame. ---
**Author:** ![tobyink](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/tobyink/32/2541_2.png) [@tobyink](https://community.codecov.com/u/tobyink)\ **Post date:** [July 21, 2022, 8:54pm UTC](https://community.codecov.com/t/503-service-unavailable-no-healthy-upstream/3762/4 "2022-07-21T20:54:53Z")
I’d temporarily disabled [codecov.io](http://codecov.io) uploads on my repos (which is not a major issue as I am also using [Coveralls.io](http://Coveralls.io) — they provide slightly different statistics, so I find it useful to have both). I’ll re-enable it and see what happens. ---
**Author:** ![tobyink](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/tobyink/32/2541_2.png) [@tobyink](https://community.codecov.com/u/tobyink)\ **Post date:** [July 21, 2022, 8:57pm UTC](https://community.codecov.com/t/503-service-unavailable-no-healthy-upstream/3762/5 "2022-07-21T20:57:59Z")
Success! Now I need to figure out how to mark this issue as resolved.