Let's see your connection speed - Page 7 - The Orange Room

darkstar

Quote:

Originally Posted by aboulzouz

Are you serious guys !!

Are you trying to get a connetion speed by pinging google?

your connection speed is the last mile between the operator DSLam and you !!!

What has google to do in here?

Umm.. Who said we are testing connection speeds with ping?
Well in the morning I was getting around 200ms to google and now its up to 400ms. I compared the traceroutes and I realised that the routes have changedand that the packet now takes a whole different path.

example:
Tracing route to www.tayyar.org [89.185.33.53]
over a maximum of 30 hops:

1 2 ms <1 ms <1 ms
2 17 ms 23 ms 22 ms
3 25 ms 19 ms 19 ms
4 20 ms 22 ms 48 ms
5 35 ms 25 ms 23 ms
6 422 ms 382 ms 399 ms << see the jump in latency, this route here was totally different before, thats what I am trying to say
7 463 ms 557 ms *

The first 5 routes are terranet routers till we get to the gateway which is at route 6.

EDIT: try pinging this please: 85.236.100.66 , thanks

aboulzouz

Quote:

Originally Posted by darkstar

Umm.. Who said we are testing connection speeds with ping?
Well in the morning I was getting around 200ms to google and now its up to 400ms. I compared the traceroutes and I realised that the routes have changedand that the packet now takes a whole different path.

example:
Tracing route to www.tayyar.org [89.185.33.53]
over a maximum of 30 hops:

1 2 ms <1 ms <1 ms
2 17 ms 23 ms 22 ms
3 25 ms 19 ms 19 ms
4 20 ms 22 ms 48 ms
5 35 ms 25 ms 23 ms
6 422 ms 382 ms 399 ms << see the jump in latency, this route here was totally different before, thats what I am trying to say
7 463 ms 557 ms *

The first 5 routes are terranet routers till we get to the gateway which is at route 6.

EDIT: try pinging this please: 85.236.100.66 , thanks

It is based on the network traffic at peak hours.

Some AS try to do load balancing in order to balance the traffic in their network this is why you may get different paths

Führer

Pinging 85.236.100.66 with 32 bytes of data:

Reply from 85.236.100.66: bytes=32 time=362ms TTL=118
Reply from 85.236.100.66: bytes=32 time=364ms TTL=118
Reply from 85.236.100.66: bytes=32 time=361ms TTL=118
Reply from 85.236.100.66: bytes=32 time=364ms TTL=118

Ping statistics for 85.236.100.66:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 361ms, Maximum = 364ms, Average = 362ms

darkstar

Quote:

Originally Posted by aboulzouz

It is based on the network traffic at peak hours.

Some AS try to do load balancing in order to balance the traffic in their network this is why you may get different paths

Well I have been on the same route for over a week now , just today it changed. I'll see how it comes out to be later tonight and tomorrow morning.

Quote:

Originally Posted by Führer

Pinging 85.236.100.66 with 32 bytes of data:

Reply from 85.236.100.66: bytes=32 time=362ms TTL=118
Reply from 85.236.100.66: bytes=32 time=364ms TTL=118
Reply from 85.236.100.66: bytes=32 time=361ms TTL=118
Reply from 85.236.100.66: bytes=32 time=364ms TTL=118

Ping statistics for 85.236.100.66:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 361ms, Maximum = 364ms, Average = 362ms

Thanks Fuhrer :)

Ok, my cousin has wise and I just asked him to try a couple of traceroutes and look at the mind blowing difference:

Tracing route to dedicated22.multiplay.co.uk [85.236.100.66]
over a maximum of 30 hops:

1 30 ms 39 ms 24 ms
2 34 ms 32 ms 32 ms
3 143 ms 116 ms 112 ms
4 153 ms 119 ms 133 ms
5 106 ms 104 ms 133 ms
6 117 ms 122 ms 108 ms
7 125 ms 115 ms 123 ms dedicated22.multiplay.co.uk [85.236.100.66]

Trace complete.

and to tayyar.org

Tracing route to www.tayyar.org
over a maximum of 30 hops:

1 95 ms 32 ms 25 ms
2 74 ms 47 ms 35 ms
3 135 ms 111 ms 119 ms
4 113 ms 141 ms 116 ms

5 150 ms 115 ms *
6 129 ms 119 ms 116 ms

7 129 ms 160 ms 144 ms
8 * * 147 ms
9 152 ms 173 ms 133 ms
10 182 ms 130 ms 130 ms
11 136 ms 195 ms 137 ms
12 139 ms 137 ms 133 ms
13 144 ms 131 ms 130 ms
14 127 ms 141 ms 152 ms
15 163 ms 122 ms 126 ms 89.185.33.53

Trace complete.