Written on February 16th, 2006 at 01:02 pm by Darren Rowse
ProBlogger Feeds Down in Bloglines
Sorry to my RSS subscribers (via Bloglines only as far as I can tell – Of course Bloglines readers won’t be able to read this :-) ) but my feed doesn’t seem to be working. It’s quite frustrating as the majority of readers to this site are via RSS and Bloglines makes up close to 40% of those subscribers. Hopefully it’s just a small glitch. Are others using other news aggregators having problems with my feeds?
update: Just heard from Feedburner (who I asked to check into it) who suggested I ask Bloglines to restart polling on my feed which I’m now going to do. From memory last time I had this problem both Bloglines and Feedburner blamed the other and it took a few days before it suddenly ‘returned to normal’ with no real explanation. Lets see what happens this time.
update 2: I’m seeing the feed again in Bloglines as are others. Thanks for all the reports in friends.
11 Responses to “ProBlogger Feeds Down in Bloglines” - Add Yours
Liam Daly
February 16th, 2006 1:54 pm
Darren I read this as a feed ok in BlogLines – it’s the FeedBurner Feed:
http://feeds.feedburner.com/ProbloggerHelpingBloggersEarnMoney?m=1608
Aaron
February 16th, 2006 2:05 pm
Well they work okay in Feedlounge
Adam
February 16th, 2006 2:05 pm
Darren, I got to this entry via Bloglines. Seems OK to me. And there’s no red exclamation mark next to your feed in my sidebar.
Cary
February 16th, 2006 2:07 pm
Bloglines has been doing this to me quite a bit lately.
It’s not too big of a deal though, because they at least give you that little red “!” to let you know the feed’s not getting updated.
In fact, I noticed it and came right over :)
Duncan
February 16th, 2006 4:02 pm
It can read it via the b5media mega feed in Bloglines but not directly??? strange
~Dawn
February 16th, 2006 9:14 pm
I read the feed in bloglines at 1014GMT 2/16/06
John Evans (Syntagma)
February 16th, 2006 9:17 pm
It’s just come back in Bloglines, Darren. At 10.15am GMT.
Darren Rowse
February 16th, 2006 9:27 pm
thanks all – seems fine here also.
Denise O'Berry
February 17th, 2006 6:45 am
Darren — I read you via My Yahoo! and they haven’t been updating your feed for quite some time. All I get is the title ” Pro Blogger.” Doesn’t stop me from coming over here and reading, but it sure would be nice if it was straightened out. :-) It’s been like this for a good couple of months now.
Darren Rowse
February 17th, 2006 8:17 am
That’s strange Denise – it seems to come through ok on my MyYahoo…. very odd
Dick Costolo
February 18th, 2006 3:58 am
Hey Darren, couple things – if anybody here ever simply blames another company for something without listing all the possible reasons some event might have occurred, email me about it. I hope in my personal email to you that I was clear about the myriad reasons that a feed might appear red-exclamationed at Bloglines. Could be that we didn’t have a valid version of your feed cached the last time they checked; could be that we timed out the last time they checked; could be that your feed just went off the rails there for some reason without an issue from us. As to the My Yahoo issue, I also see your feed correctly updated there, however, as I think the My Y! folks would tell you, they seem to have different caches for different feeds, and in rare instances, one may be correctly updated while another isn’t. Sometimes even just hitting shift-refresh does the trick on My Y! but I confess I haven’t had an issue like this in many months there.
As a general fyi for your readers (i know you know these), you can always check your feedmedic in FeedBurner to see if we’re having any source feed issues, and you can always check http://www.grabperf.org to see how FeedBurner is responding to feed requests. Grabperf’s an independent external monitoring system that Technrati hosts that checks on various blog related services. they’re a good way to verify whether some system is generally available and responsive or not.
Comments will be closed off on this post 90 days after it is published. Apologies to those this impacts but it's a regrettable and temporary measure to combat a growing comment spam problem. See our most recent posts where you can comment here.