temporary issue with some Yahoo! Pipes feeds
We had to add additional feed processing servers as a matter of urgency yesterday, which means that requests to Yahoo! Pipes from these new servers aren't whitelisted yet. Yahoo! are in the process of adding these IPs to their whitelist, so the issue is temporary.
We try to give Yahoo! notice of these things, but had a choice of causing real issues for everyone, or bring on more hardware and risk a brief period where some Yahoo! Pipes feed may get throttled.
I'll update this topic once I have confirmation that whitelisting has propagated at the Yahoo! end.
In the meantime, as a temporay measure, you may be able to route the feeds via a service like feedburner, which would avoid the throttling in the short term.
We try to give Yahoo! notice of these things, but had a choice of causing real issues for everyone, or bring on more hardware and risk a brief period where some Yahoo! Pipes feed may get throttled.
I'll update this topic once I have confirmation that whitelisting has propagated at the Yahoo! end.
In the meantime, as a temporay measure, you may be able to route the feeds via a service like feedburner, which would avoid the throttling in the short term.
Follow this update to get notifications on your dashboard.
-
Inappropriate?That's very much for the quick answer....
-
Inappropriate?Any updates on this? I am having trouble with Yahoo pipes feeds that are shown as valid with W3C's RSS validation service. For example: http://pipes.yahoo.com/pipes/pipe.run...
Twitterfeed says it cannot parse the feed.
I’m frustrated
-
I've just reached out to the Yahoo! Pipes folks again, it seems we're still getting some 999/permission denied errors from the web server IP address, meaning there's still some throttling going on. Hopefully they'll be able to fix this soon.
Loading Profile...


EMPLOYEE

