Tweetdeck, the popular Twitter-owned desktop service for monitoring incoming tweets, went down for many users Thursday morning.
Tweetdeck would not load tweets on its website or app, as pages appeared to be stuck on a "loading" screen for many users.
The problem appears to have started around 9:20 a.m. ET, when many users began reporting problems with the service. Though the issue appeared to be widespread, it seems to have not affected all of the app's users.
tweetdeck is down! Repeat, tweetdeck is down! This is not a drill, folks, this is the time to panic!— Graphoniac (@Graphoniac) July 16, 2015
I can't do news under these conditions. #tweetdeck #fail pic.twitter.com/Qykvd6fKyK— Kirsten Boyd (@Kirsten__Boyd) July 16, 2015
Twitter.com and other Twitter clients, including the main Twitter app, were unaffected by the problem. Even though Twitter's other services remained accessible, the disruption of Tweetdeck -- an app particularly known for its popularity among journalists and other power users -- sparked an immediate freakout.
#Tweetdeck is down. pic.twitter.com/QwKlyRoU2X— John Bowman (@johnbowman) July 16, 2015
.@Tweetdeck you're killin me pic.twitter.com/42vObMCP1J— Kate Sommers-Dawes (@TheRealKSD) June 11, 2015
Tweetdeck barely working. Back to using Twitter dot com like a goddamn neanderthal— Seth Fiegerman (@sfiegerman) July 16, 2015
Tweetdeck isn't working properly right now. pic.twitter.com/YWuMjG3huy— Sal Castaneda (@sal_castaneda) July 16, 2015
Tweetdeck later confirmed the issue in a tweet, saying it was working on fix but did not provide details on the source of the problem.
Some TweetDeck users may be experiencing issues Tweeting and loading Tweets. We're currently working on a fix.— TweetDeck (@TweetDeck) July 16, 2015
As of 12:00 p.m ET, the service seemed to be coming back online for affected users.
praise jesus my phone wasn’t working and now tweetdeck is fixed >.July 16, 2015
Tweetdeck is...back! pic.twitter.com/kgLM6fairo— Alex Tuckey (@alexandertuckey) July 16, 2015
Twitter did not immediately respond to Mashable's request to comment on the source of the problem, but we'll update when we hear back.