The Twitter Inc. logo and signage is displayed on the facade of the company's headquarters in San Francisco, California, U.S., on Friday, Sept. 13, 2013. The San Francisco-based company filed confidentially with the U.S. Securities and Exchange Commission through a process that will keep sales and profit data under wraps until shortly before a road show to market to investors Photographer: David Paul Morris/Bloomberg
Image Credits:David Paul Morris (opens in a new window) / Getty Images

Twitter says internal systems change to blame for partial outage

Twitter has confirmed that an “internal systems change” was to blame for its partial outage today. Earlier today, the social network confirmed that some were having problems accessing the social network and that it was working to fix the issue. Twitter has since rolled back the internal systems change.

Reports from third-party web monitoring service Downdetector indicated that problems began around 2 p.m. EDT. Users reported problems with both the app and web versions of the platform, with some saying they were being logged out or were unable load their home feed.

“We fixed it,” the company said in a tweet. “We made an internal systems change that didn’t go as planned and have rolled it back. Twitter should now be loading as expected. Sorry about that!”

Update 08/09/2022 3:10 p.m. EDT: Article was updated to include information about the cause of the outage.

Techcrunch event

Save now through June 4 for TechCrunch Sessions: AI

Save $300 on your ticket to TC Sessions: AI—and get 50% off a second. Hear from leaders at OpenAI, Anthropic, Khosla Ventures, and more during a full day of expert insights, hands-on workshops, and high-impact networking. These low-rate deals disappear when the doors open on June 5.

Exhibit at TechCrunch Sessions: AI

Secure your spot at TC Sessions: AI and show 1,200+ decision-makers what you’ve built — without the big spend. Available through May 9 or while tables last.

Berkeley, CA | June 5
REGISTER NOW

Topics

, , , , ,
Loading the next article
Error loading the next article