Showing posts with label East Coast. Show all posts
Showing posts with label East Coast. Show all posts

Friday, September 27, 2024

East Coast port strike looms for first time since 1977


Here's what to know.

By Kate Gibson

Edited By Alain Sherter

Updated on: September 26, 2024 / 11:41 PM EDT / CBS News


Thousands of dockworkers at every major East and Gulf coast port are girding to strike starting early next week, threatening to close trade gateways that handle about half of all goods shipped in containers in and out of the U.S.

Negotiations between the union representing dockworkers and a shipping industry group representing terminal operators and ocean carriers have been stalled for months, with both sides this week issuing conflicting statements about their willingness to bargain.


The United States Maritime Alliance (USMX) has filed an unfair labor practice with the National Labor Relations Board requesting "immediate injunctive relief — requiring the union to resume bargaining — so we can negotiate a deal," the alliance said Thursday.


The NLRB confirmed it had received the unfair labor practice charge, which is being docketed by its regional office in Newark, New Jersey. The charge will appear on the agency's website in the next few days, after which an investigation would begin.

Experts say a shutdown could severely hamper the flow of goods and raise shipping costs. Any spike in such expenses could be passed on to consumers just as U.S. inflation normalizes, and even potentially hinder the Federal Reserve as it finally pivots to lowering interest rates.

Here's what to know about the labor fight, which would be the first mass work stoppage at eastern ports in nearly half a century.
What are the key issues in the labor dispute?

The union representing 45,000 dockworkers, the International Longshoremen's Association (ILA), is threatening to strike at ports from Massachusetts to Texas if a new labor deal with the USMX isn't reached before the current contract expires at midnight on September 30. A walkout would be the first East Coast dock strike since 1977.

A total of 14 ports involving some 25,000 workers could be affected by the strike, according to USMX: Baltimore; Boston; Charleston, South Carolina; Jacksonville, Florida; Miami; Houston; Mobile, Alabama; New Orleans; New York/New Jersey; Norfolk, Virginia; Philadelphia; Savannah, Georgia; Tampa, Florida; and Wilmington, Delaware.

Saturday, February 10, 2018

False alarms highlight weaknesses in national alert system









Weather junkie John Grosso knew it was highly unlikely a monster wave was barreling toward the Connecticut coast. Still, when a tsunami warning appeared out of the blue on his phone Tuesday, he felt a twinge of fear. His co-workers, who got the same alert, asked whether they should evacuate.

It turned out to be a false alarm, a computer glitch. The damage? An erosion of trust.

“Now I have to check every single time, God forbid, there’s a tornado warning, a tsunami alert, pick your poison,” said Grosso, 25, a social media manager from Stamford. “I have to look at it and go, ‘Is it a test? Was it sent in error?’ And I could be wasting precious time in case it was real.”

Last month’s bogus ballistic missile warning in Hawaii and, now, this week’s tsunami snafu have highlighted trouble spots and prompted calls for change in the nation’s increasingly complex system for alerting Americans about dangerous weather, active shooters, kidnapped children, plant explosions and other emergencies.

Both incidents have prompted calls for reform, including better training for emergency workers in charge of sending alerts.

More than 1,000 federal, state and local government agencies have the ability to issue emergency alerts through an array of federally managed communications networks. It is a patchwork system that usually works as intended but can wreak havoc when it doesn’t.

In the Senate, legislation introduced this week in response to the false missile alert would establish standards for state and local agencies’ participation in the national alert system, require federal certification of their incident management systems, and recommend steps for avoiding false alarms.

Additionally, the Federal Communications Commission has ordered wireless providers to do a better job of targeting emergency alerts to only those in the affected area, with a geographic “overreach” of no more than one-tenth of a mile.

Aside from the false alarms, emergency agencies have been criticized for sending alerts to too many people or too few. In Alaska, for instance, a tsunami warning triggered by an undersea earthquake in January reached residents of Anchorage even though the city wasn’t in danger. In Northern California wine country, where wildfires killed dozens of people in October, some residents complained that authorities failed to send an emergency alert to their phones.

