This is a bit scary…
Verizon Wireless failed to connect around 10,000 calls to 911 during the Jan. 26 snowstorm that blanketed Maryland, according to the FCC, and the agency has requested that the carrier provided a detailed account of what went wrong and what the carrier plans to do to fix it. Importantly, the FCC said it is worried the problem may not be limited to the area, and instead is “widespread across Verizon’s footprint.”
Verizon noted the issue involves the company’s wireline division, although the FCC said the problem specifically involved wireless callers.
“We have taken seriously the concerns about the outage that was triggered by the mass call event that occurred during the January 26th snowstorm. We have been addressing this issue directly with the counties involved, and will work cooperatively to address the FCC’s questions, as well,” said Verizon spokesman Harry Mitchell. “Our objective is to provide the best service to our customers, and we will continue to work with 911 centers and others to ensure that callers receive the level of service they deserve and expect when they call 911.”
James Barnett, chief of the FCC’s Public Safety and Homeland Security Bureau, sent Verizon a letter Feb. 17 detailing the problem, which he said blocked 8,300 wireless calls to 911 in Montgomery County, Maryland, and 1,700 calls to 911 in Prince George’s County, Maryland, on Jan. 26. Barnett wrote that Verizon’s system stopped taking 911 calls during the snowstorm and did not alert the local 911 answering stations about the problem. He noted that 911 workers only discovered the problem after they received complaints from callers.
Barnett said the trouble was not due to an overload of the system or faulty equipment, and that similar troubles have occurred in the area a number of times before.
“We are particularly concerned that this problem may be widespread across Verizon’s footprint,” Barnett wrote. “We therefore request that Verizon investigate the extent of the problem across its network.”
The FCC requested that Verizon respond to the issue by March 10.
– see this FCC document