It seems WordPress.org is having some problems as of now. Whenever I tried logging on to my admin panel, I get redirected to a 504 Gateway Timeout message, which is very frustrating whenever I try to see my blog stats and even trying to post on my blog. Its quite inconvenient. Hopefully its not going to take a long time. It seems all WordPress blogs are affected.
Here’s a post from another blog regarding this issue… The person didn’t really talk much about the technical stuff of the problem, but one comment posted says that it could be WordPress bandwidths? Anyways here’s the link to the post…
http://saltedlithium.wordpress.com/2008/03/07/504/
I might not be able to post frequently for now until WordPress enhances their service.
I can actually get around the WordPress.ORG homepages with no problems, it’s the .COM pages I’m having problems with. I’ve checked with Other Users and most of them are doing alright. If I can get this figured out I’ll let you know how it happened. If you’re interested I just left as much tech info as I can as a response to a comment on my blog…
I just got a 504 while trying to post this… That’s irony.
Yes it’s very sporadic on the .com pages. By the way, my blog is on a .com domain, and it seems your blog as well. I think .org domains are on a user’s server out of wordpress, while .com domains are users on wordpress. I found this out recently, because I tried to go to wordpress.org, and I found a website where you can download the wordpress software for your server, and wordpress.com is like InvisionFree.com. If you can find the reason, that’ll be greatly appreciated so I can pass the message around.
If this continues on, I’ll really have to move on to purchasing my own host…
I found this in the WP Forum, it was written by one of the Top WP People, if you can get in there the topic can be found at:
http://en.forums.wordpress.com/topic.php?id=22805&replies=85
“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.”
I think I found a reason why this happened… if you look at wordpress.com stats in the past week or two, there’s been a significant jump of users making new wordpress accounts. It looks more like spambots attacked their registration which could’ve also affected the server’s performance.
oh here’s the link..
http://wordpress.com/stats/signups/
They had a DOS attack last week. I don’t know if they’re related but from what I could find in the Forum it’s a Bell / Sympatico issue… since you’re in Toronto I’m guessing you’re on Bell.
One of the People In Charge of WP wrote this in the forum:
But WP has no solutions… they’re asking Us to call Bell Canada to complain, this is from one of the Official WP People (Barry):
“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.”
I think this might sort itself out, but the more emails to Bell the better I guess… I’ll let you know if things get better.
I think it’s working itself out… it’s definitely a Bell issue. If you still have the problem on Monday or Tuesday I’d look into changing ISP’s before changing the blog. You’re in Toronto so Roger’s would offer the same services. Good luck with everything… nice to have met you, hope we can do it again under much better circumstances.
Oh great! Thanks so much for the heads up! Nice meeting you too!