They say “glitches happen.” But when the FAA grounds the nation, Microsoft’s mail and Teams go dark, and bank apps stall in the same week, we need to stop calling it a coincidence. Newsmax host Carl Higbie is right to shout that these are not just small glitches. They are warning lights flashing over an infrastructure built on brittle wiring, cozy contractor deals, and too-little oversight.
What actually broke: FAA, Microsoft, banks
The FAA ordered a nationwide ground stop after its telecommunications backbone became unstable during a cutover from copper to fiber. FAA Administrator Bryan Bedford described a flood of connection attempts that overwhelmed systems and forced the agency to stop departures. Flight trackers showed thousands of cancellations and many more delays. At the same time, Microsoft reported a major outage affecting Exchange Online and Microsoft 365 services (incident IDs EX1550543 and MO1550821), leaving businesses and workers without email and collaboration tools. Big banks also reported slowdowns and access issues; JPMorgan Chase blamed a technical bug, not an attack.
Why these failures look systemic, not accidental
Carl Higbie’s point is simple: three large, separate systems failed in days, and each failure points to deep problems. The FAA outage traced back to aging telecom links and a contractor cutover (L3Harris is cooperating with probes). Microsoft’s own status updates showed internal health checks and load handling didn’t isolate the failure. Banks’ issues showed how payment and access systems can wobble when back-end services are stressed. Homeland Security Secretary Markwayne Mullin says there’s no evidence of a cyberattack so far, and Transportation Secretary Sean Duffy is asking for major upgrades — but asking is not fixing.
What must change: accountability, redundancy, and real oversight
We can’t paper over this with statements. Congress should hold hearings, the inspector general should dig into contracts and tests, and the DOT should demand clear timelines and penalties from contractors like L3Harris. Microsoft and other cloud giants must publish full post‑incident reports and show they’ll harden systems. Banks need stronger contingency plans and better segmentation so one incident doesn’t ripple across customers. Most of all, federal agencies must stop relying on fragile single points of failure. Modernization funds are fine — if tied to audits, milestones, and real consequences when vendors fail.
Bottom line
Carl Higbie’s tone was blunt because the facts are blunt: when essential systems fail at scale, calling them “glitches” understates the danger. This is about public safety, commerce, and trust. If we want a future where airplanes fly, emails send, and money moves without interruption, we must demand that our leaders and contractors stop treating patches and press releases as fixes. Don’t wait for the next “glitch” to become a national crisis — fix the foundation now.
