Ping is Throttled, Ping is throttled, Ping is throttled

[Dacmon]

Seems like there are plenty of people with the same problem but as of
yet there appears to be no solution. Why??? Looks as though it has
been going in for some time now. I am forced to email my subscribers
manually to tell them about a new podcast. I still don't see a new
update for my podcast on ITUNES and that hurts my traffic big time.

Google... "do no evil" :-P !!!

[Dan Rodney]

Hi Dacmon,

Sorry about this -- please see this blog post:

http://feedburnerstatus.blogspot.com/2009/12/status-of-ping-is-throttled-errors.html

You should now be able to ping with your channel link URL or
feeds.feedburner.com URL without a problem. If you still get a "ping
is throttled" error repeatedly, then most likely you are not using one
of those URLs... we will fix the messaging for that case after the new
year.

Please let us know if you run into any other problems.

Dan Rodney
FeedBurner

[Dacmon]

Thanks for the response. I did what you said, got my fingers crossed
and hoping it works. While trying to figure this out on my own, I
went to podmedic at the feedburner site and saw this message about
some of my podcasts.

Link: http://feedproxy.google.com/~r/2012truthcom/~3/UJBLQ15DQe0/
Content Type reported: text/html; charset=UTF-8
Media enclosure not created because: The content type returned from
your host server was a text type, not a binary media type. Podcast
content should always return a binary media type, such as audio/mpeg
for audio, or video/mpeg for video.

I use the same procedures each time I post a podcast, some of my
podcasts seem to have worked fine but others get this message. First
off, what does this mean and second how do I correct it and why is it
kind of hit and miss on my posts. If you need more detailed info let
me know.

On Dec 21, 1:18 pm, Dan Rodney wrote:
> Hi Dacmon,
>
> Sorry about this -- please see this blog post:
>

> http://feedburnerstatus.blogspot.com/2009/12/status-of-ping-is-thrott...