DENVER -- An apparent nationwide AT&T outage that affected calls made to 911 emergency centers -- including here in Denver -- has been resolved.
Issue has been resolved that affected some calls to 911 from wireless customers. We apologize to those who were affected.
— AT&T (@ATT) March 9, 2017
The Denver Police Department tweeted out Wednesday evening that if you were trying to reach police using an AT&T phone "your call may not go through."
DPD officials advised followers to call (720) 913-2000 then push "1" to reach an emergency communications operator.
Officers with Denver police then tweeted his helpful how-to guide if you needed to get in contact with police for an emergency situation via text:
HOW TO TEXT 911: pic.twitter.com/IdeEa2cOUt
— Denver Police Dept. (@DenverPolice) March 9, 2017
Lakewood Police also reached to the community via Twitter, asking people to call another line or text 911 if they needed help.
911 calls by AT&T mobile customers are not going through, call 303-987-7111 or text 911 if you need help.
— Lakewood Police (@LakewoodPDCO) March 9, 2017
Aurora police also tweeted out alternate phone numbers even though tests done in the area did not find any issues.
However, if you are AT&T customer and have problems reaching 911 in Aurora, call nonemergency line at 303.627.3100 to reach dispatch. 2/2
— City of Aurora, CO (@AuroraGov) March 9, 2017
Arvada PD, Boulder County, Garfield County, Douglas County, Eagle River Fire and Vail police also tweeted out numbers people could call in case of an emergency.
The problem was not only felt in several parts of Colorado. Law enforcement agencies in Texas, Florida, Tennessee and Washington, D.C., sent out tweets alerting the community of the outage, according to The Washington Post.
The states of Indianapolis, Georgia and New York were also affected.
An AT&T spokesperson released the following statement following reports across the country:
"We are aware of a service issue affecting some calls to 911 for wireless customers and we’re working to resolve it as quickly as possible. We apologize for this inconvenience."
The issue was resolved at around 8:30 p.m.