Software bug caused CBP airport system outage

A computer system outage that led to long passenger lines at international airports across the country on Aug. 19 was caused by a software bug, according to Customs and Border Protection.

Long lines at Miami International Airport during a TECS outage in 2017

Miami International Airport passengers lined up to await processing during a 2017 CBP outage.

The nationwide outage on Aug. 16 of Customs and Border computer systems that processed international travelers at airports across the U.S. was caused by a software bug that hit in the wake of a system update, the agency said.

The outage, which hit airports from New York's John F. Kennedy International, O'Hare International in Chicago and Washington D.C.'s Dulles International and others from coast-to-coast resulted in long lines for passengers at the facilities on a busy summer Friday.

In a statement to FCW on Aug. 19, a CBP spokesperson said the systems it uses to process international travelers "experienced a temporary outage that resulted in an impact to passenger processing at CBP ports of entry nationwide."

The outage resulted in long lines, but its personnel still had access to security databases for passenger screening. The agency, said the spokesperson, ruled out a cybersecurity threat or incident as a cause.

In its initial troubleshooting to determine what caused the outage, CBP said it was potentially a problem with application connection failures in some of its databases.

The agency had to sequentially restart "multiple CBP application servers" to restore service after about two and a half hours, the spokesperson said.

A four-hour outage of the CBP's IT system in January 2017 was also linked to a failed technology upgrade, according to an oversight report published in November 2017. In that outage, CBP had to route data requests from the modernized TECS system to the legacy TECS mainframe.

In their report, the Department of Homeland Security Office of Inspector General identified multiple system weaknesses including "inadequate CBP software capacity testing" and "deficient software maintenance" and "inadequate business continuity and disaster recovery capabilities to minimize the impact of system failures on the traveling public."

The report concluded that CBP "lacks a means to minimize the possibility and impact of similar system outages in the future."

NEXT STORY: Can EIS stay on schedule?