Tsunami Warning mistakenly sent to phones

Share

A bogus tsunami warning caused a flood of Tuesday morning confusion along the East Coast.

The message appears to have been conveyed through third-party apps, perhaps including Accuweather, not the USA government's wireless and broadcast emergency alert systems.

But if the user clicked through to the full message in some cases, the alert did say "This message is for test purposes only".

The alert popped up as a phone notification for many mainly on the East Coast through weather apps like Accuweather.

Borel posted a Facebook item that named Patterson as included in the tsunami warning.

Molleda, who emailed reporters within an hour of the alert, said his office received several calls to confirm the information. The US National Weather Service and the Federal Communications Commission said they were investigating the false alarm.

Days after the Hawaii warning, a Japan broadcaster mistakenly sent a text-message alert.

"We understand the reason for test messages, but we feel that NWS consider failsafe measures for the future to prevent such an occurrence", AccuWeather CEO Barry Myers wrote to the weather service, adding the system is "less than flawless".

"But knowing a tsunami warning is usually preceded by seismic activity really made me have second thoughts", Borel said.

The AccuWeather gaffe comes just weeks after residents of Hawaii were sent into a panic after a false alert was sent out informing them that a ballistic missile was heading straight for their island. "We will update you when we find out more", the NWS wrote, according to The Patch. It was just a Tsunami test message.

The NWS sent out an alert around 8:30 a.m. stating there was one in effect.

And social media was quick to point out the similarities in Tuesday's tsunami warning. Had hen been a live warning the Emergency Alerts System and Wire Emergency Alert system would have been activated in addition to all other outlets similar to a Tornado Warning.

AccuWeather had warned the weather service about incorrectly coded emergency messages after a similar problem in 2014.

Share