Outbound Twitter email is currently delayed and will remain delayed for the next 4-5 hours due to a processing issue.
Update: This issue has been resolved.
Outbound Twitter email is currently delayed and will remain delayed for the next 4-5 hours due to a processing issue.
Update: This issue has been resolved.
We’ve seen a number of reports from people receiving emails from “support@twitter.com” notifying them that they have unread/delayed/undelivered messages at Twitter. Twitter does not send any messages of this type; support@twitter.com does not send notifications in general.
While malware does not appear to be inherent in the email, the link is actually masked; rather than taking you to Twitter once you click on it, it actually takes you to a pharmaceutical site after routing you through a couple other websites (which may have malware). We’re actively pursuing measures to get these sites shut down; in the meantime, we recommend that you not click on the link and instead just delete any such emails you receive.
Update (May 1, 2010): Twitter engineers do not send emails to users. Please report any emails you receive from engineer@twitter.com as spam, then delete those messages; they are not originating from us and are part of an ongoing spam campaign. You can find out more information about this spam campaign here.
Users will see an increased number of errors starting around 2:30p Pacific today. The increased errors should last for less than 5 minutes.
Users are seeing an elevated number of errors on twitter.com and we’re working to recover from this problem.
Update Tuesday 5:48:26PM PDT 2010: Site Fully Recovered.
We have disabled the local trends feature. We expect to re-enable the feature in a few hours. Look for an update soon.
Update: We are keeping this feature disabled while we continue to diagnose the issue.
Update April 20th 4:12PM PST: We’re slowly dialing up local trends again
Users are seeing an elevated number of errors on twitter.com and we’re working to recover from this problem.
Update (2:37p): We have uncovered the underlying problem and site errors are now subsiding. Total duration of the period of elevated errors was around 20 minutes.
We’re looking into the cause of the general site outage that began at about 14:02 UTC (7:02 PDT).
Update: The root problem was addressed at 14:25 UTC (7:25 PDT) and the site has recovered.