- NRA calls Beto O’Rourke ‘AR-15 salesman of the month’ in wake of buyback proposal 8 Years Ago
- After 23 deaths, Sean Bean is tired of getting killed on-screen 8 Years Ago
- Stephen Miller has a girlfriend—and people are stunned Today 11:35 AM
- Mickey Rourke says Robert De Niro iced him out of ‘The Irishman’ Today 11:07 AM
- Conservative men are melting down over Elizabeth Warren’s speech Today 10:40 AM
- People are calling rapper Tekashi 69 a ‘snitch’ for outing gang members Today 10:16 AM
- Greta Thunberg tells Congress to ‘listen to the scientists’ about climate crisis Today 9:55 AM
- Maybe we should start taking Tom DeLonge seriously about UFOs Today 9:11 AM
- Get ready to argue about the alternate-history politics of HBO’s ‘Watchmen’ Today 8:53 AM
- Third instance of Justin Trudeau wearing racist makeup emerges after he apologized for first 2 Today 8:45 AM
- 6 must-watch college football games to stream this weekend Today 8:12 AM
- What is the Hinge dating app, and how does it work? Today 7:00 AM
- ‘Inside Bill’s Brain’ is nothing more than a Bill Gates infomercial Today 6:30 AM
- Swipe This! He hasn’t texted me back. Should I text him again? Today 6:00 AM
- New Loch Ness monster video may just confirm giant eel theory Wednesday 8:04 PM
Twitter glitch: Can we chat?
Because of an error on the site, some Twitter users missed replies to their messages, disrupting regulary scheduled Tuesday tweetfests.
At 8:30 p.m. ET Tuesday Roy Atkinson was watching for updates on a Twitter outage that sporadically impacted users throughout the day.
Atkinson, a senior writer and analyst for HDI, an IT service and technical support membership association, was hosting a Twitter chat on “ROI: Selling the Social Media Proposition for Customer Service.”
“Hope it clears up by chat time!” Atkinson said in a retweet of a ReadWriteWeb article about the outage.
At 11:42 a.m. EST Tuesday, Twitter confirmed there was an issue that was preventing many users from seeing replies and mentions left by other users.
Many Twitter users went the whole day without noticing the glitch, but others were upset by the company’s slow response and the lag of nearly nine hours between the acknowledgement of the problem and the announcement of the repair.
Some of the first complaints were recorded, according to the ReadWriteWeb report, a full four hours before Twitter posted its response.
“If you don’t see a Twitter reply, did it happen?” Jason Gertzen asked in a Tweet.
There were no updates on the Twitter @support page until 7:30 pm ET, when engineers reported the problem had been fixed. That meant, unless the problem cropped up again, Atkinson’s chat would get underway as scheduled. Others were not so fortunate.
“Figures this happens as i was testing today.. good to know now,” Rick Racela, a social media manager at Comcast Sports Group complained two hours before the problem was resolved.
Photo by Crystl
Dave Copeland is a tech reporter whose work has appeared in the Wall Street Journal, Boston Globe, and ReadWrite. He teaches journalism at Bridgewater State University.