Insane Lag Between TSTT & FLOW

[SPK]

Did some tests just now, got this on my 2mbps Blink:

TO FLOW:



TO NYC:



TO CALIFORNIA:



TO UK:

[TriniXaeno]

Well I know this is just beating a dead horse at this stage, but here are ping results to our very own site, www.carigamers.com, taken a few minutes ago.

From Flow, an impressive 100ms

Pinging carigamers.com [209.59.162.27] with 32 bytes o
Reply from 209.59.162.27: bytes=32 time=102ms TTL=49
Reply from 209.59.162.27: bytes=32 time=100ms TTL=49
Reply from 209.59.162.27: bytes=32 time=105ms TTL=49
Reply from 209.59.162.27: bytes=32 time=104ms TTL=49

From TSTT/Blink, a piddling 445ms. Shame on you tstt, shame on you.

Pinging carigamers.com [209.59.162.27] with 32 bytes of
Reply from 209.59.162.27: bytes=32 time=445ms TTL=52
Reply from 209.59.162.27: bytes=32 time=472ms TTL=52
Reply from 209.59.162.27: bytes=32 time=488ms TTL=52
Reply from 209.59.162.27: bytes=32 time=493ms TTL=52

Think I'll be canceling my blink.

[woodyear99]

Blink.......it's that fast lol

[Philosophical45]

Blink prolly don't like u NGW... my response times arent that bad.

Pinging carigamers.com [209.59.162.27] with 32 bytes of data:
Reply from 209.59.162.27: bytes=32 time=123ms TTL=51
Reply from 209.59.162.27: bytes=32 time=122ms TTL=51
Reply from 209.59.162.27: bytes=32 time=120ms TTL=51
Reply from 209.59.162.27: bytes=32 time=122ms TTL=51

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

[TriniXaeno]

All Blinks are not created equal.

Run a traceroute, should be interesting to see where the difference lies.

[W1nTry]

All Blinks are not created equal.

Run a traceroute, should be interesting to see where the difference lies.

QFMFT

[SPK]

Ok I just did one from my connection @ home to Carigamers (both ping and trace route):



ping www.carigamers.com

Pinging carigamers.com [209.59.162.27] with 32 bytes of data:

Reply from 209.59.162.27: bytes=32 time=113ms TTL=43
Reply from 209.59.162.27: bytes=32 time=113ms TTL=43
Reply from 209.59.162.27: bytes=32 time=111ms TTL=43
Reply from 209.59.162.27: bytes=32 time=114ms TTL=43

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

tracert www.carigamers.com

Tracing route to carigamers.com [209.59.162.27]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.2.1
  2     1 ms     1 ms     1 ms  192.168.1.1
  3    35 ms    39 ms    39 ms  cuscon129501.tstt.net.tt [190.59.128.1]
  4    29 ms    28 ms    29 ms  201.238.123.42.business.static.tstt.net.tt [201.238.123.42]
  5    29 ms    28 ms    28 ms  201.238.77.22.business.static.tstt.net.tt [201.238.77.22]
  6    28 ms    28 ms    27 ms  201.238.77.21.business.static.tstt.net.tt [201.238.77.21]
  7    29 ms    29 ms    28 ms  cuscon66795.tstt.net.tt [190.58.140.13]
  8    88 ms    87 ms    89 ms  208.172.108.41
  9    92 ms    91 ms    93 ms  cr1-pos-0-3-1-0.miami.savvis.net [208.172.99.93]
 10   105 ms   104 ms   105 ms  cr2-pos-0-0-0-0.Washington.savvis.net [204.70.192.54]
 11   103 ms   104 ms   103 ms  acr2-so-4-0-0.washington.savvis.net [204.70.196.182]
 12   112 ms   112 ms   114 ms  206.24.225.226
 13   114 ms   114 ms   112 ms  lw-core2-ge4.rtr.liquidweb.com [209.59.157.26]
 14   116 ms   116 ms   116 ms  lw-dc1-dist5-ge2.rtr.liquidweb.com [209.59.157.74]
 15   116 ms   116 ms   116 ms  vz010.liquidweb.com [209.59.162.1]
 16   111 ms   114 ms   111 ms  host.carigamers.com [209.59.162.27]

Trace complete.

[Redlum08]

Ran this Trace from home in New York..

Tracing route to carigamers.com [209.59.162.27]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     6 ms     5 ms     5 ms  10.70.224.1
  3     6 ms     5 ms     5 ms  ge-3-1-nycmnyj-rtr1.nyc.rr.com [24.29.104.45]
  4     7 ms     6 ms     6 ms  pos2-0nycmnyl-rtr2.nyc.rr.com [24.29.100.122]
  5     7 ms     5 ms     5 ms  gig15-0-0-nycmnyrdc-rtr1.nyc.rr.com [24.29.130.189]
  6     7 ms     7 ms     8 ms  tenge-4-2-0-nwrknjmd-rtr1.nyc.rr.com [24.29.97.18]
  7     9 ms     7 ms     9 ms  xe-10-3-0.edge2.Newark1.Level3.net [4.79.188.33]
  8     8 ms    17 ms    17 ms  ae-31-51.ebr1.Newark1.Level3.net [4.68.99.30]
  9    18 ms    17 ms    17 ms  ae-1-100.ebr2.Newark1.Level3.net [4.69.132.22]
 10    13 ms    13 ms    13 ms  ae-4-4.ebr2.Washington1.Level3.net [4.69.132.101]
 11    29 ms    29 ms    29 ms  ae-2-2.ebr2.Chicago2.Level3.net [4.69.132.69]
 12    28 ms    36 ms    36 ms  ae-5.ebr2.Chicago1.Level3.net [4.69.140.193]
 13    29 ms    39 ms    30 ms  ae-21-54.car1.Chicago1.Level3.net [4.68.101.98]
 14    38 ms    37 ms    37 ms  WBS-CONNECT.edge5.Chicago1.Level3.net [4.71.182.14]
 15    37 ms    37 ms    39 ms  lw-core4-ge10.rtr.liquidweb.com [209.59.157.137]
 16    41 ms    41 ms    41 ms  lw-core2-ge5.rtr.liquidweb.com [209.59.157.113]
 17    41 ms    41 ms    42 ms  lw-dc1-dist5-ge2.rtr.liquidweb.com [209.59.157.74]
 18    40 ms    41 ms    42 ms  vz010.liquidweb.com [209.59.162.1]
 19    41 ms    43 ms    40 ms  host.carigamers.com [209.59.162.27]

Trace complete.


Ping from New York...

Pinging 209.59.162.27 with 32 bytes of data:
Reply from 209.59.162.27: bytes=32 time=41ms TTL=45
Reply from 209.59.162.27: bytes=32 time=41ms TTL=45
Reply from 209.59.162.27: bytes=32 time=40ms TTL=45
Reply from 209.59.162.27: bytes=32 time=40ms TTL=45

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

[TriniXaeno]

* NoobGoneWild kills redlum for having imba internet