# Broken link for the diff posted by @letsencrypt\_ops **URL:** \ **Category:** ISRG/Organizational\ **Created:** [April 19, 2018, 6:22pm UTC](https://community.letsencrypt.org/t/broken-link-for-the-diff-posted-by-letsencrypt-ops/59973 "2018-04-19T18:22:58Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![tdelmas](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/tdelmas/32/1866_2.png) [@tdelmas](https://community.letsencrypt.org/u/tdelmas)\ **Post date:** [April 19, 2018, 6:22pm UTC](https://community.letsencrypt.org/t/broken-link-for-the-diff-posted-by-letsencrypt-ops/59973/1 "2018-04-19T18:22:58Z")
Hi, I think there is a bug somewere in the soft used to post on twitter updates from [https://letsencrypt.status.io/](https://letsencrypt.status.io/) : it's not the first time that the link is invalid: [https://twitter.com/letsencrypt\_ops/status/987029551531212801](https://twitter.com/letsencrypt_ops/status/987029551531212801) : > We are updating Boulder to +a1b98d9. Changelog is [https://github.com/letsencrypt/boulder/compare/699c7e4...a1b9](https://github.com/letsencrypt/boulder/compare/699c7e4...a1b9) …... [http://letsencrypt.status.io](http://letsencrypt.status.io) The diff link [https://github.com/letsencrypt/boulder/compare/699c7e4...a1b9](https://github.com/letsencrypt/boulder/compare/699c7e4...a1b9) should be [Comparing 699c7e4...a1b98d9 · letsencrypt/boulder · GitHub](https://github.com/letsencrypt/boulder/compare/699c7e4...a1b98d9) Other tweets with broken link: [https://twitter.com/letsencrypt\_ops/status/979403462365536256](https://twitter.com/letsencrypt_ops/status/979403462365536256) [https://twitter.com/letsencrypt\_ops/status/951618362995490816](https://twitter.com/letsencrypt_ops/status/951618362995490816) ---
**Author:** ![Patches](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/patches/32/17145_2.png) [@Patches](https://community.letsencrypt.org/u/Patches)\ **Post date:** [April 19, 2018, 7:49pm UTC](https://community.letsencrypt.org/t/broken-link-for-the-diff-posted-by-letsencrypt-ops/59973/2 "2018-04-19T19:49:36Z")
This is probably a bug in the [status.io](http://status.io) Twitter posting code, because the links from [letsencrypt.status.io](http://letsencrypt.status.io) do work. (I click on them all the time. 🤓) ---
**Author:** ![tdelmas](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/tdelmas/32/1866_2.png) [@tdelmas](https://community.letsencrypt.org/u/tdelmas)\ **Post date:** [April 19, 2018, 7:53pm UTC](https://community.letsencrypt.org/t/broken-link-for-the-diff-posted-by-letsencrypt-ops/59973/3 "2018-04-19T19:53:29Z")
Yes, the link on [letsencrypt.status.io](http://letsencrypt.status.io) are always correct! I didn’t know if Let’s Encrypt posted the tweet themselves or if [status.io](http://status.io) did it. I pinged them on twitter (I’ll update this thread if they answer) Update: [Broken link for the diff posted by @letsencrypt\_ops](https://community.letsencrypt.org/t/broken-link-for-the-diff-posted-by-letsencrypt-ops/59973/4?u=tdelmas) ---
**Author:** ![tdelmas](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/tdelmas/32/1866_2.png) [@tdelmas](https://community.letsencrypt.org/u/tdelmas)\ **Post date:** [April 20, 2018, 6:52pm UTC](https://community.letsencrypt.org/t/broken-link-for-the-diff-posted-by-letsencrypt-ops/59973/4 "2018-04-20T18:52:39Z")
After a PM, [status.io](http://status.io) responded privately, they confirmed it’s a bug on their end, and said it should be fixed today or tomorrow. ---
**Author:** ![jsha](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/jsha/32/12_2.png) [@jsha](https://community.letsencrypt.org/u/jsha)\ **Post date:** [April 21, 2018, 4:33am UTC](https://community.letsencrypt.org/t/broken-link-for-the-diff-posted-by-letsencrypt-ops/59973/5 "2018-04-21T04:33:22Z")
Thanks for pointing this out, and for resolving it with [status.io](http://status.io)! How great to come to this thread and find it’s solved. 🙂 ---
**Author:** ![isk](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/isk/32/7003_2.png) [@isk](https://community.letsencrypt.org/u/isk)\ **Post date:** [April 23, 2018, 8:06pm UTC](https://community.letsencrypt.org/t/broken-link-for-the-diff-posted-by-letsencrypt-ops/59973/6 "2018-04-23T20:06:30Z")
This is right as we tweeted out to them as well. Thanks for helping out with this and I’m glad to hear they’ve got a solution!