Recently I’ve experienced reeeeeeaaaaaallllllyyyyy slow load times for anything at wordpress.com and wordpress.org, including all wordpress.com individual blogs. They would finally load but with no formatting. So obviously something was getting gummed up in the works. I’ve solved the problem finally and so I’ll share my experience in hoping that it will help someone else.
Here’s my process of discovery and solution:
- It’s only happening on these WordPress-hosted sites. Everything else is loading fine.
- My Firefox has tons of addons so I load up IE and Google Chrome to see if it’s the browser messing up. Nope. Same results with other browsers.
- I look at the Net tab of Firebug in Firefox to see what is not loading. I notice that s0.wp.com, s1.wp.com, s2.wp.com and s.wordpress.org are not loading. These all resolved to 220.127.116.11 for me.
- I lookup “slow loading s0.wp.com” on Google and even in the recent posts there is not unanimous agreement that there is a “general” problem or outage.
- We have K9 Web filtering on some computers but not others. I try wordpress.com on a non-filtered Windows box and on a headless linux box (a simple wget). Nope. Same results.
- I do a traceroute/tracert. No problem. Works fine.
- I can ping both the ip address and the domain
- We use OpenDNS and its cache check page had no problems
- I have access to a windows box via VNC that has a different ISP and it worked fine
- I have access to a linux server at large French hosting service and via Webmin’s HTTP tunnel it worked fine
Process of elimination points to our house and not a specific computer or operating system in our house. What’s left? My Neuf box (SFR) ADSL router. Everything looks fine in its web interface, including its ability to ping and traceroute. It caught my eye that the uptime for my router was 51 days. This problem with WordPress I had noticed, maybe 2 weeks ago. In the past, I’ve had speed issues every once in a while and have discovered that rebooting the router can fix some of them. So, on a whim I thought I’d just reboot the router.
That fixed it. So I’m not sure exactly WHAT was the problem in the router that screwed up HTTP traffic to a single IP but not other traffic, but perhaps this will save you some time if you encounter something similar.