“The emergency alerting system is really a whole collection of systems, and there are various places where it can break down,” said Dan Gonzales, a scientist at RAND Corp. who studies emergency alert systems. “With so many organizations involved, it’s difficult to make it foolproof.”

The risk of too many false alarms, Gonzales said, is that “people will ignore warnings if they believe they’re not accurate or not relevant.”

That was on vivid display Tuesday when AccuWeather, the private forecasting service, took what was intended to be a routine, monthly National Weather Service test message and sent it as a real warning to subscribers up and down the East Coast, the Gulf of Mexico and the Caribbean.

Katia Del Negro, 33, was at home in New York City when she got the alert, her surprise quickly turning to skepticism.

“I definitely got a bit concerned when I saw that many people along the East Coast received the alert,” she said. “But at the same it seemed so weird, so I thought something was off, thinking back about what happened in Hawaii not long ago.”

AccuWeather, based in State College, Pennsylvania, blamed the weather service, saying the government agency miscoded the test message. That caused the company’s computers to interpret it as real and push it to subscribers’ cellphones, according to AccuWeather.

The weather service insisted its message was coded properly.

Daryl Herzmann, a systems analyst in the agronomy department at Iowa State University, said the message contained a “T″ flag, indicating test. But the weather service also recycled a tracking number it used in a previous tsunami warning, probably confusing AccuWeather’s computers, he said.

The weather service has been recycling tracking numbers for years, said Herzmann, who runs an environmental data project that compiles information from the weather service.

Weather service spokeswoman Susan Buchanan had no comment on Herzmann’s observation. She pointed to an earlier statement that said the agency is “working with private sector companies to determine why some systems did not recognize the coding.”

It was human error, not a computer problem, that caused last month’s panic in Hawaii. A state worker mistook a drill for a missile attack and sent an emergency alert to cellphones and broadcast stations. It took nearly 40 minutes for the Hawaii Emergency Management Agency to figure out a way to retract the alert. The worker was fired and the agency chief resigned.

“This cry of wolf damaged the credibility of alert messaging, which can be dangerous when a real emergency occurs,” Lisa Fowlkes, an FCC official, said Tuesday during a House committee hearing on the nation’s emergency messaging system.

Jeremy DaRos, of Portland, Maine, who lives near the water and got the erroneous tsunami alert, said he is concerned that people won’t take seriously the emergency alerts they get in an actual crisis.

“People need to trust the alerts they’re pushing out,” he said. “This is important stuff, and to have two incidents in the span of a month is just unacceptable.”




Friday, October 21, 2016

WHAT WE KNOW ABOUT FRIDAY’S MASSIVE EAST COAST INTERNET OUTAGE





AUTHOR: LILY HAY NEWMAN.LILY HAY NEWMAN SECURITY

DATE OF PUBLICATION: 10.21.16.10.21.16

TIME OF PUBLICATION: 1:04 PM.1:04 PM



GETTY IMAGES



FRIDAY MORNING IS prime time for some casual news reading, tweeting, and general Internet browsing, but you may have had some trouble accessing your usual sites and services this morning and throughout the day, from Spotify and Reddit to the New York Times and even good ol’ WIRED.com. For that, you can thank a distributed denial of service attack (DDoS) that took down a big chunk of the Internet for most of the Eastern seaboard.

This morning’s attack started around 7 am ET and was aimed at Dyn, an Internet infrastructure company headquartered in New Hampshire. That first bout was resolved after about two hours; a second attack began just before noon. Dyn reported a third wave of attacks a little after 4pm ET, and called the overall situation a “very sophisticated and complex attack” stemming from tens of millions of IP addresses. In all cases, traffic to Dyn’s Internet directory servers throughout the US—primarily on the East Coast but later on the opposite end of the country as well—was stopped by a flood of malicious requests disrupting the system. Still ongoing, the situation is a definite reminder of the fragility of the web, and the power of the forces that aim to disrupt it.