Meta's Threads API started returning server errors on the step where we exchange an authorization code for an access token. That step is what runs when you connect a Threads account to Buffer, so while it was failing, new connections couldn't complete. Accounts that were already connected weren't affected.

Customer impact

If you tried to connect a Threads account to Buffer between roughly 03:25 and 05:23 UTC on 16 June, the connection most likely failed with a "Looks like we've hit a snag" message.

Threads accounts you'd already connected kept working, and posting to Threads carried on as normal. This only hit new connections. Two customers wrote in about it.

Key learnings

One thing we'd love to improve is how fast we can detect issues like this from our own monitoring systems, so that we can communicate when issues start sooner next time. We've planned a few improvements around this!