A word on the today's disruption, what you need to do and where I'm headed. TLDR: You need to reconnect X, Bluesky and probably Youtube to avoid failed posts Today, Beplan was down. Completely. This is not the quality of service I want, even more disruptions as severe as today. I've been able to find the root cause: a capacity issue with our database. Its resources had been maxed out for a few days and today it hit its limit. That meant token refreshes weren't processing correctly, and some scheduled posts took longer than they should have to save. 🚨 One thing I need from you: Please reconnect your social accounts, especially X/Twitter, Bluesky and probably Youtube. Because token refreshes were disrupted, some connections may be stale, and reconnecting now prevents failed posts going forward. Another thing: I'd been wanting to fix this properly since February. The plan was to move our database to infrastructure I fully control, and that also put Beplan entirely under European (and specifically French 🇫🇷) data sovereignty. Today's incident turned out to be the perfect moment to do it. Since tokens weren't refreshing anyway for short-lived-token platforms like X, the usual risk that makes this migration painful was off the table. So I pulled the trigger and did the move today. What this means for you: Beplan is now much faster. One heavy request that used to take ~2s now runs in under 100ms. What this means for Beplan: I now own the full infrastructure, so I can monitor everything properly and catch problems before they reach you. I'll be working on this in the next few weeks. Real data sovereignty makes Beplan a genuinely stronger, locally-rooted alternative to foreign platforms and from here I want to grow it into something meaningful for small businesses and down the line institutions too. Thanks for bearing with me today and sorry again for the huge disruption.