United Launch Alliance said its Vulcan rocket suffered an anomaly 10 minutes after a Sunday liftoff from Cape Canaveral and failed to deliver 40 Amazon Leo internet satellites to orbit, Spaceflight Now reported, quoting a ULA statement issued about 50 minutes after launch.

It was the first outright failure of a ULA rocket since the Boeing-Lockheed Martin venture was formed in 2006, and only the fifth flight of Vulcan. Sunday's mission was the first of 38 Vulcan flights Amazon has bought for Leo, a constellation designed to compete with SpaceX's Starlink. ULA had already flown eight Leo missions on Atlas 5 rockets. The lost payload would have raised the number of Leo satellites launched to 436; more than 3,300 are needed to complete the constellation, the report said. Amazon has also booked Leo launches on Blue Origin's New Glenn, Europe's Ariane 6 and SpaceX Falcon 9 rockets.

The 214-foot rocket lifted off at 12:40 p.m. EST. Solid-rocket boosters appeared to work normally, but the BE-4 first-stage engines appeared to burn longer than the pre-launch timeline, and ULA said the failure came during the Centaur upper-stage burn, with no further official detail. Friday and Saturday attempts had been delayed, and Sunday's countdown included a hold at T-minus 20 seconds; it was not yet known whether that issue played any role.

For Tesla and SpaceX watchers, the immediate point is competitive, not celebratory. A failed Vulcan flight slows a well-funded rival constellation and may ground Vulcan while the investigation runs. It does not, by itself, change Starlink's current operational fleet, and it does not tell us how long Amazon will have to wait to try again. NASA Administrator Jared Isaacman offered NASA's help and said the agency and the nation need ULA, Spaceflight Now reported.

ULA said it would work with its customer to find the cause, determine corrective action and return to flight as quickly as possible, and that customers would have visibility into a formal investigation. Until a cause is published, the accurate summary is the company's own: an anomaly at T+10 minutes, a lost Amazon Leo payload, and an investigation now under way.

Those are the official and on-the-record points we have this morning. Timetables, investigations and return-to-flight plans can change, and we will update this file if the company or a regulator publishes a new date, a cause or a revised figure.

Spaceflight Now's reporting is based on ULA's own statement and on the live launch events it described. It is not a finding on the Centaur or the BE-4 engines, and it should not be read as one.