People all over social media say they’re receiving texts originally sent months ago, including on Valentine’s Day.
The out-of-context messages — especially for people who were in a relationship with their exes at the time — have led to some funny but awkward situations.
The late text messages are affecting smartphones across several major carriers, but the companies say there’s an explanation and you haven’t been hacked.
Sprint and T-Mobile spokespersons said the problem was the result of a maintenance update affecting multiple carriers, according to Business Insider. T-Mobile told the news site that it occurred because of a “third-party vendor issue.”
An update for messaging platforms used by major carrier caused the “glitch,” Sprint told CNET. The website reported that Sprint, Verizon, T-Mobile and AT&T are working on an effort called the “Cross Carrier Message Initiative,” which is expected to launch next year.
On Friday, a telecom vendor called Syniverse took responsibility for the problem, which caused about 170,000 messages to be sent on Feb. 14, The Associated Press reported.
The company said messages that fail to send are temporarily stored in a server, according to a statement on Syniverse’s website. That server failed in February and it was restarted on Thursday — which caused the stored messages from months earlier to be released, the company said.
People were definitely confused by all the delayed texts.
On Reddit, a user said she received random texts from her boyfriend who was sitting next to her all night. Another user said his wife got a text from him asking about a party — just as they were getting ready for bed.
Others received text messages or had them sent to exes.
According to this Twitter user, his relationship might’ve been doomed because of a missed text from his girlfriend on Valentine’s Day.
It was alarming for one person when she received a text that said “need help” in the middle of the night.
In a statement, Sprint apologized for all the confusion, according to CNET.
“The issue was resolved not long after it occurred. We apologize for any confusion this may have caused,” a Sprint spokesperson told CNET.