Do Not Glitch the Football Game (or the Drone Swarm)

I used to work at Cisco. When the FCC started talking about killing Net Neutrality, the internet decided this was the end of civilization. People who had never touched a router were certain that without a rule saying every bit must be treated the same, the ISPs would suddenly start censoring their favorite websites and charging extra to load cat videos. They never asked the network engineers what we actually do all day.

Network engineers do not care what is inside the bits. Looking inside the bits is slow, and slow is the original sin. We care about how many bits there are, where they are coming from, and whether the pipes are about to melt. Making the network slower on purpose is a mortal sin. Every piece of “Net Neutrality” legislation still had the escape hatch that let the operator “shape traffic” or practice “reasonable network management.” That clause was not a loophole. It was the admission that the whole premise was unserious. Capacity is finite. Someone has to decide what gets through when everyone wants everything at once.

Back then my former coworkers were building the tools that let the big ISPs actually manage traffic. The reason was simple: BitTorrent. A bunch of nerds had invented a protocol whose entire purpose was to maximize network usage. It was excellent at what it did. It was also a nightmare for anyone running the network. One neighborhood full of people downloading every movie and every piece of porn they would never have time to watch could fill the uplink and make the NFL stream stutter. And you do not glitch American football. If the game breaks, people cancel. The ISPs were not philosophically opposed to free speech or open networks. They were opposed to one protocol eating the entire pipe while the thing that actually paid the bills started dropping frames.

Launching a bunch of drones from a single location is a lot like BitTorrent. Each drone wants a continuous, low-latency video and control stream. Stack enough of them in the same beam, moving fast, and you have concentrated demand that looks exactly like a swarm saturating the available capacity. Starlink and Starshield have finite spectrum, finite satellite power, and finite ability to track terminals that are trying to outrun the beam. When Ukrainian units started reporting that military terminals dropped above roughly 100 mph (with some seeing problems lower), and that strike and interceptor drones lost their links mid-mission, that was not a sudden ideological conversion. It was the network operator noticing that the load profile had changed and applying the same kind of traffic shaping every serious operator has always done.

Physics still does not negotiate. Doppler shift, beam handoff rates, and the geometry of low-Earth-orbit satellites do not care about press conferences. The consumer and standard military terminals people bolt onto drones are not the same hardware as the aviation product. Aviation Starlink uses a dedicated Aero Terminal: larger electronically steered phased-array antenna, higher continuous power draw (typically 60–100 W or more), separate power supply unit, and aircraft-specific certification and mounting. It is built to track satellites while the platform is moving at jet speeds for hours. A Mini or standard dish taped to a drone is a different, cheaper, less capable piece of kit. You do not get the high-mobility performance of the aviation hardware for free just because the satellites are overhead.

Ownership still matters more than slogans. SpaceX built and operates the constellation. The early wartime access that kept Ukrainian units talking was an accommodation, not a property right. When the use case (or the politics, or the capacity) becomes inconvenient, the operator can throttle by speed, geofence, whitelist, or simply decline. They have done versions of this before with Crimea, with long-range strike discussions, and with unauthorized Russian terminals. Complaining that the resulting outages are catastrophic is understandable from the receiving end. It does not change who owns the satellites or who gets to decide the traffic policy.

Net Neutrality was always a crock for the same reason the BitTorrent fights were never really about morality. It pretended the network was a commons that someone else would fund and defend while treating the operator’s need to keep the pipes working as optional. In practice, every network that has ever stayed up has shaped traffic. The legislation always admitted it. The engineers always knew it. The only people who were surprised are the ones who thought “treat all bits the same” was an engineering plan instead of a bumper sticker.

As of October 24, Zelensky and the Ukrainian Defense Ministry say the speeds are back. Monitoring shows stable connections above 400 km/h again, and the president called it the speed they need for frontline logistics and intercepting jet-powered Shaheds. Good for them. But was that a pure policy reversal (Trump calls Musk, dial gets turned), or did SpaceX have to write some software to better handle the concentrated high-mobility drone load without melting the beam? We do not know. What we do know is that the operator still owns the network, the aviation terminals still have the extra hardware for a reason, and the next time a swarm of fast terminals lights up the same cell the dial can move again. Physics and the guy who paid to put the satellites up there both win those arguments. Plan accordingly.

And be nice to your Tech Bros. It's our world now.