debbiemum

Thank you for your response.

I appreciate your explanation of how the plugin connection works and that Smash Balloon uses Meta’s approved API. However, I remain concerned because the sequence of events was too specific and too consistent across all three accounts to dismiss as coincidence without further investigation.

To clarify the timeline:

• Three separate websites were migrated to a new server on the same day.
• All three websites used Smash Balloon to display Instagram/Facebook content.
• Following the migration, each website displayed the decryption/reconnection error.
• I began following the reconnection process for one Instagram account only.
• During that process, Instagram requested verification and then disabled the account.
• When I subsequently checked the other two Instagram accounts, I discovered that they had also been disabled, despite me not having attempted to reconnect them.

This is why I am struggling to reconcile what happened with the explanation provided.

You mention that “signing into several Instagram accounts in a short window from a brand new server or location can trip Instagram’s automated security checks.” However, I had not signed into or reconnected all three accounts when the issue occurred. I only attempted the process on one account before discovering that all three had already been disabled.

My concern is therefore not simply that Instagram made a decision independently, but whether there is any interaction between the Smash Balloon reconnection workflow, the server migration, Meta’s API, or Instagram’s automated security systems that could explain why three separate accounts became disabled at effectively the same time.

Given these circumstances, I would appreciate answers to the following:

1. Have you received any other reports of Instagram accounts being restricted, suspended or disabled immediately following a server migration and subsequent Smash Balloon reconnection requirement?
2. Have you investigated whether the Error 999/decryption issue or its recovery process can trigger security events within Meta’s systems?
3. Are there any known cases where multiple accounts connected to the same user, business, Meta account, or IP address have been flagged following a reconnection event?
4. Is there any logging available that would show precisely what requests were made from the plugin and when?

I appreciate that Smash Balloon cannot reinstate accounts and that only Instagram can do so. However, given that three separate accounts were disabled in close proximity to the reconnection issue, I believe it is reasonable to ask whether similar incidents have been reported and whether the matter can be reviewed by a member of your technical team.

I would be grateful if this could be escalated accordingly.