Switching to Rapid Systems Fiber [ Tampa, FL ]

[Runna]

If anyone on Rapid Systems fiber, can post a few trace routes of websites such as,

[direwolf]

Here you go

Tracing route to tampabay.rr.com [24.92.220.60]

over a maximum of 30 hops:

[Runna]

Thanks Direwolf,  4-5th hop tracing wdc.speakeasy.net,  66ms same what I get for around 90% of the sites I try to connect to,  I already spoke with Rapid Systems tech rep earlier today,  I am switching off Verizons end in 5 days, I will post results from switching to Rapid systems.    I also asked to obtain trace route results from their end through email of several sites that I hope to get back soon.

[xs1]

While on my friends fios a few days ago i noticed ungodly pings as well.... especially for fiber.. about 3- 5 th hop was in the 100's tracing to testmy , and tracing to my home pc 10 minutes away was an overall of 98 ms... I dont know why the pings are so bad on fios right now :s

[KingCobra]

While on my friends fios a few days ago i noticed ungodly pings as well.... especially for fiber.. about 3- 5 th hop was in the 100's tracing to testmy , and tracing to my home pc 10 minutes away was an overall of 98 ms... I dont know why the pings are so bad on fios right now :s

Did you look at the route to see where the problem was?

[Runna]

Now on Rapid Systems fiber, the routing with this ISP vs. verizons GNI Routes, huge drop in latencies. 

Here are a few examples,   

Tracing route to www.tampabay.rr.com [24.92.220.60]

over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1

  2    3 ms    2 ms    3 ms  198.77.232.1

  3    4 ms    3 ms    3 ms  rsrouter.rapidsys.com [209.84.253.1]

  4    4 ms    3 ms    3 ms  s3-0-3-155.hsa1.tmp1.bbnplanet.net [4.24.183.137

]

  5    4 ms    4 ms    3 ms  ge-1-2-56.car2.Tampa1.Level3.net [4.68.104.163]

  6    6 ms    21 ms    14 ms  roadrunner.car2.tampa1.level3.net [4.79.174.2]

  7    5 ms    7 ms    6 ms  pos2-0-bhn.tpafl21-cr2.tampabay.rr.com [65.32.8.

158]

  8    5 ms    5 ms    5 ms  at2-0s2.tpafl21-iar1.bhntampa.com [72.31.0.53]

  9    *        *    at2-0s2.tpafl21-iar1.bhntampa.com [72.31.0.53]  reports:

Destination net unreachable.

Trace complete.

Tracing route to wdc.speakeasy.net [66.92.159.2]

over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1

  2    3 ms    3 ms    2 ms  198.77.232.1

  3    3 ms    3 ms    3 ms  rsrouter.rapidsys.com [209.84.253.1]

  4    4 ms    6 ms    3 ms  s3-0-3-155.hsa1.tmp1.bbnplanet.net [4.24.183.137

]

  5    19 ms    5 ms    4 ms  ae-1-55.mp1.Tampa1.Level3.net [4.68.104.129]

  6    *      34 ms    36 ms  ae-0-0.bbr2.washington1.level3.net [4.68.128.210

]

  7    34 ms    38 ms    35 ms  ge-9-2.ipcolo2.Washington1.Level3.net [4.68.121.

172]

  8    35 ms    36 ms    35 ms  unknown.level3.net [166.90.148.50]

  9    35 ms    35 ms    37 ms  dns.wdc1.speakeasy.net [66.92.159.2]

Trace complete.

Tracing route to atl.speakeasy.net [216.27.175.2]

over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1

  2    2 ms    3 ms    2 ms  198.77.232.1

  3    3 ms    3 ms    3 ms  rsrouter.rapidsys.com [209.84.253.1]

  4    7 ms    6 ms    5 ms  s3-0-3-155.hsa1.tmp1.bbnplanet.net [4.24.183.137

]

  5    5 ms    3 ms    6 ms  ae-1-53.mp1.Tampa1.Level3.net [4.68.104.65]

  6    22 ms    23 ms    21 ms  ae-0-0.bbr1.atlanta1.level3.net [64.159.1.45]

  7    22 ms    21 ms    21 ms  ge-11-1.hsa2.Atlanta1.Level3.net [4.68.103.101]

  8    22 ms    22 ms    23 ms  unknown.level3.net [63.210.88.154]

  9    21 ms    21 ms    22 ms  dns.atl1.speakeasy.net [216.27.175.2]

Trace complete.