# Twitter @letsencrypt\_ops integration broken?

**URL:** <https://community.letsencrypt.org/t/twitter-letsencrypt-ops-integration-broken/128648>\
**Category:** Site Feedback\
**Created:** [July 16, 2020, 9:00pm UTC](https://community.letsencrypt.org/t/twitter-letsencrypt-ops-integration-broken/128648 "2020-07-16T21:00:48Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![cpu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/cpu/32/84514_2.png) [@cpu](https://community.letsencrypt.org/u/cpu)\
**Post date:** [July 16, 2020, 9:00pm UTC](https://community.letsencrypt.org/t/twitter-letsencrypt-ops-integration-broken/128648/1 "2020-07-16T21:00:48Z")

</div>

👋 Hi folks,

Is the [@letsencrypt\_ops](https://twitter.com/letsencrypt_ops) Twitter integration broken or maybe stuck? I notice there hasn't been an update posted by the account since [the July 2nd](https://twitter.com/letsencrypt_ops/status/1278765814947037186) release.

If I check [status.io](https://status.letsencrypt.org) I can see there was a deploy announcement on the status page for [July 7th](https://letsencrypt.status.io/pages/maintenance/55957a99e800baa4470002da/5f07503a1bc3b004bb011f46) that doesn't seem to have a matching tweet from @letsencrypt\_ops.

It doesn't look like the missing July 7th deploy was reverted or otherwise skipped, because production Boulder is [currently reporting](https://acme-v02.api.letsencrypt.org/build) a commit hash/build date from the 7th that matches the status page update:

> Boulder=( +cb06fe8 Wed Jul 8 01:38:25 UTC 2020)

Could someone check if there's something jamming up the status page -\> twitter integration? cc [@staff](https://community.letsencrypt.org/groups/staff)

Thanks!

---

<div class="post-metadata">

**Author:** ![andygabby](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/andygabby/32/15876_2.png) [@andygabby](https://community.letsencrypt.org/u/andygabby)\
**Post date:** [July 17, 2020, 9:42pm UTC](https://community.letsencrypt.org/t/twitter-letsencrypt-ops-integration-broken/128648/2 "2020-07-17T21:42:10Z")

</div>

Thanks for the report @cpu!

I’ll check the integration. It’s possible it is not working.

I checked the [status.io](http://status.io) history, it is possible the check mark wasn’t selected to tweet the updates but I can’t find that [status.io](http://status.io) let’s me see if it was or not.

**Update** : While writing this there was a Cloudflare DNS outage that let us test our Twitter integration and it looks to be working (at least now). I’ll keep an eye on it for next deploy.

---

<div class="post-metadata">

**Author:** ![cpu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/cpu/32/84514_2.png) [@cpu](https://community.letsencrypt.org/u/cpu)\
**Post date:** [July 17, 2020, 9:55pm UTC](https://community.letsencrypt.org/t/twitter-letsencrypt-ops-integration-broken/128648/3 "2020-07-17T21:55:58Z")

</div>

> [@andygabby](#):
>
> **Update** : While writing this there was a Cloudflare DNS outage that let us test our Twitter integration and it looks to be working (at least now). I’ll keep an eye on it for next deploy.

Thanks! Best of luck weathering the Cloudflare outage.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [August 16, 2020, 9:56pm UTC](https://community.letsencrypt.org/t/twitter-letsencrypt-ops-integration-broken/128648/4 "2020-08-16T21:56:00Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.