SpaceX’s satellite internet service, Starlink, is now up and running throughout the White House campus. This move marks a significant expansion of the government’s Wi-Fi network since Elon Musk came aboard as an unpaid adviser during Trump’s administration.
The exact timeline of Starlink’s installation within the White House complex remains unclear following Trump’s re-election. Instead of placing Starlink’s terminals—rectangular panels capturing satellite internet signals—right on the White House grounds, signals are rerouted through a nearby data center via existing fiber cables.
According to White House officials, this setup aims to boost internet coverage on the premises. Some areas reportedly struggle with cell service, and the current Wi-Fi system is stretched thin.
Karoline Leavitt, the White House press secretary, stated the mission is simply “to improve Wi-Fi connectivity on the complex.” However, this situation is unique compared to previous internet service solutions. Musk, now a “special government employee,” maintains control over Starlink despite concerns about potential conflicts of interest due to his company’s ties with federal agencies.
In February, Chris Stanley—a security engineer with SpaceX and another of Musk’s ventures—surveyed the Eisenhower Executive Office Building’s rooftop for Starlink installation. The visit turned eventful when an alarm was triggered, summoning the Secret Service. While Stanley had prior clearance to check the rooftop, a formal schedule was never set, leading to unexpected drama.
Harrison Fields, another White House spokesperson, downplayed the incident as a security concern, a stance echoed by Anthony Guglielmi of the Secret Service. The White House claims Starlink’s internet was donated, a contribution vetted by its legal team in charge of ethics.
Some former officials question the feasibility of such a donation. Clare Martorana, a previous chief information officer during the Biden administration, emphasized that technology gifts to the government typically require thorough approval to ensure security.
Stanley collaborated with the White House IT team to integrate Starlink into the existing system while consulting for both the White House and the Justice Department.
Besides the White House, Starlink has been rolled out at the General Services Administration, echoing Musk’s governmental efficiency drive. While federal agencies usually depend on Starlink during emergencies or in remote locations, its application in Washington’s well-connected federal buildings raises eyebrows.
Starlink is regarded as a robust network, as demonstrated during relief efforts in North Carolina post-Hurricane Helene and Ukraine’s defense against Russian aggression—aiding efforts costing SpaceX $400 million over a year.
Still, questions linger about its ability to improve wireless capacity in a fiber-opulent environment like federal buildings. Moreover, the encryption status of Starlink communications remains uncertain, though it reportedly creates a separate network accessible only from White House grounds.
Cybersecurity expert Jake Williams noted that replacing existing government-sanctioned infrastructure with Starlink is “super rare,” pointing out the potential security risks of such an implementation.
Concerns about Starlink’s integration into Washington’s secure hardwiring have been mitigated by rerouting through a different data hub, alleviating initial apprehensions from the Secret Service.
The General Services Administration has integrated Musk’s technologies, including apps from SpaceX and Tesla, onto its approved list for mobile devices. The agency reassures that only apps meeting their security standards are allowed but declined further comment on their Starlink usage.
Musk has expressed dissatisfaction with what he perceives as outdated government technology. His push for modernization in the White House saw Stanley tasked with refining WAVES, the digital system managing visitor clearance. Although Secret Service discussions with Musk’s team are ongoing, no definitive changes have been made to the visitor access protocol.
Reporting contributions were made by Jonathan Swan and Tyler Pager.
