heya
so today ive been trying to access this site, and I found that it takes sometimes 20-30 min to load a page if it doesnt just say cant connect then I refresh.
I ran a ping test, 100 pings 89 failed, so I did a short test to show 25% packet loss,
as well as a tracert to show that its only on the end of either your host or provider (I have comcast and in the tracert u will see low 24 ms pings then it hits your backbone and goes nuts)
you guys working on the site or is the provider just acting up? anyone else getting slow site issues
Btw for those that dont know how to use dos or tracert or ping its ok
im sure someone will understand what im talking about
below is my trace to you, and my last comcast hop is at
static.hfc.comcastbusiness.net 24ms
it goes to the .lsanca03.us.bb.gin.ntt.net hop and its ok 25 ms then the next its 255+ ms or packet loss and fyi no other sites are causing such issues as ive traced and pinged many
seems just this ntt.net and secureserver.net backbone
lemme know if its just me
Pinging infamous-quests.com [203.124.115.1] with 32 bytes of data:
Reply from 203.124.115.1: bytes=32 time=224ms TTL=52
Reply from 203.124.115.1: bytes=32 time=233ms TTL=52
Request timed out.
Reply from 203.124.115.1: bytes=32 time=229ms TTL=52
Ping statistics for 203.124.115.1:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 224ms, Maximum = 233ms, Average = 228ms
Tracing route to infamous-quests.com [203.124.115.1]
over a maximum of 30 hops:
1 * 357 ms 24 ms 98.238.244.1
2 13 ms 13 ms 13 ms xe-7-2-0-32767-sur02.sacramento.ca.ccal.comcast.
net [68.85.196.81]
3 19 ms 17 ms 27 ms xe-1-0-0-0-ar04.fresno.ca.fresno.comcast.net [68
.87.202.241]
4 30 ms 31 ms 28 ms he-1-4-0-0-11-cr01.losangeles.ca.ibone.comcast.n
et [68.86.89.61]
5 26 ms 30 ms 29 ms xe-0-0-0-0-pe01.onewilshire.ca.ibone.comcast.net
[68.86.82.34]
6 29 ms 31 ms 24 ms 50-242-151-62-static.hfc.comcastbusiness.net [50
.242.151.62]
7 24 ms 27 ms 30 ms ae-2.r20.lsanca03.us.bb.gin.ntt.net [129.250.2.2
29]
8 * 129 ms 134 ms ae-6.r20.osakjp02.jp.bb.gin.ntt.net [129.250.4.3
9]
9 129 ms 159 ms 138 ms ae-4.r22.osakjp02.jp.bb.gin.ntt.net [129.250.6.1
88]
10 192 ms 192 ms * ae-8.r20.sngpsi05.sg.bb.gin.ntt.net [129.250.3.1
10]
11 197 ms 201 ms 197 ms ae-2.r00.sngpsi02.sg.bb.gin.ntt.net [129.250.3.1
47]
12 231 ms 227 ms 227 ms 116.51.27.158
13 221 ms * 238 ms ip-182-50-156-222.ip.secureserver.net [182.50.15
6.222]
14 * * 239 ms ip-182-50-156-222.ip.secureserver.net [182.50.15
6.222]
15 227 ms 229 ms 226 ms ip-182-50-157-221.ip.secureserver.net [182.50.15
7.221]
16 * 234 ms 230 ms ip-182-50-156-89.ip.secureserver.net [182.50.156
.89]
17 * * 225 ms ip-203-124-115-1.ip.secureserver.net [203.124.11
5.1]
Trace complete.