Traceroute & times of lag

[Revenant]

Tracing route to heroserver.bounceme.net [67.205.124.138]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.254
2 23 ms * 23 ms b-ras2.prp.dublin.eircom.net [159.134.155.6]
3 24 ms 23 ms 23 ms 86.43.246.1
4 31 ms 23 ms 23 ms tenge-3-1-1.core2.prp.core.eircom.net [86.43.252
.69]
5 23 ms 22 ms 23 ms tenge-2-2-1.pe2.crz.crz-crz.eircom.net [86.43.25
2.142]
6 93 ms 93 ms 105 ms 86.43.244.41
7 94 ms 93 ms 93 ms 83.71.113.110
8 94 ms 94 ms 94 ms xe-1-0-0.paix.nyc-telx-dis-1.peer1.net [198.32.1
18.146]
9 * * * Request timed out.
10 106 ms 110 ms 105 ms te6-3.cl-core05.peer1.mtl.iweb.com [216.187.90.1
34]
11 105 ms 106 ms 105 ms te9-7.cl-vcore05.mtl.iweb.com [67.205.127.206]
12 105 ms 106 ms 105 ms te8-2.v0688.cl-vcore08.mtl.iweb.com [67.205.127.
190]
13 107 ms 106 ms 105 ms ip-67-205-124-138.static.privatedns.com [67.205.
124.138]

Trace complete.

Pinging heroserver.bounceme.net [67.205.124.138] with 32 bytes of data:
Reply from 67.205.124.138: bytes=32 time=106ms TTL=50
Reply from 67.205.124.138: bytes=32 time=106ms TTL=50
Reply from 67.205.124.138: bytes=32 time=106ms TTL=50
Reply from 67.205.124.138: bytes=32 time=107ms TTL=50

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

10:50 AM GMT