06-12-2018 6:18 PM
06-14-2018 12:59 PM
Hey there @airwricka,
Thank you for visiting our Community Forums. Having your device unlocked can definitely be important. I understand the website wasn't working properly. I’d be happy to guide you through some steps to request an unlock. Lets go ahead and attempt to submit this request again. Our Device unlock portal provides all of the eligibility requirements as well. Please ensure your device meets all of these requirements before moving forward with the request:
*Your device isn't reported lost or stolen, or involved with fraud.
*You must complete your contract or installment plan (including early termination fees). Or, pay off an installment plan early and then make another unlock request in 24 hours.
*Your device isn't active on another AT&T account.
*If you upgraded early, wait 14 days to unlock your old device. Business customers wait 30 days. Your service must be active for at least 60 days with no past due or unpaid balance.
*AT&T PREPAID℠ (formerly GoPhone®) devices must have at least 6 months of active service.
*If you're military, we'll ask you to email your TCS or PCS (Temporary / permanent change of station) documents for eligibility. You won't have to complete installment plans or contracts.
*If you have a business-owned device, your company must authorize you to unlock
I hope this helps! Have a wonderful rest of the day.
Jess, AT&T Community Specialist
06-15-2018 2:29 PM
hello I mistakenly typed a wrong IMEI number but it went through the confirmation page. I thought the website was back up but then when I applied again with the correct IMEI number, it still says that the site is experiencing network difficulties. So, I tried that wrong IMEI number just to be sure the site was okay and then it went through the confirmation page! I asked my uncle who gave me his IPhone 6+ who already has an iPhone X. He went personally to At&T and was advised to go through the unlock process again online. Still doesn’t work.
06-15-2018 3:47 PM
Thank you for letting us know! If this is someone else's device, please have them contact us so we can make sure the device is 100% eligible for an unlock.
Your time is very much appreciated, and I hope you have a great rest of the day.
Jess, AT&T Community Specialist
11-04-2018 11:56 AM
I too am getting the same message for an iPhone 6 that was paid off 3 years ago. Please do NOT replay with the canned message spread across the forum. This has been going on for the last 5 hours.
12-07-2018 6:33 PM
portal still returns "Oops! Looks like we're having network difficulties. Try again later." I would really like to unlock this iPhone 6 that I replaced over a year ago. It is paid off and not on any other network. Still has its original sim card. I want to use it in Europe with a different network/sim. I'm running out of time. att store will not unlock it. They say they "can't.". Suggest I keep trying the portal and seem surprised it is broken (for more days and weeks?!). Or they will accept it as a trade in for $50-60 credit (but how will they unlock it?! haha). I think they just don't want me to use the phone on another network.
In the past I have successfully used the portal to unlock a 5s that I sold to a friend. That went smoothly. What is annoying is that the error message seems to be misleading. I cannot believe that a network company is having network difficulties unresolved for weeks and months. I'm not a conspiracy theorist, but this is ridiculous. Seems designed to make people give-up. Perhaps it is time to move the whole family and our five active devices to Verizon.
12-13-2018 2:03 AM
I submitted an unlock request and successfully confirmed it by clicking the link in the confirmation email. 42 hours later I received this:
"Looks like you didn't confirm your request.
- edited 12-13-2018 12:31 PM
I am getting similar behavior today JakesOnline... unlock request confirmed (after a few of the network errors) but email received right-away, clicked and then it complained that it was only good for 24 hours. trying again all day and only get the 'network error' now...