# Build status is not updating in GitHub **URL:** \ **Category:** Travis CI Discussions & Feedback\ **Created:** [November 8, 2020, 11:20am UTC](https://travis-ci.community/t/build-status-is-not-updating-in-github/10479 "2020-11-08T11:20:38Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![phil-davis](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/phil-davis/32/4852_2.png) [@phil-davis](https://travis-ci.community/u/phil-davis)\ **Post date:** [November 8, 2020, 11:20am UTC](https://travis-ci.community/t/build-status-is-not-updating-in-github/10479/1 "2020-11-08T11:20:38Z")
For example, [https://travis-ci.org/github/sabre-io/vobject/builds/742211391](https://travis-ci.org/github/sabre-io/vobject/builds/742211391) passed, but [https://github.com/sabre-io/vobject/pull/519](https://github.com/sabre-io/vobject/pull/519) has not received the build result. The same problem happened for all the builds today. Is there some problem with either Travis or GitHub today? ---
**Author:** ![phil-davis](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/phil-davis/32/4852_2.png) [@phil-davis](https://travis-ci.community/u/phil-davis)\ **Post date:** [November 8, 2020, 12:12pm UTC](https://travis-ci.community/t/build-status-is-not-updating-in-github/10479/2 "2020-11-08T12:12:29Z")
I tried making PR [https://github.com/sabre-io/vobject/pull/521](https://github.com/sabre-io/vobject/pull/521) from a branch inside the vobject repo. That also passed Travis CI [https://travis-ci.org/github/sabre-io/vobject/builds/742216430](https://travis-ci.org/github/sabre-io/vobject/builds/742216430) but the status on GitHub has not been reported. ---
**Author:** ![native-api](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/native-api/32/430_2.png) [@native-api](https://travis-ci.community/u/native-api)\ **Post date:** [November 8, 2020, 12:28pm UTC](https://travis-ci.community/t/build-status-is-not-updating-in-github/10479/3 "2020-11-08T12:28:12Z")
Looks like a duplicate of > [@GitHub status not posted on commits on repositories using legacy Service integration](https://travis-ci.community/t/github-status-not-posted-on-commits-on-repositories-using-legacy-service-integration/7798/9): > > We have a few more details to share on this subject. In the last couple of weeks, we have observed an increased number of failures to post statuses on GitHub. The sources of the increase itself remains unclear, but the repeated problems prompted us to clean up some wasteful requests. This helped a little, but not entirely; at the height of the user activities, we still saw some errors. We reached out to GitHub, and was granted some additional (but temporary) capacity so that our services can c… Also note > [@Build delays for open source project](https://travis-ci.community/t/build-delays-for-open-source-project/10272/26): > > As was pointed out in [https://travis-ci.community/t/builds-hang-in-queued-state/10250/6](https://travis-ci.community/t/builds-hang-in-queued-state/10250/6) linked to earlier in this topic, Travis is moving workers from [travis-ci.org](http://travis-ci.org) to [travis-ci.com](http://travis-ci.com) in preparation to fully close .org (or rather, make it read-only) around the New Year. [https://docs.travis-ci.com/user/migrate/open-source-repository-migration#frequently-asked-questions](https://docs.travis-ci.com/user/migrate/open-source-repository-migration#frequently-asked-questions) So you need to migrate to .com to stop experiencing delays. Note the caveats: [https://travis-ci.community/t/how-to-migrate-from-…](https://travis-ci.community/t/how-to-migrate-from-org-to-com-in-the-light-of-org-shutting-down/10566/2) ---
**Author:** ![phil-davis](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/phil-davis/32/4852_2.png) [@phil-davis](https://travis-ci.community/u/phil-davis)\ **Post date:** [November 8, 2020, 3:25pm UTC](https://travis-ci.community/t/build-status-is-not-updating-in-github/10479/4 "2020-11-08T15:25:44Z")
The CI status got updated now - [https://travis-ci.org/github/sabre-io/vobject/builds/742216143](https://travis-ci.org/github/sabre-io/vobject/builds/742216143) [https://github.com/sabre-io/vobject/pull/519](https://github.com/sabre-io/vobject/pull/519) It took “a long time” ™ ---
**Author:** ![MysterAitch](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/mysteraitch/32/5532_2.png) [@MysterAitch](https://travis-ci.community/u/MysterAitch)\ **Post date:** [November 11, 2020, 12:09am UTC](https://travis-ci.community/t/build-status-is-not-updating-in-github/10479/5 "2020-11-11T00:09:12Z")
We’re also experiencing this issue, where tests show as green on [travis-ci.org](http://travis-ci.org) but the status indicator on github is still showing as pending (support email sent separately). My first thought is that maybe it’s a repeat of the April api limit issue linked to above, but the status page reports no github problems so perhaps not? Browsing these forums it seems like there might be a few concurrent problems going on – e.g. build queues. It is (currently) unclear to me whether the queuing is part of this though (given that builds have run / completed, just not updated on github).