intermittent throttling by Yahoo! Pipes
It looks like twitterfeed is again being throttled by Yahoo! Pipes, so we're getting quite a large number of errors like "ERROR 999: Unable to process request at this time", which results in you seeing "we couldn't parse this feed" error messages.
I've contacted Yahoo! and will see what the response is, hopefully they are willing/able to remove these limits for twitterfeed.
I've contacted Yahoo! and will see what the response is, hopefully they are willing/able to remove these limits for twitterfeed.
Follow this update to get notifications on your dashboard.
-
Inappropriate?My feeds work everywhere except twitterfeed.
-
Inappropriate?Speaking of Yahoo! Pipes, any chance of being able to label our feeds in the future? The only way for me to know which feed/pipe is which is to open YP in another tab and compare the address. If I was able to label the feeds I could know at a glance which is which.
-
Inappropriate?Any updates?
-
Inappropriate?Yeah, any news?
-
Inappropriate?No news on the Yahoo! throttling (which also affects news feeds from Yahoo!) - I've emailed them but not had any response.
On the labelling of feeds - yes, you will soon be able to give each feed a name (soon meaning within the next few weeks). -
Inappropriate?Mario, I've just post a message on the Yahoo Pipes Developer Help forum, and the ypipes team replied here:
http://discuss.pipes.yahoo.com/Messag...
-
Good going! I've added my comments there to try and narrow down the issue for them. -
Inappropriate?I also added post to YP forum. I noted that I am having the same YP feed work on one Twitterfeed account but not parse on another one. Why would that be?
-
Inappropriate?Paul from Pipes wrote on the help forum:
'If someone can post the IP's that twitterfeed uses to call the Pipes RSS feeds, we can look and see if indeed we are periodically rate limiting them.'
http://discuss.pipes.yahoo.com/Messag...
Anyone know the IP?
I have had to stop using Pipes for one important account, and another I have left alone hasn't updated in 12 days!
I’m irked
-
Inappropriate?Current IP addresses used by feed processing are:
78.31.110.126
78.31.110.127
75.101.135.18 -
Inappropriate?Thanks Mario! I posted on YP Forum.
-
Inappropriate?As for this forum message (http://discuss.pipes.yahoo.com/Messag...) problems should be solved, but my tweeterfeed stopped working this week (and does not work yet). Did I understand wrong?
(My feed: http://pipes.yahoo.com/pipes/pipe.run...)
-
We added more servers, so some whitelisting hasn't been propagated at the Yahoo! side yet. I have spoken to them 2 days ago and they agreed to add all new twitterfeed IP addresses to the whitelist, but it may take a few days to show. I'm hoping this will be fixed and working in the very near future. -
Inappropriate?Mario, the same that @daguayo reported it's happening to me on this feed
http://pipes.yahoo.com/pipes/pipe.run...
and the twitter account is: http://twitter.com/unabchile
I hope to see everything working well soon
I’m sad
-
Inappropriate?Is this still happening?
My pipes feed ain't being updated by Twitterfeed... like this one
http://pipes.yahoo.com/pipes/pipe.inf...
I’m frustrated
-
Inappropriate?Will channeling Pipes feeds through FeedBurner solve the issue for now?
-
Yes, that should work, although potentially a bit of a pain to set up.. -
Introduces new problems last time I tried pipes > feedburner. You're also going to add a delay. -
My big trouble is that when I try to ping my Ypipes feed directly or trough feedburner (ypipes feed), it appears to me the message that "it can't parse the feed"... so basically it can't connect to the feed... and sometimes with feedvalidator it appears "Server returned timed out"... so I think the main issue here it's with Yahoo Pipes and not with twitterfeed -
Inappropriate?Yahoo! have just told me the whitelisting of our latest server IP address has gone through, to the throttling errors with Yahoo! Pipes feeds should now be solved.
-
Inappropriate?My Yahoo Pipes -> Twitterfeed -> Twitter (@wivbweb) is still not working. It's been intermittent for at least a week. As of right now it hasn't worked at all since 24 hours ago.
-
Inappropriate?I see the same thing as Chris.
-
Inappropriate?Apologies for the inconvenience, please see this update: http://getsatisfaction.com/twitterfee...
Loading Profile...


EMPLOYEE





