[doublepost=1510787683][/doublepost]LTE down in Boston. Able to call using WiFi.
http://downdetector.com/status/att/map/
[doublepost=1510787683][/doublepost]LTE down in Boston. Able to call using WiFi.
Seems Verizon, T-Mobile, and Sprint are having similar issues.[doublepost=1510787683][/doublepost]
http://downdetector.com/status/att/map/
http://downdetector.com/status/att/map/
Restart worked for my wife.
I did just get a text from AT&T that they had upgraded up and down and with in my area. Not the carrier update for Saf but some sort of infrastructure update, I guess. Maybe these two things are related.No carrier update (I'm on 31.0 with iOS 11.2 beta) so that's not it.
Restarting my phone also solved the problem for me
[doublepost=1510788785][/doublepost]Tried restarting iPhone a few times, didn’t work.[/QUOTE
Going on airplane mode worked
Att down
Google docs down
What’s going on?
This looks like a cyber attack.Seems Verizon, T-Mobile, and Sprint are having similar issues.
http://downdetector.com/status/verizon/map/
http://downdetector.com/status/t-mobile/map/
http://downdetector.com/status/sprint/map/
Try toggling Voice over LTE on and off. From an iPhone go to Settings>Cellular>Cellular Data Options>Enable LTE and select Data Only. Make a call. For me it worked and I was able to toggle it back to Voice and Data.Turned airplane mode off/on, rebooted twice & it still didn't work. My son is in the hospital & I am unable to call to get an update.
Try toggling Voice over LTE on and off. From an iPhone go to Settings>Cellular>Cellular Data Options>Enable LTE and select Data Only. Make a call. For me it worked and I was able to toggle it back to Voice and Data.
Hopefully all goes well at the hospital.You're a genius!! It worked!!
Thanks a million!! Very appreciative!
You're a genius!! It worked!!
Thanks a million!! Very appreciative!
Hopefully all goes well at the hospital.
That’s alright. Nobody uses their iPhone to make calls anyway
That didn’t work for me but the following did for me and one other poster here.Thanks, guys. Added a note to the post that a restart is resolving the problem for some users.