Pages Loading Slowly

[Theronae]

Hello, for the past couple of days I've been having issues loading pages from MMO Champion.
Each page loads abysmally slowly for the Main Page and the Forums, images fail to load such
as the sidebar menu backgrounds, and the links to screenshots on the Main Page will not load
because the server is "taking too long to respond."

I haven't made a post about it yet because I assumed it was just a temporary hiccup of some
sort and would solve itself but it seems to be persisting. It is through great patience that
I bring you this message

This issue is occurring in both Firefox and Chrome for the Main Page and the Forums; however
the Blue Tracker and MMOC Database load just fine. On the Blue Tracker page, the icon for
'Cataclysm-logo-small' does not load, possibly because it too is hosted on 'static.mmo-champion.com'.

Here is the error message from Firefox when I try to click links to 'Screenshots' on the Main Page:

The connection has timed out

The server at media.mmo-champion.com is taking too long to respond.

I am unsure if this is a problem with my internet connection or if it's a webserver issue, but
I thought I would bring it to your attention just in case. Thank you for your time

[Xtek]

I'll see if I can't look into what the issue is. Those media servers are very beefy behind an insanely huge connection.

My first response would be that it's something on your end. However I will look into this.

[Xtek]

I went ahead and did trace routes and pings to your IP from all 4 of our media servers and everything looks good.

So it looks like it might be something on your end. Whether it be your ISP, the route it's taking from your location or something along the way to the data center. I'll keep looking into it.

Here are the ping results I got back from your IP from all 4 media servers.

Server 1:
Pinging *.*.*.* with 32 bytes of data:
Reply from *.*.*.*: bytes=32 time=50ms TTL=50
Reply from *.*.*.*: bytes=32 time=49ms TTL=50
Reply from *.*.*.*: bytes=32 time=49ms TTL=50
Reply from *.*.*.*: bytes=32 time=51ms TTL=50

Server 2:
Pinging *.*.*.* with 32 bytes of data:
Reply from *.*.*.*: bytes=32 time=52ms TTL=50
Reply from *.*.*.*: bytes=32 time=49ms TTL=50
Reply from *.*.*.*: bytes=32 time=48ms TTL=50
Reply from *.*.*.*: bytes=32 time=50ms TTL=50

Server 3:
Pinging *.*.*.* with 32 bytes of data:
Reply from *.*.*.*: bytes=32 time=48ms TTL=50
Reply from *.*.*.*: bytes=32 time=48ms TTL=50
Reply from *.*.*.*: bytes=32 time=49ms TTL=50
Reply from *.*.*.*: bytes=32 time=48ms TTL=50

Server 4:
Pinging *.*.*.* with 32 bytes of data:
Reply from *.*.*.*: bytes=32 time=49ms TTL=50
Reply from *.*.*.*: bytes=32 time=48ms TTL=50
Reply from *.*.*.*: bytes=32 time=49ms TTL=50
Reply from *.*.*.*: bytes=32 time=50ms TTL=50

[Xtek]

Assuming you're running windows would you mind opening a command prompt and running...

tracert media.mmo-champion.com

Then paste back the results.

[Theronae]

Thank you very much for the responses. I did the tracert and here are the results.

Tracing route to media.mmo-champion.com [65.254.218.140]
over a maximum of 30 hops:

1 * * * Request timed out.
2 97 ms 9 ms 9 ms ge-3-31-ur01.grant.tx.houston.comcast.net [68.85
.248.209]
3 13 ms 10 ms 9 ms te-8-1-ur02.grant.tx.houston.comcast.net [68.85.
244.202]
4 11 ms 10 ms 179 ms te-8-1-ar01.royalton.tx.houston.comcast.net [68.
85.244.101]
5 17 ms 15 ms 15 ms 68.86.93.13
6 16 ms 27 ms 15 ms pos-0-0-0-0-pe01.1950stemmons.tx.ibone.comcast.n
et [68.86.86.90]
7 21 ms 17 ms 22 ms Vlan553.icore2.DTX-Dallas.as6453.net [206.82.142
.17]
8 * 28 ms * Vlan6.icore1.DTX-Dallas.as6453.net [209.58.47.13
]
9 82 ms 16 ms 15 ms te9-3-0d0.cir1.dallas2-tx.us.xo.net [206.111.5.2
05]
10 19 ms 16 ms 21 ms vb2000d1.rar3.dallas-tx.us.xo.net [207.88.13.122
]
11 52 ms 54 ms 81 ms te-4-0-0.rar3.atlanta-ga.us.xo.net [207.88.12.1]

12 49 ms 49 ms 52 ms ae0d0.mcr1.smyrna-ga.us.xo.net [216.156.0.66]
13 51 ms 50 ms 58 ms 209.118.220.30
14 51 ms 51 ms 51 ms 68.64.33.45
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

I noticed that each time that "Request timed out" there was a long pause
between each one. I hope this helps, though this is sounding like an issue
that's on my end.

[Xtek]

Looking at your trace route it looks like it's somewhere your ISP is routing you. If you look at hop #8

8 * 28 ms * Vlan6.icore1.DTX-Dallas.as6453.net [209.58.47.13

Those 2 *s are actual ping timeouts.

Also hop #14 is the actual media server and it looks like you were getting routed beyond that point not sure why.

As far as the delays at the last hops that's because it was trying to do a reverse DNS lookup on the IP and there wasn't one so it was timing out.

[Xtek]

So after further investigation the problem is with a Tier 1 peering network company that Comcast uses to peer it's network with other networks across the internet.

[Theronae]

I see, I'll have to check with my ISP to see what's going on. Thank
you very much for your effort in investigating this for me, I really
appreciate it!

[Leylin]

This is happening to me also

Though it does not happen often , its not really a problem.