To add more pieces to the puzzle, I get the same thing happening on my FaunaClassifieds site, which is on a different server. We could be having an issue at the data center itself.
I believe I am also having troubles with my ISP (Comcast) as well, as I will get intermittent timeouts, evidently from one or more of Comcast's routers along the way. Here's a traceroute:
Code:
1 0 0 192.168.0.1
2 10 10 73.10.128.1
3 7 -3 68.85.237.81 ge-2-1-sr01.wakulla.fl.tallah.comcast.net
4 9 2 68.85.236.65 te-9-2-ur01.pershingst.fl.tallah.comcast.net
5 7 -2 68.85.236.38 te-8-1-ur01.capitalcircl.fl.tallah.comcast.net
6 Timed out
7 9 2 68.85.236.102
8 39 30 68.86.84.86 te-0-0-0-0-cr01.miami.fl.ibone.comcast.net
9 40 1 68.86.84.66 te-0-0-0-0-cr01.atlanta.ga.ibone.comcast.net
10 42 2 64.209.97.13
11 41 -1 64.209.99.62
12 44 3 65.254.48.106 L3-ATL-14-g0-2.gnax.net
13 41 -3 216.180.243.154 ayk.faunanet.com
Code:
1 0 0 192.168.0.1
2 7 7 73.10.128.1
3 6 -1 68.85.237.81 ge-2-1-sr01.wakulla.fl.tallah.comcast.net
4 7 1 68.85.236.65 te-9-2-ur01.pershingst.fl.tallah.comcast.net
5 Timed out
6 Timed out
7 10 3 68.85.236.102
8 43 33 68.86.84.86 te-0-0-0-0-cr01.miami.fl.ibone.comcast.net
9 44 1 68.86.84.66 te-0-0-0-0-cr01.atlanta.ga.ibone.comcast.net
10 51 7 64.209.97.13
11 64 13 64.209.99.62
12 48 -16 65.254.48.106 L3-ATL-14-g0-2.gnax.net
13 41 -7 216.180.243.154 ayk.faunanet.com
Code:
1 0 0 192.168.0.1
2 7 7 73.10.128.1
3 5 -2 68.85.237.81 ge-2-1-sr01.wakulla.fl.tallah.comcast.net
4 Timed out
5 Timed out
6 Timed out
7 Timed out
8 38 33 68.86.84.86 te-0-0-0-0-cr01.miami.fl.ibone.comcast.net
9 42 4 68.86.84.66 te-0-0-0-0-cr01.atlanta.ga.ibone.comcast.net
10 42 0 64.209.97.13
11 42 0 64.209.99.62
12 42 0 65.254.48.106 L3-ATL-14-g0-2.gnax.net
13 43 1 216.180.243.154 ayk.faunanet.com
These were made in succession, one after the other just a few moments ago. Timeout is set for 5,000ms.
Here's results from pinging this server:
Code:
1 216.180.243.154 56 41 Success
2 216.180.243.154 56 41 Success
3 216.180.243.154 56 41 Success
4 216.180.243.154 56 41 Success
5 216.180.243.154 56 41 Success
6 216.180.243.154 56 42 Success
7 216.180.243.154 56 40 Success
8 216.180.243.154 56 41 Success
9 216.180.243.154 56 43 Success
10 216.180.243.154 56 43 Success
Now this doesn't look too bad except for the fact when I first got this server, all the ping tests exactly like this one were hitting 22 to 24 ms religiously. So SOMETHING has definitely changed. It almost appears that my server is not even located in Atlanta any longer, as these sorts of pings are what I was getting for Chicago based servers...
And lastly, throughput:
Code:
1 102 B 102 B 41.02 39.80 kilobits/sec Success
2 204 B 204 B 43.03 75.90 kilobits/sec Success
3 306 B 306 B 42.00 116.57 kilobits/sec Success
4 408 B 408 B 43.01 151.81 kilobits/sec Success
5 510 B 510 B 42.03 194.28 kilobits/sec Success
6 612 B 612 B 43.04 227.72 kilobits/sec Success
7 714 B 714 B 42.06 272.00 kilobits/sec Success
8 816 B 816 B 43.03 303.62 kilobits/sec Success
9 918 B 918 B 44.04 333.81 kilobits/sec Success
10 1,020 B 1,020 B 44.01 370.90 kilobits/sec Success
Again, when I first got this server, results were hitting 1.2Megabits per second every time I tried.
If I didn't know better (which I don't) I would swear my server host pulled a bait and switch on me. I used this server with the above mentioned sterling results to evaluate their services. But no sooner had I switched my other two servers over to them, things went rapidly downhill.
Yeah, conspiracy theory stuff, I know........ But them's the facts...