• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Site really slow

ozonetrooper

ozonetrooper

Android Expert
Site has been really slow my way for the past week.

This is what I see on my side (not good) :

C:\Windows\System32>tracert 147.182.165.119

Tracing route to newdo.neverstill.com [147.182.165.119]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 10.0.0.1
2 15 ms 13 ms 10 ms 10.54.155.131
3 11 ms 13 ms 12 ms po-307-340-rur202.lamarque.tx.houston.comcast.net [96.216.183.205]
4 12 ms 13 ms 12 ms po-200-xar02.lamarque.tx.houston.comcast.net [96.217.21.241]
5 12 ms 15 ms 27 ms po-2-xar01.lamarque.tx.houston.comcast.net [68.85.246.21]
6 17 ms 16 ms 17 ms be-325-arsc1.bearcreek.tx.houston.comcast.net [96.217.21.141]
7 * * * Request timed out.
8 45 ms * * ae2.3610.edge5.Newark1.net.lumen.tech [4.69.209.74]
9 44 ms 70 ms 45 ms digital-oce.edge5.newark1.level3.net [4.28.0.46]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 46 ms 43 ms 44 ms newdo.neverstill.com [147.182.165.119]
 
Upvote 0 Downvote
FWIW here's a couple of traceroutes from where I am. I haven't noticed any slowdown with these fora.

~ % traceroute 147.182.165.119
traceroute to 147.182.165.119 (147.182.165.119), 64 hops max, 40 byte packets
1 192.168.0.1 (192.168.0.1) 14.515 ms 4.605 ms 7.182 ms
2 192.168.1.1 (192.168.1.1) 4.373 ms 20.265 ms 5.021 ms
3 10.40.0.1 (10.40.0.1) 6.872 ms 9.042 ms 9.481 ms
4 60.31.149.77 (60.31.149.77) 6.137 ms 10.560 ms 6.514 ms
5 116.115.64.17 (116.115.64.17) 14.059 ms
116.115.64.61 (116.115.64.61) 19.814 ms
116.115.64.17 (116.115.64.17) 12.452 ms
6 * * *
7 219.158.16.70 (219.158.16.70) 23.175 ms *
219.158.3.138 (219.158.3.138) 25.372 ms
8 219.158.16.94 (219.158.16.94) 168.016 ms 164.465 ms
219.158.96.26 (219.158.96.26) 179.401 ms
9 ix-ae-29-0.tcore2.lvw-losangeles.as6453.net (207.45.219.8) 165.888 ms 165.659 ms 163.680 ms
10 * if-bundle-34-2.qcore2.lvw-losangeles.as6453.net (207.45.219.128) 331.896 ms *
11 * * *
12 if-ae-12-2.tcore4.njy-newark.as6453.net (66.198.155.33) 359.532 ms 247.367 ms 247.303 ms
13 66.198.111.7 (66.198.111.7) 230.595 ms 274.799 ms 241.456 ms
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 newdo.neverstill.com (147.182.165.119) 347.421 ms 330.102 ms 260.383 ms

mike@mx:~
$ traceroute 147.182.165.119
traceroute to 147.182.165.119 (147.182.165.119), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 4.215 ms 4.617 ms 4.581 ms
2 192.168.1.1 (192.168.1.1) 3.993 ms 3.910 ms 3.961 ms
3 10.40.0.1 (10.40.0.1) 7.881 ms 7.855 ms 7.826 ms
4 60.31.149.77 (60.31.149.77) 7.488 ms 7.451 ms 7.424 ms
5 * * *
6 219.158.9.202 (219.158.9.202) 13.349 ms * *
7 219.158.10.78 (219.158.10.78) 20.050 ms 219.158.16.70 (219.158.16.70) 20.023 ms *
8 219.158.16.98 (219.158.16.98) 162.610 ms 219.158.17.82 (219.158.17.82) 164.521 ms 219.158.16.98 (219.158.16.98)
162.426 ms
9 ix-ae-29-0.tcore2.lvw-losangeles.as6453.net (207.45.219.8) 162.398 ms 162.813 ms 159.873 ms
10 * * *
11 if-bundle-26-2.qcore2.aeq-ashburn.as6453.net (207.45.219.137) 245.908 ms * 305.421 ms
12 if-ae-12-2.tcore4.njy-newark.as6453.net (66.198.155.33) 305.364 ms 305.320 ms 305.198 ms
13 66.198.111.7 (66.198.111.7) 305.136 ms 306.965 ms 306.782 ms
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 newdo.neverstill.com (147.182.165.119) 322.779 ms 322.753 ms 322.676 ms
 
Last edited:
Yup, same time outs after the newark hop !

sometimes servers are set up not to divulge information like pings and tracerts, but as the site is having issues I take this to be a valid time out/hand off to the next one in line that is doing the same thing for 6 hops.

Not good for a guy on a slow connection, I recently switched to 1 gig fiber, and the site is still having lags on my side.
 
I vote Rob gives you the phone number to call in a fix when it is needed ...

smilewinkgrin
 
You must log in or register to reply here.
Back
Top Bottom