For Bell Canada Customers WordPress.com too slow to respond?

• 

  lloydbudd · Member · Mar 8, 2008 at 12:04 am

  • Copy link

  computerfella, you do realize that I’m Canadian and in Canada?

  Encouraging you to pursue the issue wasn’t saying that we weren’t pursuing it, but the reality is, as I suggested before, they are even less likely to listen to us.

  I try to remember not to vent my frustration in the people that will listen and join me in a conversation.

  The issue came to a head last night when we finally identified a routing issue between Bell Canada and one of the IP blocks assigned to us in one of our datacenters in Texas. We have currently routed traffic around the problem area and are working with our provider and Bell Canada to resolve the routing issue.

• 

  raincoaster · Member · Mar 8, 2008 at 12:20 am

  • Copy link

  Ah, thanks for changing the title. Now the complaints I’ve been getting from readers make sense. Any ETA on the solution?

• 

  computerfella · Member · Mar 8, 2008 at 12:48 am

  • Copy link

  Foolswisdom, I did not realize you are Canadian, nor did I realize staff was working directly on the problem. I appologize for the frustated rant. I prefer wordpress to blogger and hope you are able to get the problem resolved. I’ve been able to get in to this forum using a proxy which for reasons I am not familiar with, has allowed fast access. Of course I can’t ask readers to use a proxy but will wait and see how you make out. Good luck.

• 

  universalgeni · Member · Mar 8, 2008 at 12:54 am

  • Copy link

  I wonder if Blogger wouldn’t have the same issue? Do we know that they don’t? They might as well have exactly identical problems…

• 

  barry · Staff · Mar 8, 2008 at 1:09 am

  • Copy link

  Based on the traceroutes we have received from various users and the information we have received from our upstream provider, Bell Cananda is routing traffic destined to one of our IP blocks in a loop. The traffic is not being correctly routed out of the Bell network. This is likely a simple configuration error on their end and may or may not affect their routing of traffic to other IP blocks/websites. Our upstream provider has contacted their Network Operations Center and informed them of the problem, but as Bell Canada customers, it would also probably be helpful if you contact them as well. Unfortunately, since the configuration error is not within our network, there is nothing we can do to fix the problem. As a temporary workaround, I have routed the majority of blog traffic around the problem area for the time being.