I am finding the site quite slow to load. Is this a server thing and will it always be like this or could it be something on my end?
the server load is very light and from what I have seen "processes" the page faster than RCC now.
Can you provide a traceroute so we can see if its a network related issue?
Quote from: rjtx667 on September 04, 2012, 11:49:44 AM
the server load is very light and from what I have seen "processes" the page faster than RCC now.
Can you provide a traceroute so we can see if its a network related issue?
Only if you tell me how. :dontknow:
start -> run -> in the box type "cmd" then press ok
now you have a black box infront of you.
type "tracert ramcharger.net
post the output like below:
i have not noticed any speed problems. everything seems to load at a reasonable speed.
i did that test for Sh!ts and giggles and here is my results.
yeah that one looks pretty good. 86 MS or so to go from Chicago to Dallas, hard to go a whole lot faster than that. :13:
Tracing route to ramcharger.net [50.115.6.130]
over a maximum of 30 hops:
1 6 ms 5 ms 5 ms 192.168.1.1
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 73 ms 79 ms 79 ms 50.115.6.130
Trace complete.
that does not show a lot, but 79ms is not a horrible response time for a decent distance from Dallas.
http://www.colocateusa.net
how does that page load for you?
well I had never used that function before... but here is what it shows to me
:icon_scratch:
My numbers look low compared to everyone else.
Tracing route to ramcharger.net [50.115.6.130]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 15 ms 6 ms 10.77.30.1
3 9 ms 6 ms 8 ms tge7-1.snantx6500-er01.texas.rr.com [24.28.134.1
06]
4 23 ms 14 ms 15 ms 24.175.33.248
5 16 ms 15 ms 15 ms ae23.dllatxl3-cr01.texas.rr.com [24.175.32.146]
6 15 ms 15 ms 23 ms 107.14.17.136
7 17 ms 16 ms 18 ms ae-0-0.ar0.dfw10.tbone.rr.com [66.109.9.105]
8 52 ms 36 ms 35 ms xe-11-1-2.edge9.Dallas1.Level3.net [4.59.32.25]
9 37 ms 38 ms 41 ms ae-4-90.edge2.Dallas1.Level3.net [4.69.145.203]
10 37 ms 36 ms 35 ms COLOCATEUSA.edge2.Dallas1.Level3.net [4.71.220.1
54]
11 36 ms 37 ms 36 ms core1.colocateusa.net [50.115.15.206]
12 35 ms 37 ms 37 ms 130.6.115.50.in-addr.arpa [50.115.6.130]
Trace complete.
lol. the lower the better. :thumbsup:
Tracing route to colocateusa.net [208.75.177.93]
over a maximum of 30 hops:
1 2 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 61 ms 64 ms 69 ms 93.177.75.208.in-addr.arpa [208.75.177.93]
Trace complete.
Why all the timed out?
I think my ISP just sucks. That's what you get for living out in the sticks. You gain privacy but lose on the technology :dontknow:
its not your ISP, its your router at your house.
Some block the traceroute, makes it harder to troubleshoot... but as we have seen, only the "true" nerds use this command anyways.
:laughing4: :breakcomp: :sign0085: