Starlink fixes a gigantic outage that brought the network to a standstill


On the night of September 12 to 13, the Starlink network was the victim of a gigantic outage, which damaged the Internet connection of several thousand users. If, in France, the problem went somewhat unnoticed, it made a lot of waves in the United States, triggering the anger of many users. Fortunately, the technical problem was quickly corrected.

Credit: dutourdumonde/123RF

While it’s not uncommon for an ISP to go down, that doesn’t make it any better. It’s all the more infuriating when it comes to Starlink, the SpaceX service which prides itself on bringing the Internet to the most remote regions of the planet. Today, many users rely on Starlink to enjoy a decent connection, in the absence of suitable alternatives.

This certainly explains the immense wave of discontent which swept across social networks on the night of September 12 to 13. Around 2 a.m., messages began to flood in and reports multiplied: thousands of Starlink subscribers had lost their Internet connection. A few minutes later, the company confirmed that an outage was occurring on its network, and promised a rapid return to normal.

On the same subject — Amazon prepares to compete with Starlink with its own satellite Internet service

An outage hits the Starlink network, but is corrected immediately

Meanwhile, the affair continues to make noise. On DownDetector, there are more than 30,000 reports in the space of a few minutes, while topics on Reddit generate several hundred comments. Fortunately, it did not take long for the situation to return to normal. About an hour after communicating about the outage, Starlink announced that it had been resolved.

If you are a Starlink subscriber, there is a good chance that you did not even realize that an outage was in progress, as it occurred in the middle of the night. It is also possible that it struck mainly in the United States. Regardless, it is reassuring to see how quickly the company’s teams can react in the event of a problem.



Source link -101