Instagram users are finding themselves locked out of their accounts for no apparent reason. Some are even getting a "Sorry, this page isn't available message" when trying to visit their user profile. However, Instagram has blamed a bug for the problems, and promised to fix the issue ASAP.

Like all social networks, Instagram relies on you using it every day. As soon as you stop being active, social networks suffer, and a MySpace-like future beckons. Instagram is showing no signs of collapsing, but preventing people from accessing their accounts certainly isn't going to help.

Help! My Instagram Account Has Been Disabled

Complaints from Instagram users starting popping up online on Thursday (July 6). People were finding themselves locked out of their accounts having been shown one of a handful of error messages. Instagram's social media accounts are full of angry messages from frustrated users.

Some were told they'd had their accounts disabled for violating Instagram's Terms of Use, even though they're sure they haven't broken any rules. Others were prompted to enter their phone number in order to verify their account. But entering the relevant security code didn't work.

Instagram tweeted out an explanation, blaming "a bug that's causing some users to be logged out of their accounts." The company has also promised that it's "working to resolve this as quickly as possible." In the meantime, a small percentage of Instagram users have been locked out of their accounts, and left wondering whether they'll ever actually get back in. And it's still happening.

Call Us Cynical, But...

We really hope this is just a minor bug that Instagram can fix quickly and efficiently. However, with data leaks being revealed years after they occur, and cyberwars masquerading as ransomware, we reserve the right to be cynical about any app exhibiting strange behavior such as this.

Do you have an Instagram account? Have you accessed it over the last few days? If so, has your account been disabled? Do you buy Instagram's explanation that this is all down to a bug? Or do you think there's more going on here? Please let us know in the comments below!