[EAS] Cell Phone Warning Failure
Sean Donelan
sean at donelan.com
Tue Jun 27 13:11:44 CDT 2017
Emergency officials are blaming a "technical glitch," but don't know what
that technical glitch was.
I wonder if two different warnings got picked up? There isn't a "full"
feed channel out of IPAWS, so its difficult to tell if a different alert
channel (EAS, WEA, NWEM, Public) had another message. Or a mobile carrier
had a tower geo-location mistake and broadcast the message from many
towers?
I don't see a Riverside County, CA evacuation IPAWS message on the
IPAWS EAS channel feed.
Douglas County, Washington issued a fire warning around 8:28 p.m. for a
fire near Palisades Rd. It was correctly coded 053017 (Douglas County).
The polygon box appears reasonable in Douglas County. No complaints in
the State of Washington.
On Mon, 26 Jun 2017, Adrienne Abbott wrote:
> Oops...
> Courtesy KVVU Fox 5 Las Vegas.
>
> LVFR: Text msg alerting T-Mobile and Metro PCS customers to evacuate sent to Vegas customers incorrectly. Only meant for Riverside, CA area
>
> 5 minutes ago
>
> undefined
> LVFR: A text message alerting T-Mobile and Metro PCS customers to evacuate because of a fire was sent to Las Vegas customers incorrectly. It was only meant for Riverside County, California area residents.
> Several calls were placed to Las Vegas Fire and Rescue regarding these messages, according to PIO Tim Szymanski.
> Copyright 2017 KVVU (KVVU Broadcasting Corporation). All rights reserved.
>
> Adrienne
>
> __________________________________________________________
> The EAS Forum Discussion List is hosted by the BWWG (Broadcast Warning Working Group). http://eas.radiolists.net
> Please invite your friends to join our Forum! The sign up is at: http://lists.radiolists.net/mailman/listinfo/eas
> ___________________________________________________________
>
More information about the EAS
mailing list