# Twitter connection issue

**URL:** <https://forum.beeminder.com/t/twitter-connection-issue/7376>\
**Category:** Bugabee\
**Created:** [October 16, 2020, 4:20pm UTC](https://forum.beeminder.com/t/twitter-connection-issue/7376 "2020-10-16T16:20:31Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![dreev](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.beeminder.com/dreev/32/4311_2.png) [@dreev](https://forum.beeminder.com/u/dreev)\
**Post date:** [October 16, 2020, 7:20pm UTC](https://forum.beeminder.com/t/twitter-connection-issue/7376/5 "2020-10-16T19:20:27Z")

</div>

The email problem is very tentatively resolved:

> [@Beeminder's DNS/email woes (for hardcore sysadminny types only)](https://forum.beeminder.com/t/beeminders-dns-email-woes-for-hardcore-sysadminny-types-only/7377):
>
> The “[beeminder.com](http://beeminder.com)” domain is registered with Namecheap, with DNS pointing to Linode (ns\*.linode.com as nameservers) where we have our zonefiles. We’ve been having rare but ongoing DNS failures, which we now think is Linode’s fault. Last night, it because hair-on-fire acute for a while, with emails to @beeminder.com addresses mostly bouncing: It seems that that was due to the following Linode outage: We’re pretty angry about how consistently flaky Linode has been with DNS so probably @ada…

Also thanks for the nudge to get that outage on [https://twitter.com/beemstat](https://twitter.com/beemstat) – now done!

So back to this Twitter problem: can you ping [support@beeminder.com](mailto:support@beeminder.com) where we can investigate under the assumption that it’s specific to your account at first. Then we can update this thread if it’s a more general bug.

---

_[View the full topic](https://forum.beeminder.com/t/twitter-connection-issue/7376)._
