Looks like there’s currently some issues with the Twitter API, we’re seeing lots of timeouts, which are leading to delays with publishing. Should hopefully just be temporary issue, we’re sure the guys at Twitter are on it…

UPDATE: this issue is still happening, we’ve reached out to Twitter in the hope they can shed more light on it - we’re so sorry for any problems caused!

UPDATE 2: it looks like the problem is a networking issue somewhere between our hosting provider and Twitter. We’ve implemented a temporary get-around until the issue is permanently fixed, which - we hope - will help with the immediate problem. We’ll update further once we’re confident the issue has been found and fixed. Apologies again for the problems today!

UPDATE 3: this issue has now been fixed, and everything should work again as expected.

We are currently seeing very slow response times from the Twitter API, leading to large numbers of time-outs when we’re trying to update statuses. This means many posts are currently delayed, but hopefully this is just a temporary issue at the Twitter end that they’ll fix in due course.

Apologies for the inconvenience!

We’re seeing some indications that notifications for new posts from some Feedburner feeds are not being received. If your feed is hosted at Feedburner, and no updates are posted via twitterfeed then your feed may be affected by this.

Hopefully this is a short term issue that will be fixed by Feedburner/ the appspot hub soon, but in the meantime you should be able to click “check now” in the twitterfeed dashboard to force us to check the feed ourselves, until the Feedburner notifications start working reliably again.

At the moment, the Twitter website and API are unavailable, so we are unable to post updates. Things will catch up automatically once Twitter have fixed their issues… (if you read this via Twitter, chances are that things are ok again).

Hi there - bitly suffered a service disruption, which in turn affected the availability of the twitterfeed website and feed processing. Things are going back to normal now, but some feeds/posts may be slightly delayed as a result. Apologies for any inconvenience!

We had some problems with the back-end component that creates the Twitter messages failing this afternoon. To the best of our knowledge this should be fixed now, and all new posts should be going out again now.

Please accept our apologies for the issue!

We are currently unable to fetch feeds from Yahoo! Pipes. We’ve been in touch with our contacts at Yahoo! Pipes to make them aware of the problem, so hopefully this will just be a temporary issue.

Once we hear back from the team at Yahoo! we’ll update this post with more details. Apologies for the inconvenience!

UPDATE: At the moment it seems to be working again, but we’re not sure yet if the issue is permanently fixed, or if there is some throttling in place that would make it work intermittently only. More conclusive update to follow once we hear back from Yahoo!…

It looks like GoDaddy is currently suffering from a DDoS attack that is affecting DNS lookups for many sites and feeds hosted there.

Although the twitterfeed site itself is not affected by this issue, because a large number of feeds we are processing are affected by this, and are currently unreachable (or only reachable intermittently), our feed processing is running slower than usual at this time. This should improve and get back to normal automatically, once the GoDaddy issues clear up.

Apologies for any inconvenience, and thanks for your understanding!

We are currently unable to fetch feeds from Yahoo! Pipes. We’ve been in touch with our contacts at Yahoo! Pipes to make them aware of the problem, so hopefully this will just be a temporary issue. Once we hear back from the team at Yahoo! we’ll update this post with more details.

Thanks, and apologies for any inconvenience!

UPDATE: Things should be getting back to normal now, but we’ll keep an eye on things in case there are still some issues around Pipes URLs.

… at the moment. Should be temporary, but just so you’re aware if you’re currently waiting for items to be posted. Nothing will be lost, we will continue trying to post, and will repost items that fail at the current time.
We’re sure the Twitter folks are hard at work fixing this as we speak ;)