# Account Disabled but not actually disabled...?

**URL:** <https://mpsocial.com/t/account-disabled-but-not-actually-disabled/82754>\
**Category:** Instagram Marketing\
**Created:** [September 3, 2019, 3:06pm UTC](https://mpsocial.com/t/account-disabled-but-not-actually-disabled/82754 "2019-09-03T15:06:23Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![Duncan.Music](https://mpsocial.com/user_avatar/mpsocial.com/duncan.music/32/28270_2.png) [@Duncan.Music](https://mpsocial.com/u/Duncan.Music)\
**Post date:** [September 3, 2019, 3:06pm UTC](https://mpsocial.com/t/account-disabled-but-not-actually-disabled/82754/1 "2019-09-03T15:06:23Z")

</div>

This morning I got my first ever “ACCOUNT DISABLED” on one of my client accounts. Never had it happened, and started freaking out. Looked on the [instagram.com](http://instagram.com) url and saw that it is still up. Even logged in manually and the page is still up and working. Even appears in the search.

Is this a false error on the software side? Was it disabled then reenabled? Anyone seen something like this before?

Any recommendations on automation etc. like changing proxy, resetting device ID, letting it rest for a day?

Thanks!

---

<div class="post-metadata">

**Author:** ![socialgain](https://mpsocial.com/user_avatar/mpsocial.com/socialgain/32/36263_2.png) [@socialgain](https://mpsocial.com/u/socialgain)\
**Post date:** [September 3, 2019, 3:12pm UTC](https://mpsocial.com/t/account-disabled-but-not-actually-disabled/82754/2 "2019-09-03T15:12:07Z")

</div>

Did you talk to the client yet?  
Did he notice something?

---

<div class="post-metadata">

**Author:** ![roishalev1995](https://mpsocial.com/letter_avatar_proxy/v4/letter/r/278dde/32.png) [@roishalev1995](https://mpsocial.com/u/roishalev1995)\
**Post date:** [September 3, 2019, 3:19pm UTC](https://mpsocial.com/t/account-disabled-but-not-actually-disabled/82754/3 "2019-09-03T15:19:52Z")

</div>

Seems to me like a mistake in the program, but not sure… Wait for more people

---

<div class="post-metadata">

**Author:** ![Duncan.Music](https://mpsocial.com/user_avatar/mpsocial.com/duncan.music/32/28270_2.png) [@Duncan.Music](https://mpsocial.com/u/Duncan.Music)\
**Post date:** [September 3, 2019, 3:22pm UTC](https://mpsocial.com/t/account-disabled-but-not-actually-disabled/82754/4 "2019-09-03T15:22:00Z")

</div>

Was once I loaded the software I saw in red ACCOUNT DISABLED I immediately typed in [Instagram.com/Username](http://Instagram.com/Username) and was still up, I logged in from my phone and no issue following/liking/etc., I reset Device IDs, changed proxies, EB couldn’t log in “Sorry there was a problem logging you in please try again soon” logged in using API got APIBLOCK added @ to username, Invalid credentials, Removed and Reverified in API, VALID now. Stopped all tools, will restart tomorrow. Hopefully not a ban…

---

<div class="post-metadata">

**Author:** ![EYS](https://mpsocial.com/user_avatar/mpsocial.com/eys/32/43327_2.png) [@EYS](https://mpsocial.com/u/EYS)\
**Post date:** [September 3, 2019, 3:24pm UTC](https://mpsocial.com/t/account-disabled-but-not-actually-disabled/82754/5 "2019-09-03T15:24:20Z")

</div>

Same thing happened to me with a client account last week. MP says account is disabled but it definately is not

---

<div class="post-metadata">

**Author:** ![Duncan.Music](https://mpsocial.com/user_avatar/mpsocial.com/duncan.music/32/28270_2.png) [@Duncan.Music](https://mpsocial.com/u/Duncan.Music)\
**Post date:** [September 3, 2019, 3:24pm UTC](https://mpsocial.com/t/account-disabled-but-not-actually-disabled/82754/6 "2019-09-03T15:24:54Z")

</div>

Did you see any issues moving forward? Did you continue tools or rest?

---

<div class="post-metadata">

**Author:** ![EYS](https://mpsocial.com/user_avatar/mpsocial.com/eys/32/43327_2.png) [@EYS](https://mpsocial.com/u/EYS)\
**Post date:** [September 3, 2019, 3:26pm UTC](https://mpsocial.com/t/account-disabled-but-not-actually-disabled/82754/7 "2019-09-03T15:26:42Z")

</div>

I rested the account for 3 days and since then it has been working fine. I also freaked out and thought I might as well quit this IG game if clients start having their accounts disabled but it seems it is a MP bug. A bug which could probably give you a heart attack…

---

<div class="post-metadata">

**Author:** ![Duncan.Music](https://mpsocial.com/user_avatar/mpsocial.com/duncan.music/32/28270_2.png) [@Duncan.Music](https://mpsocial.com/u/Duncan.Music)\
**Post date:** [September 3, 2019, 3:27pm UTC](https://mpsocial.com/t/account-disabled-but-not-actually-disabled/82754/8 "2019-09-03T15:27:46Z")

</div>

Yeah I freaked out…Never had a client account disabled and wasnt even doing anything crazy. Could IG have disabled then reenabled it accidentally?

---

<div class="post-metadata">

**Author:** ![denis1](https://mpsocial.com/user_avatar/mpsocial.com/denis1/32/34057_2.png) [@denis1](https://mpsocial.com/u/denis1)\
**Post date:** [September 3, 2019, 3:30pm UTC](https://mpsocial.com/t/account-disabled-but-not-actually-disabled/82754/9 "2019-09-03T15:30:06Z")

</div>

God. I will be more carefull when i’ll see a DISABLED in the software now,

😮

---

<div class="post-metadata">

**Author:** ![EYS](https://mpsocial.com/user_avatar/mpsocial.com/eys/32/43327_2.png) [@EYS](https://mpsocial.com/u/EYS)\
**Post date:** [September 3, 2019, 3:32pm UTC](https://mpsocial.com/t/account-disabled-but-not-actually-disabled/82754/10 "2019-09-03T15:32:02Z")

</div>

Highly unlikely because I checked the account within 30 minutes of it being “disabled”
