Page 2 of 2 FirstFirst 12
Results 26 to 33 of 33
  1. #26
    Quote Originally Posted by dotHostel View Post
    Or ... SecuredServers don't want to host the OP's company.
    Yup, also possible. Instead of coming out and saying you don't want someone's business, you can simply answer their presales questions in a way that makes your company not look like it meets the customer's requirements. All told, this is really all speculation at this point.
    IOFLOOD.com -- We Love Servers
    Phoenix, AZ Dedicated Servers in under an hour
    ★ Ryzen 9: 7950x3D ★ Dual E5-2680v4 Xeon ★
    Contact Us: sales@ioflood.com

  2. #27
    Join Date
    Oct 2002
    Location
    Vancouver, B.C.
    Posts
    2,699
    Quote Originally Posted by funkywizard View Post
    I would say Chicago is not going to be any better than Phoenix to reach the target location. Certainly Chicago is not a bad option, but I wouldn't pick it over Phoenix due to proximity here.
    In terms of pure geographical distance, they may be pretty similar, but Chicago is a much better connected city. I don't think that many networks have transport directly to Phoenix from Dallas, so there's a much greater likelihood of taking a less optimal path.

    Quote Originally Posted by dotHostel View Post
    I guess your customers are used to latency. In your case I think it is more important availability than reduce latency few miliseconds as you will have high latency anyway.
    It's at least an additional 50ms, possibly much more depending on the path, not just a few.

    Quote Originally Posted by dotHostel View Post
    there is no clear indication to suggest FL instead AZ, and, as I said before, not all routes from South America networks peer directly with Florida data centers networks. You can't take for granted the latency will be lower. The sales rep must know something (we don't) about SecuredServers connectivity with the Caribbean networks precluding the use of their data center to justify his/her action.
    Even if they don't peer in Florida, they will still usually have upstreams there. It doesn't make any sense to haul traffic further than they have to, as transport costs money. The cases where you see issues with traffic backtracking around is usually due to two networks having peering between each other in some locations and not others, where it's still cheaper to pay for transport than to send the traffic out their upstreams.

    Yes, a far away server with good routing can be better than a near server with bad routing, but it's still nowhere as good as a near server with good routing, and a far away server with bad routing is still considerably worse than a near server with bad routing. Both routing and distance should be considered, instead of just ignoring one or the other. In this case, Phoenix is quite far (almost opposite coast), so it's a factor that should not be ignored.

    As I said before, choosing between Phoenix and Miami is a false dichotomy. There are cities where you can find servers as cheap as Phoenix, but much closer to Miami.
    ASTUTE INTERNET: Advanced, customized, and scalable solutions with AS54527 Premium Performance and Canadian Optimized Network (Level3, Shaw, CogecoPeer1, GTT/Tinet),
    AS63213 Cost Effective High Performance Network (Cogent, HE, GTT/Tinet)
    Dedicated Hosting, Colo, Bandwidth, and Fiber out of Vancouver, Seattle, LA, Toronto, NYC, and Miami

  3. #28
    Most of your Phoenix transport is going to go through Dallas heading east, so it's not exactly a roundabout path your data would take. Chicago may be well connected, but so is Dallas. It's not like you're going to have traffic go PHX -> LA -> Miami, so you may add an extra hop going to Dallas whereas Chicago would interconnect locally, but geographically it's still fine.

    Not making the point that CHI is a bad choice, just not really that much better than PHX in the situation mentioned.
    IOFLOOD.com -- We Love Servers
    Phoenix, AZ Dedicated Servers in under an hour
    ★ Ryzen 9: 7950x3D ★ Dual E5-2680v4 Xeon ★
    Contact Us: sales@ioflood.com

  4. #29
    Join Date
    Apr 2009
    Location
    USA / UK
    Posts
    4,577
    You might want to take a look at Atlanta for southeast US. Virtually next door to Florida and plenty of good providers there (and a major exchange point as far as traffic is concerned).

    As far as lag goes, East to West coast lag can be anywhere from 40 to 90 ms - for your application however I doubt it will matter much.
    RAM Host -- USA Premium & Budget Linux Hosting
    █ Featuring Powerful cPanel Shared Hosting
    █ & Premium Virtual Dedicated Servers
    Follow us on Twitter

  5. #30
    Join Date
    Jun 2005
    Posts
    2,752
    Quote Originally Posted by hhw View Post
    It's at least an additional 50ms, possibly much more depending on the path, not just a few.

    Even if they don't peer in Florida, they will still usually have upstreams there. It doesn't make any sense to haul traffic further than they have to, as transport costs money. The cases where you see issues with traffic backtracking around is usually due to two networks having peering between each other in some locations and not others, where it's still cheaper to pay for transport than to send the traffic out their upstreams.
    not be ignored.

    [...]

    As I said before, choosing between Phoenix and Miami is a false dichotomy. There are cities where you can find servers as cheap as Phoenix, but much closer to Miami.
    Please take a look at the following traceroutes from Sao Paulo, Brazil:

    C:\>tracert www.hostdime.com

    Tracing route to www.hostdime.com [72.29.79.120]
    over a maximum of 30 hops:


    6 34 ms * 33 ms Xe0-1-2-0-grtsaosi3.red.telefonica-wholesale.net [213.140.39.137]
    7 139 ms 140 ms * Xe4-1-1-0-grtmiabr4.red.telefonica-wholesale.net [84.16.15.58]
    8 170 ms 252 ms 177 ms Xe7-1-0-0-grtnycpt3.red.telefonica-wholesale.net [94.142.122.221]
    9 190 ms 175 ms 176 ms xe-8-1-0.nyc20.ip4.tinet.net [77.67.78.1]
    10 252 ms 223 ms 224 ms xe-0-0-0.mia10.ip4.tinet.net [89.149.186.237]
    11 231 ms 231 ms 243 ms HostDime-gw.1ge.tinet.net [213.200.73.30]
    12 359 ms 396 ms 245 ms core-10gigabit-ethernet-peering.dimenoc.com [72.29.88.34]
    13 230 ms 226 ms 229 ms 72-29-79-119.static.dimenoc.com [72.29.79.119]
    14 232 ms 231 ms 219 ms hdusvps.dimenoc.com [72.29.79.120]


    C:\>tracert www.softlayer.com

    Tracing route to www.softlayer.com [66.228.118.51]
    over a maximum of 30 hops:


    6 34 ms 45 ms 34 ms Xe-1-1-0-0-grtsaosi2.red.telefonica-wholesale.net [84.16.9.109]
    7 141 ms 192 ms 183 ms Xe5-0-0-0-grtmiabr3.red.telefonica-wholesale.net [213.140.43.109]
    8 141 ms 146 ms 142 ms Xe2-0-6-0-grtmiana2.red.telefonica-wholesale.net [94.142.119.229]
    9 641 ms * 142 ms 213.140.51.190
    10 173 ms 174 ms 173 ms po1.slr01.sr01.dal01.networklayer.com [66.228.118.138]
    11 172 ms 170 ms 173 ms www.softlayer.com [66.228.118.51]


    C:\>tracert www.securedservers.com

    Tracing route to www.securedservers.com [209.188.23.6]
    over a maximum of 30 hops:


    6 34 ms 34 ms 32 ms Xe4-2-0-0-grtsanem2.red.telefonica-wholesale.net [213.140.39.69]
    7 138 ms 141 ms 141 ms Xe2-1-3-0-grtmiabr3.red.telefonica-wholesale.net [94.142.123.250]
    8 166 ms 167 ms 163 ms Xe1-1-2-0-grtwaseq3.red.telefonica-wholesale.net [213.140.36.50]
    9 * 174 ms * 213.140.55.90
    10 * 212 ms 225 ms CWIE-LLC.TenGigabitEthernet6-1.ar6.PHX1.gblx.net [64.211.166.134]
    11 209 ms 214 ms 219 ms 209.188.23.6


    C:\>tracert www.atlantic.net

    Tracing route to www.atlantic.net [209.208.9.38]
    over a maximum of 30 hops:


    6 108 ms 32 ms 35 ms Xe7-2-0-0-grtsanem2.red.telefonica-wholesale.net [84.16.10.233]
    7 138 ms 140 ms 138 ms Xe-4-1-2-0-grtmiabr4.red.telefonica-wholesale.net [94.142.124.174]
    8 172 ms 175 ms 170 ms Xe7-1-0-0-grtwaseq4.red.telefonica-wholesale.net [94.142.122.157]
    9 175 ms 175 ms 174 ms xe-7-3-0.edge3.Washington4.Level3.net [4.53.112.41]
    10 178 ms 175 ms 183 ms vlan90.csw4.Washington1.Level3.net [4.69.149.254]
    11 180 ms 165 ms 187 ms ae-91-91.ebr1.Washington1.Level3.net [4.69.134.141]
    12 188 ms 178 ms 179 ms ae-2-2.ebr3.Atlanta2.Level3.net [4.69.132.85]
    13 189 ms 189 ms 188 ms ae-63-63.csw1.Atlanta2.Level3.net [4.69.148.242]
    14 186 ms 192 ms 197 ms ae-61-61.ebr1.Atlanta2.Level3.net [4.69.148.233]
    15 169 ms * 874 ms ae-1-8.bar1.Orlando1.Level3.net [4.69.137.149]
    16 166 ms 167 ms 168 ms ae-6-6.car1.Orlando1.Level3.net [4.69.133.77]
    17 171 ms * 168 ms ATLANTIC.NE.car1.Orlando1.Level3.net [63.209.98.66]
    18 176 ms 174 ms 174 ms andc-abr-1-g3-13.atlantic.net [209.208.6.50]
    19 * 176 ms 176 ms andc-vl-950-csw-17.atlantic.net [69.28.72.179]
    20 166 ms 176 ms * www.atlantic.net [209.208.9.38]
    21 180 ms 180 ms 177 ms www.atlantic.net [209.208.9.38]


    C:\>tracert www.terremark.com

    Tracing route to terremark.com [72.46.236.35]
    over a maximum of 30 hops:

    6 32 ms 54 ms 35 ms Xe7-2-0-0-grtsaosi2.red.telefonica-wholesale.net [213.140.39.117]
    7 140 ms 138 ms 141 ms Xe5-1-2-0-grtmiabr4.red.telefonica-wholesale.net [94.142.124.222]
    8 173 ms 173 ms 174 ms Xe2-1-1-0-grtdaleq3.red.telefonica-wholesale.net [94.142.125.49]
    9 172 ms * * 192.205.35.249
    10 179 ms 177 ms 174 ms cr2.dlstx.ip.att.net [12.122.214.250]
    11 176 ms 179 ms 176 ms cr84.dlstx.ip.att.net [12.123.18.249]
    12 174 ms 177 ms 181 ms gar3.dlrtx.ip.att.net [12.122.139.173]
    13 176 ms 181 ms 175 ms 12.86.210.30
    14 174 ms 177 ms 180 ms g0-5-0-2.br2.dfw3.terremark.net [66.165.161.182]
    15 181 ms 178 ms 180 ms t0-0-0-7.br2.mia.terremark.net [66.165.161.229]
    16 179 ms 177 ms 176 ms t9-1.gw1.mia.terremark.net [66.165.161.94]
    17 181 ms 175 ms 175 ms 66.165.170.14
    18 183 ms * 175 ms 72.46.239.66
    19 176 ms 186 ms 178 ms 72.46.239.73
    20 177 ms 177 ms 176 ms www.terremark.com [72.46.236.35]


    C:\>tracert www.fdcservers.com

    Tracing route to www.fdcservers.com [66.90.66.155]
    over a maximum of 30 hops:

    1 2 ms 5 ms 6 ms 192.168.1.1
    2 * * * Request timed out.
    3 33 ms 31 ms 33 ms 201-0-92-177.dsl.telesp.net.br [201.0.92.177]
    4 33 ms 34 ms 30 ms 200-148-89-49.dsl.telesp.net.br [200.148.89.49]
    5 106 ms 30 ms 70 ms 201-63-253-134.customer.tdatabrasil.net.br [201.63.253.134]
    6 36 ms 167 ms 33 ms 213.140.50.53
    7 142 ms 140 ms 145 ms Xe4-1-1-0-grtmiabr4.red.telefonica-wholesale.net [84.16.15.58]
    8 * * 142 ms Xe6-1-1-0-grtmiana3.red.telefonica-wholesale.net [94.142.123.1]
    9 143 ms 141 ms * if-2-8.icore1.MLN-Miami.as6453.net [66.110.9.81]
    10 191 ms * 174 ms Vlan1276.icore2.DTX-Dallas.as6453.net [66.110.9.90]
    11 * * * Request timed out.
    12 205 ms * 205 ms Vlan563.icore1.CT8-Chicago.as6453.net [206.82.141.82]
    13 225 ms 207 ms 250 ms 66.90.127.177 [66.90.127.177]
    14 202 ms 199 ms 201 ms www.fdcservers.net [66.90.66.155]

    C:\>tracert www.colocrossing.com

    Tracing route to colocrossing.com [216.246.49.26]
    over a maximum of 30 hops:

    1 3 ms 3 ms 3 ms 192.168.1.1
    2 * * * Request timed out.
    3 32 ms * 36 ms 201-0-93-17.dsl.telesp.net.br [201.0.93.17]
    4 43 ms 34 ms 33 ms 200-148-89-61.dsl.telesp.net.br [200.148.89.61]
    5 32 ms 32 ms 143 ms 187-100-57-93.dsl.telesp.net.br [187.100.57.93]
    6 86 ms 37 ms 40 ms 213.140.51.233
    7 142 ms 140 ms 139 ms Xe2-0-3-0-grtmiabr3.red.telefonica-wholesale.net [94.142.123.254]
    8 143 ms 200 ms 143 ms So4-1-0-0-grtmiana3.red.telefonica-wholesale.net [213.140.37.37]
    9 * 144 ms 143 ms if-2-8.icore1.MLN-Miami.as6453.net [66.110.9.81]
    10 188 ms 178 ms 179 ms Vlan1276.icore2.DTX-Dallas.as6453.net [66.110.9.90]
    11 363 ms 200 ms 203 ms te7-1.ar5.DAL2.gblx.net [64.215.195.201]
    12 202 ms 200 ms 201 ms xe-2-0-5.ar2.ord1.us.nlayer.net [69.31.111.222]
    13 209 ms 204 ms 207 ms ae2-30g.cr2.ord1.us.nlayer.net [69.31.111.149]
    14 206 ms 204 ms 205 ms po6.ar2.ord1.us.scnet.net [69.31.111.6]
    15 * 206 ms 221 ms 62.po2.ar2.ord6.us.scnet.net [75.102.3.230]
    16 210 ms 207 ms 208 ms as36352.po4.ar2.ord6.us.scnet.net [204.93.192.190]
    17 203 ms 201 ms 201 ms ge146.aggr.chi.colocrossing.com [75.102.34.250]
    18 202 ms 207 ms 209 ms mail.colocrossing.com [216.246.49.26]
    Last edited by dotHostel; 02-16-2011 at 04:53 AM.
    You will only find out how good a provider is when the going gets tough

  6. #31
    Join Date
    Jun 2005
    Posts
    2,752
    C:\tracert wwww.interserver.com

    Tracing route to interserver.com [66.45.228.100]
    over a maximum of 30 hops:


    6 41 ms 38 ms * 213.140.51.237
    7 143 ms 143 ms 143 ms Xe4-1-1-0-grtmiabr3.red.telefonica-wholesale.net [213.140.36.13]
    8 189 ms 170 ms 163 ms Xe-2-1-0-0-grtwaseq4.red.telefonica-wholesale.net [94.142.124.117]
    9 163 ms 166 ms 166 ms 213.140.53.26
    10 171 ms 164 ms 162 ms xe-3-0-0.cr1.dca2.us.above.net [64.125.26.237]
    11 175 ms 179 ms 166 ms xe-1-0-0.cr2.dca2.us.above.net [64.125.28.250]
    12 177 ms 168 ms 170 ms xe-3-2-0.cr2.lga5.us.above.net [64.125.26.110]
    13 179 ms 172 ms 172 ms xe-0-1-0.er2.lga5.us.above.net [64.125.27.65]
    14 180 ms * 192 ms 64.124.44.213.interserver.com [64.124.44.213]
    15 183 ms 181 ms 190 ms vl562.cr1.teb1.us.as19318.net [64.20.32.174]
    16 173 ms 167 ms 171 ms nucleus.interserver.net [66.45.228.100]


    C:\Users\Coppe>tracert www.voxel.net

    Tracing route to www.voxel.net [72.251.192.236]
    over a maximum of 30 hops:

    6 33 ms * 34 ms Xe5-0-3-0-grtsaosi2.red.telefonica-wholesale.net [84.16.7.153]
    7 148 ms 139 ms 141 ms Xe4-1-1-0-grtmiabr3.red.telefonica-wholesale.net [213.140.36.13]
    8 166 ms 165 ms 177 ms Xe9-0-0-0-grtwaseq4.red.telefonica-wholesale.net [213.140.36.177]
    9 171 ms 165 ms 165 ms ash-bb1-link.telia.net [213.248.77.213]
    10 187 ms 179 ms 170 ms voxel-ic-129445-ash-bb1.c.telia.net [213.248.91.50]
    11 358 ms 198 ms 225 ms 0.te6-2.tsr1.ewr1.us.voxel.net [208.122.44.105]
    12 180 ms 187 ms 188 ms 0.te1-49.esr2.ldj1.us.voxel.net [208.122.44.150]
    13 180 ms 181 ms 182 ms app1.ldj1.us.voxel.net [72.251.192.236]



    C:\>tracert www.gnax.com

    Tracing route to www.gnax.com [207.210.69.71]
    over a maximum of 30 hops:


    6 34 ms * 34 ms 213.140.39.41
    7 138 ms 139 ms 141 ms Xe6-0-1-0-grtmiabr3.red.telefonica-wholesale.net [84.16.15.42]
    8 171 ms 165 ms 172 ms Xe7-1-0-0-grtwaseq4.red.telefonica-wholesale.net [94.142.122.157]
    9 175 ms 163 ms 172 ms ash-bb1-link.telia.net [213.248.77.213]
    10 192 ms 209 ms 189 ms atl-bb1-link.telia.net [80.91.248.137]
    11 190 ms * 193 ms globalnet-127291-atl-bb1.c.telia.net [213.248.90.54]
    12 199 ms 215 ms 255 ms atl-l3-2-g0-2.gnax.net [209.51.130.38]
    13 180 ms 179 ms 185 ms web.gnax.net [207.210.69.71]
    Last edited by dotHostel; 02-16-2011 at 05:08 AM.
    You will only find out how good a provider is when the going gets tough

  7. #32
    Join Date
    Oct 2002
    Location
    Vancouver, B.C.
    Posts
    2,699
    Quote Originally Posted by funkywizard View Post
    Most of your Phoenix transport is going to go through Dallas heading east, so it's not exactly a roundabout path your data would take.
    Most, but not all. There are going to be networks out there that do have transport to Phoenix, but not through Dallas.
    e.g. http://www.nlayer.com/network

    But point taken, the difference may not be that great in those cases, and traffic that takes the proper path will be comparable.

    Quote Originally Posted by dotHostel View Post
    Please take a look at the following traceroutes from Sao Paulo, Brazil:
    Telefonica is an extreme example of what I described of incomplete peering. Nobody peers with them in Miami because they insist on being paid there (even by the likes of AT&T or Level3), but will still peer in other cities, which is why you see most of those traceroutes go to Dallas and back. It's not because Telefonica doesn't have connectivity in Miami. One unreasonable network, despite being a major player in the region, doesn't mean geography doesn't matter. It just means you should avoid such networks if possible.
    ASTUTE INTERNET: Advanced, customized, and scalable solutions with AS54527 Premium Performance and Canadian Optimized Network (Level3, Shaw, CogecoPeer1, GTT/Tinet),
    AS63213 Cost Effective High Performance Network (Cogent, HE, GTT/Tinet)
    Dedicated Hosting, Colo, Bandwidth, and Fiber out of Vancouver, Seattle, LA, Toronto, NYC, and Miami

  8. #33
    Join Date
    Jun 2005
    Posts
    2,752
    /unsubscribe
    You will only find out how good a provider is when the going gets tough

Page 2 of 2 FirstFirst 12

Similar Threads

  1. west? east? or central?
    By linktome in forum Colocation, Data Centers, IP Space and Networks
    Replies: 7
    Last Post: 04-04-2007, 01:50 PM
  2. cogent east to west issues?
    By jeev in forum Dedicated Server
    Replies: 4
    Last Post: 04-26-2005, 03:40 PM
  3. East or West US better for Euro?
    By HighCommit in forum Colocation, Data Centers, IP Space and Networks
    Replies: 2
    Last Post: 07-07-2004, 07:20 PM
  4. east vs. west bandwidth
    By Maxine in forum Dedicated Server
    Replies: 4
    Last Post: 05-03-2004, 04:27 AM
  5. East/West Colocation
    By MSolutions in forum Colocation, Data Centers, IP Space and Networks
    Replies: 11
    Last Post: 11-10-2003, 08:17 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •