Many of you will have noticed that Twitter has been intermittently slow and occasionally down altogether in the last 2 days. This is because it was hit with a DDoS attack – an attack where the server is overloaded with many “fluff” requests that cause it to slow down and sometimes even crash – in short, someone was deliberately trying to bring Twitter offline.

Though the Twitter.com web front-end is back up, the API (Application Programming Interface – a method by which third parties such as ourselves can talk to Twitter to send/recieve your tweets) has taken a serious hit on Twitter’s end – we have no doubt that they’re doing their best to get it back up to full potential.

However, until those issues are fixed and the interface is stable again, iTweetReply will remain less reliable than usual – other services have gone down completely, as OAuth, the method used by others for authenticating with Twitter, is completely offline at the moment.

We’re doing our best to keep everything working on our end – you can (oh the irony) follow us on Twitter for status updates.

Update: iTweetReply push now appears to be stable, though this could change in the future relative to the Twitter API.