SpaceX launched 27 more of its Starlink internet satellites to orbit today (Sept. 6).
The spacecraft rode to low Earth orbit (LEO) atop a Falcon 9 rocket, which lifted off from California's Vandenberg Space Force Base at 10:26 a.m. EDT (1426 GMT; 7:26 a.m. local California time). The Falcon 9 rose into blue morning skies — something of a rarity for California's central coast, which is often cloaked in fog.
The Falcon 9's first stage came back to Earth as planned 8.5 minutes later, landing in the Pacific Ocean on the SpaceX drone ship "Of Course I Still Love You."
A SpaceX Falcon 9 rocket launches 27 Starlink satellites into orbit from Vandenberg Space Force Base in California on Sept. 6, 2026. (Image credit: SpaceX)
It was the 19th flight for this particular booster, which is designated B1088. This marks about the halfway point to the SpaceX record of 37 flights, which was set by B1067 during a Starlink launch on Aug. 25.
The Falcon 9's upper stage, meanwhile, carried the 27 Starlink satellites to LEO, deploying them on schedule 62 minutes after launch.
SpaceX's sooty Falcon 9 rocket first stage on the drone ship Of Course I Still Love You in the Pacific Ocean after a successful launch and landing on Sept. 6, 2026. (Image credit: SpaceX)
Today's launch was the 103rd Falcon 9 mission of 2026. Eighty of those flights have been dedicated to building out the Starlink megaconstellation, by far the largest satellite network ever assembled. It currently consists of more than 11,000 active spacecraft, according to astronomer and satellite tracker Jonathan McDowell.
Starlink missions fly exclusively out of Vandenberg these days. SpaceX used to launch them from Florida as well, but the company recently put those missions on hold until it gets its Starship megarocket up and running on the Space Coast.
SpaceX will rely on Starship to launch its next-gen Starlink V3 satellites, which are bigger and more capable than the current V2. The company wants to assemble a network of about 100,000 Starlink V3s in LEO, Elon Musk has said.
No rocket had ever reached orbit from Western European soil — until today.
The German company Isar Aerospace launched its Spectrum rocket from Andøya Space Center in northern Norway today (Sept. 5) at 4:12 p.m. EDT (2012 GMT; 10:12 p.m. local time in Norway). A little over seven minutes later, it etched its name into the record books, settling into an elliptical path around our planet.
"This is right now making history — making history for Spectrum, making history for Isar, making history for Europe,” Nikolaos Perakis, Spectrum chief engineer at Isar, said during today's launch webcast, which the company produced in collaboration with NASASpaceflight. "I'm incredibly proud of this massive achievement."
The view from the second stage of Isar Aerospace's Spectrum rocket after it reached orbit on Sept. 5, 2026. (Image credit: Isar Aerospace/NASASpaceflight)
This was Spectrum's second bite at the apple: The two-stage, 95-foot-tall (28-meter-tall) rocket first flew in March 2025, lifting off from Andøya on a flight Isar called "Going Full Spectrum." But, as often happens on debut missions, Spectrum suffered an anomaly that day; it came crashing back to Earth less than a minute after launch.
"A comprehensive investigation was completed within two months of the launch," Isar wrote in a September 2025 update. "The findings identified an unintended opening of the vent valve and a loss of attitude control at the start of the roll maneuver as the initiating events that led to the in-flight failure."
The company took the lessons learned that day and geared up for flight number two, "Onward and Upward," which was originally supposed to launch in January.
An issue with a pressurization valve nixed that plan, however, pushing the flight to March. Bad weather and an intruding boat scuttled multiple attempts that month, and an April 9 try was scrubbed due to a leak in a composite overwrapped pressure vessel.
Isar next tried to fly on June 15 but stood down after "detecting off-nominal behavior in the vehicle's fluid systems," according to a company update that day on X. But the company got that issue under control, rolling Spectrum back to the pad for today's launch.
"We had some delays, obviously," Petrakis said during the webcast. "We had some setbacks, but we came back stronger from them. And it validates this tremendous amount of engineering across all the teams, and that's what brings us into orbit."
Spectrum didn't carry viable payloads on its debut flight, but it did today: Five cubesats and one non-deployable scientific experiment went up on "Onward and Upward."
Spectrum's upper stage needed to deploy those payloads before Isar could declare full mission success. And deployment couldn't occur until after the rocket performed a circularization burn to get out of its initial elliptical orbit, which was estimated to feature a closest approach to Earth of 112 miles (180 kilometers) and a farthest-away point of 311 miles (500 km).
Spectrum was able to check those boxes, ultimately deploying the payloads as planned, Isar announced via X about two hours after launch.
So today was a very big day for Isar, which is thinking big with Spectrum. The company sees the rocket — which can haul about 2,200 pounds (1,000 kilograms) of payload to low Earth orbit — becoming a workhorse launcher of small to medium-size satellites down the road, and its infrastructure supports that vision. Isar says its manufacturing facility near Munich can churn out more than 30 of the rockets per year.
“Flight 2 is a big, big milestone, big success," Petrakis said. "But this is just the beginning. So I'm really looking forward to the next steps."
Spectrum is the first rocket to reach orbit from Western Europe, but others have long flown from a different part of the continent — the Russian part. For example, Plesetsk Cosmodrome has hosted orbital launches for about six decades now. (About 25% of Russia lies in Europe, with the rest classified as part of Asia.)
Editor's note: This story was updated at 4:45 p.m. ET with news of successful launch and orbital insertion, then again at 8:35 p.m. ET with news of payload deployment.
Continuing on our journey through retro classic computing experiences, here’s another fun one reborn for retro gamers in the modern MacOS era: Chonkcraft. Remember Warcraft 2, the award-winning classic real-time strategy game from Blizzard circa 1995? You’d play as Orcs or Humans, build a village and an army, and then command that army through battles ... Read More
On August 17, GitHub experienced an outage that lasted 7 hours and 47 minutes. It disrupted github.com, authentication, GitHub Actions, APIs, pull requests, issues, and Copilot, affecting developers and organizations around the world.
[…]
Neither outage was caused by a code or configuration change. Both incidents were capacity failures at their core. We failed to scale critical components before demand exceeded their capacity. Since April, monthly commits have grown from 1.4 billion to 2.9 billion. That growth explains the pressure on our systems, but it does not excuse these outages.
[…]
As part of the reliability commitments we made earlier this year, we have focused on three priorities: adding capacity, improving efficiency, and removing architectural bottlenecks. We have since added more than 3 million CPU cores, 120 petabytes of high-speed storage, and significant network capacity. We installed as much hardware as available power allowed in our existing data centers while accelerating our migration to Azure.
This is the wrong way to think about this because there’s no such thing as infinite capacity. A large distributed system will be simultaneously mostly idle and (in some subcomponents) overloaded. The root cause is not “a component didn’t have enough capacity (because of auto scaling failures)”, but rather “this complex system collapses (rather than degrade gracefully) when demand exceeds capacity”.
When components reach capacity limits, the excess traffic of the lowest priority should be rejected. Rejected traffic should not be retried — in fact, not only should clients not retry these errors, these errors should cause client-side throttling. Traffic isolation should be applied — if the cause of the overload is a single client/customer system, no other system should be affected.
For the first time in decades, NASA has rolled out one of its iconic astronaut training aircraft with a bold, new look.
The space agency debuted a new livery on one of its T-38 jets in celebration of its program to return astronauts to the Moon. The Artemis design retains nods to what made the "white rocket" immediately recognizable, but adds a new colorway and painted graphics to make clear where NASA is headed.
"This new 'Artemis' livery has a black and white paint scheme with blue and red stripes that separate those two paint schemes," said Sean Brady, who proposed and designed the new livery while serving as the T-38 project pilot in NASA's Aircraft Operations Division (AOD), part of the Flight Operations Directorate at Johnson Space Center in Houston. "The Artemis program logo in the back and a picture of the Moon is on the left and right side of the rear fuselage."
Login
