- Report finds some users can’t opt out of Facebook’s face recognition Monday 7:27 PM
- Get emotional over this real-life pastor baptizing an anime girl in virtual reality Monday 6:53 PM
- Twitter wants to know what Jack in the Box did to offend Kim Kardashian Monday 6:38 PM
- ‘Game of Thrones’ meme claims King’s Landing is an ‘inside job’ Monday 6:06 PM
- Report: Personal data of 49 million Instagram influencers exposed online Monday 4:57 PM
- ‘Stranger Things’ season 3 trailer teases a wet, hot American summer Monday 4:02 PM
- What Daenerys’ biggest ‘Game of Thrones’ scenes have in common with Nazi propaganda Monday 3:12 PM
- Here’s what’s coming to Amazon Prime in June Monday 2:11 PM
- Where did Jon Snow go? Unpacking the ‘Game of Thrones’ ending Monday 2:04 PM
- So, did anyone actually win ‘Game of Thrones’? Monday 1:29 PM
- The surprising religious subtext of ‘John Wick: Chapter 3’ Monday 12:53 PM
- Robin Arryn got hot—and the internet is seriously shook Monday 12:40 PM
- Tana Mongeau is going to VidCon a year after TanaCon disaster Monday 12:12 PM
- What have 2020 Democrats said about Alabama’s abortion ban? Monday 11:36 AM
- People keep throwing milkshakes at the U.K.’s far-right politicians Monday 11:10 AM
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.