As some of you know, fetching Twitter feeds via Pipes often produces a 406 error in our editor, and the Pipe does not run successfully.

We have been in contact with Twitter trying to resolve this problem and supplied them several test cases. Based on various tests we've performed it appears that Twitter's servers are blocking requests from our outbound caches. At the moment they are still looking into it, but until they uncover the reason any Pipes using Twitter feeds will only work occasionally.

If there is any change in status regarding this situation, we will let you know.

Thanks - The Pipes team