When a major event goes viral on Threads, you may see the error message “Couldn’t send reply” after tapping the post button. This happens because the Threads servers cannot process your reply fast enough when thousands of users are posting at the same time. The error is not a problem with your account or internet connection. This article explains why the error occurs and gives you several practical fixes to get your reply posted.
Key Takeaways: Fixing Threads Reply Errors During Traffic Spikes
- Wait 10–15 seconds before retrying: Server load drops quickly; a short pause often lets the reply go through.
- Restart the Threads app: Force-closing and reopening the app clears a stuck request queue.
- Use a cellular data connection instead of Wi-Fi: Cellular networks can bypass congested ISP routes to Threads servers.
Why Threads Shows “Couldn’t Send Reply” During High Traffic
Threads runs on servers that handle millions of requests every second. When a breaking news event, a sports final, or a celebrity post goes viral, the number of reply attempts spikes far above normal levels. The server may accept your reply request but cannot process it before the connection times out. This timeout triggers the “Couldn’t send reply” message on your screen.
The error is not caused by your account being blocked or your internet being slow. It is a server-side capacity issue. Threads uses a queuing system that drops requests when the queue gets too long. Your reply text is still saved in the app’s local memory, but the server never confirmed receipt.
Some users see this error even when their internet connection is fast. That is because the delay happens at Meta’s servers, not on your device. The app shows the error after waiting a few seconds for a server response that never arrives.
Steps to Fix “Couldn’t Send Reply” on Threads
Try these fixes in order. Stop after each step and attempt to send your reply again.
- Wait 15 seconds and tap Retry
When the error appears, do not close the app. Wait 15 seconds. Then tap the Retry button that appears below the error message. The server load may have dropped enough to accept your reply. - Copy your reply text before closing the error
Highlight your reply text and copy it to the clipboard. Then close the error message. Tap the text field again and paste the reply. Tap the Send button. This works because the app sends a fresh request instead of retrying the old failed request. - Force-close and reopen the Threads app
On Android, open Settings > Apps > Threads > Force Stop. On iPhone, swipe up from the bottom of the screen and hold, then swipe the Threads card up. Reopen Threads. Navigate back to the post and send your reply again. - Switch from Wi-Fi to cellular data
Turn off Wi-Fi on your phone. Use your mobile data plan. Open Threads and try to send the reply again. Cellular data sometimes routes through different internet exchange points that are less congested. - Clear the Threads app cache on Android
Open Settings > Apps > Threads > Storage > Clear Cache. This removes temporary data that may be causing the app to reuse a failed request. Your login and drafts are not affected. - Update the Threads app to the latest version
Open the Google Play Store or Apple App Store. Search for Threads. If an Update button appears, tap it. Updated versions often include server-side retry logic that handles high traffic better. - Wait 2 minutes and try again from scratch
If none of the above work, wait 2 full minutes. Then open Threads, find the post, type your reply, and tap Send. The traffic spike may have subsided in that time.
If the Error Appears on Every Post
If you see “Couldn’t send reply” on every post and not just during viral events, the issue is likely on your end. Check your internet connection by loading a web page in your browser. If pages load slowly, restart your router or contact your internet provider. Also check if Threads is down for everyone by visiting downdetector.com and searching for Threads.
Other Reply Errors That Look Similar
“Something went wrong. Please try again.”
This generic error appears when the server rejects the request for a reason other than high traffic. The most common cause is that your reply contains a link or word that Threads flagged as spam. Remove any links from your reply and try again. If the error persists, simplify the reply to plain text.
“You are unable to reply to this post.”
This message means the post’s author has restricted replies. The author may have limited replies to people they follow or to accounts with a verified badge. You cannot fix this from your side. Move on to another post.
“Reply not sent. Check your connection.”
This error indicates a local network problem rather than a server issue. Restart your phone’s Wi-Fi or enable Airplane Mode for 10 seconds and then disable it. If the error persists, try the cellular data switch described above.
Threads Reply Error: High Traffic vs. Account Issue Comparison
| Item | High Traffic Error | Account or Network Issue |
|---|---|---|
| Error message | “Couldn’t send reply” | “Something went wrong” or “Check your connection” |
| When it occurs | During viral events only | On every reply attempt |
| Root cause | Server overload from many users | Blocked account, spam filter, or bad internet |
| Best fix | Wait 15 seconds and tap Retry | Restart app or check network |
| Account action needed | None | May need to appeal a block or update app |
The “Couldn’t send reply” error during high traffic events is almost always temporary. The fixes above work because they either wait for the server load to drop or force the app to send a new request instead of repeating a failed one.
If you frequently post during viral events, turn on Threads notifications for the accounts you follow. When you see a post immediately after it is published, you can reply before the traffic spike hits. Also consider writing your reply in a notes app and pasting it into Threads after the first attempt fails. This saves you from retyping the text.
For persistent reply failures that happen outside of high traffic, check your account status in Settings > Account. If your account is flagged for spam, follow the on-screen instructions to verify your identity. Most reply errors are resolved within a few minutes without any action from the account owner.