Results 1 to 23 of 23
  1. #1

    Ubiquity and network to Europe

    Since 2 weeks of so, we're having horrible connections between Europe and our servers in the United States (Ubiqiuty).
    Our monitoring server is located in Chicago and is constantly sending false alerts that servers are offline.
    Even connectivity between their own POPs (Chicago to Los Angeles) fails frequently.
    Ticket has been open since the 2nd of March, and each time they are putting the blame on one of their carriers.

    Is anyone having the same kind of issues with them?

    Here some traceroutes:
    Code:
    traceroute to 217.18.70.7 (217.18.70.7), 30 hops max, 40 byte packets
     1  64.120.12.17.novanetworks.net (64.120.12.17)  0.330 ms  0.420 ms  0.549 ms
     2  g0-6.cr01.ord01.mzima.net (72.37.148.177)  4.099 ms  4.095 ms  4.096 ms
     3  te4-5.cr01.lga01.us.mzima.net (69.174.120.73)  21.936 ms  21.988 ms  21.971 ms
     4  gi3-0.nyc-002-inter-1.interoute.net (198.32.160.102)  22.179 ms  22.184 ms *
     5  * * *
     6  * * *
     7  * * *
     8  * * *
     9  * * *
    10  * * *
    11  * * *
    12  * * *
    13  * * *
    14  * * *
    15  * * *
    16  * * *
    17  * * *
    18  * * *
    19  * * *
    20  * * *
    21  * * *
    22  * * *
    23  * * *
    24  * * *
    25  * * *
    26  * * *
    27  * * *
    28  * * *
    29  * * *
    30  * * *
    Code:
    traceroute to frog.serverffs.com (94.23.26.143), 30 hops max, 40 byte packets
     1  64.120.12.17.novanetworks.net (64.120.12.17)  0.315 ms  0.421 ms  0.537 ms
     2  te1-4.ar1.ord1.us.nlayer.net (69.31.111.65)  1.264 ms  1.347 ms  1.452 ms
     3  ae1-40g.cr2.ord1.us.nlayer.net (69.31.111.137)  0.975 ms  0.958 ms  0.988 ms
     4  te8-3.ar3.CHI2.gblx.net (69.31.110.225)  1.366 ms  1.410 ms te9-3.ar3.CHI2.gblx.net (69.31.110.233)  1.496 ms
     5  * * *
     6  * * *
     7  * * *
     8  * * *
     9  * * *
    10  * * *
    11  * * *
    12  * * *
    13  * * *
    14  * * *
    15  * * *
    16  * * *
    17  * * *
    18  * * *
    19  * * *
    20  * * *
    21  * * *
    22  * * *
    23  * * *
    24  * * *
    25  * * *
    26  * * *
    27  * * *
    28  * * *
    29  * * *
    30  * * *
    Code:
    traceroute to cheetah.serverffs.com (174.34.155.106), 30 hops max, 40 byte packets
     1  64.120.12.17.novanetworks.net (64.120.12.17)  3.778 ms  3.902 ms  4.041 ms
     2  ip65-47-180-113.z180-47-65.customer.algx.net (65.47.180.113)  0.910 ms  0.911 ms  0.908 ms
     3  ge11-1-4d0.mcr2.chicago-il.us.xo.net (207.88.172.13)  1.021 ms  1.014 ms  1.017 ms
     4  ae1d0.mcr1.chicago-il.us.xo.net (216.156.1.81)  1.291 ms  1.277 ms  1.242 ms
     5  216.156.0.161.ptr.us.xo.net (216.156.0.161)  62.548 ms  62.530 ms  62.501 ms
     6  te-3-2-0.rar3.dallas-tx.us.xo.net (207.88.12.14)  62.415 ms  62.214 ms  62.200 ms
     7  vb12.rar3.la-ca.us.xo.net (207.88.12.46)  62.248 ms  62.392 ms  62.368 ms
     8  ae0d0.mcr1.la-ca.us.xo.net (216.156.0.114)  62.084 ms  61.834 ms  61.821 ms
     9  ae1d0.mcr1.santaana-ca.us.xo.net (216.156.1.58)  61.779 ms  61.762 ms  61.775 ms
    10  * * *
    11  * * *
    12  * * *
    13  * * *
    14  * * *
    15  * * *
    16  * * *
    17  * * *
    18  * * *
    19  * * *
    20  * * *
    21  * * *
    22  * * *
    23  * * *
    24  * * *
    25  * * *
    26  * * *
    27  * * *
    28  * * *
    29  * * *
    30  * * *
    - Dedicated servers with instant setup - http://www.instantdedi.com
    - Gameservers, Webhosting, Domains, IRC Bouncers, Dedicated Servers and more with instant setup - https://www.serverffs.com

    All covered by our phone support, low pricing and unique custom control panel.

  2. #2
    Are you sure this issue isn't cause by OVH's terrible network?

    Code:
    traceroute to frog.serverffs.com (94.23.26.143), 30 hops max, 40 byte packets
     1  [...]
     2  te6-8.dsr02.dllstx2.theplanet.com (70.87.254.253)  0.416 ms  0.458 ms  0.269 ms
     3  te9-4.dsr02.dllstx3.theplanet.com (70.87.253.125)  1.244 ms 85.fd.5746.static.theplanet.com (70.87.253.133)  1.138 ms te7-4.dsr02.dllstx3.theplanet.com (70.87.253.121)  1.190 ms
     4  et3-2.ibr03.dllstx3.theplanet.com (70.87.253.17)  0.601 ms  0.527 ms  0.429 ms
     5  xe-2-4.r01.dllstx09.us.bb.gin.ntt.net (157.238.225.5)  11.694 ms  11.624 ms  11.729 ms
     6  xe-1-2.r02.dllstx09.us.bb.gin.ntt.net (129.250.4.173)  0.737 ms  0.621 ms  0.652 ms
     7  po-1.r03.dllstx09.us.bb.gin.ntt.net (129.250.2.94)  0.837 ms  0.754 ms  0.878 ms
     8  xe-0.tata-communications.dllstx09.us.bb.gin.ntt.net (129.250.9.14)  5.999 ms * *
     9  if-6-0-0-1697.core2.DTX-Dallas.as6453.net (66.198.2.1)  0.740 ms  0.726 ms if-5-0-0-31.core2.DTX-Dallas.as6453.net (66.198.2.37)  1.074 ms
    10  if-2-0-705.core1.DTX-Dallas.as6453.net (66.198.2.50)  1.485 ms  1.616 ms  1.491 ms
    11  if-0-0-0-931.core3.AEQ-Ashburn.as6453.net (216.6.53.78)  36.460 ms  37.040 ms  36.949 ms
    12  if-15-0.core1.PYE-Paris.as6453.net (216.6.51.54)  119.851 ms  119.619 ms  119.513 ms
    13  if-11-4.har1.PV0-Paris.as6453.net (195.219.224.77)  121.727 ms  121.693 ms  121.460 ms
    14  * * *
    15  40g.vss-1-6k.routers.chtix.eu (91.121.131.29)  142.122 ms * *
    16  frog.serverffs.com (94.23.26.143)  115.028 ms  114.947 ms  115.035 ms
    
    
    traceroute to cheetah.serverffs.com (174.34.155.106), 30 hops max, 40 byte packets
     1  [...]
     2  te6-8.dsr02.dllstx2.theplanet.com (70.87.254.253)  0.564 ms  0.495 ms  0.406 ms
     3  te9-4.dsr02.dllstx3.theplanet.com (70.87.253.125)  0.639 ms te7-4.dsr02.dllstx3.theplanet.com (70.87.253.121)  0.844 ms 85.fd.5746.static.theplanet.com (70.87.253.133)  1.004 ms
     4  et3-1.ibr03.dllstx3.theplanet.com (70.87.253.21)  0.923 ms  0.774 ms  0.447 ms
     5  209.66.99.89.available.above.net (209.66.99.89)  0.575 ms  0.795 ms  0.722 ms
     6  xe-2-1-0.er1.ord2.us.above.net (64.125.30.62)  28.456 ms  28.356 ms  28.496 ms
     7  xe-1-1-0.er1.ord7.above.net (64.125.26.250)  28.623 ms  28.535 ms  28.458 ms
     8  xe1-1.cr01.ord01.mzima.net (206.223.119.62)  28.552 ms  28.483 ms  28.376 ms
     9  te0-0.cr01.dfw01.us.mzima.net (69.174.120.14)  30.917 ms te0-0.cr02.sjc02.us.mzima.net (69.174.120.9)  66.204 ms  66.139 ms
    10  te1-1.cr01.phx01.us.mzima.net (69.174.120.37)  59.581 ms te0-1.cr01.lax02.us.mzima.net (69.174.120.85)  62.210 ms te1-1.cr01.phx01.us.mzima.net (69.174.120.37)  59.826 ms
    11  te1-1.cr01.lax02.us.mzima.net (69.174.120.33)  60.376 ms  69.342 ms  69.256 ms
    12  edge1.lax.ubiquityservers.com (216.193.192.22)  59.924 ms  60.007 ms cheetah.serverffs.com (174.34.155.106)  62.104 ms
    478east
    High Bandwidth Servers
    Custom Hosting Solutions

  3. #3
    No, I'm having the problems with 4 separate networks and datacenters (Germany, France, The Netherlands and the United Kingdom).
    'cheetah.serverffs.com' is the server in Los Angeles and '217.18.70.7' is a server in The Netherlands, both have no connections with OVH whatsoever.

    Further more, it isn't a permanent problem (it indeed works right now). It happens for about 5 to 10 minutes a few times per day.
    - Dedicated servers with instant setup - http://www.instantdedi.com
    - Gameservers, Webhosting, Domains, IRC Bouncers, Dedicated Servers and more with instant setup - https://www.serverffs.com

    All covered by our phone support, low pricing and unique custom control panel.

  4. #4
    Join Date
    Dec 2007
    Location
    Isle of Man
    Posts
    3,068
    Funnily enough I was doing some network testing from here in MANCHESTER (UK) to Ubiquity last night. To my server in New York with them I got 101ms average (which is good) and in comparison I got about 100-102ms to InterServer.

    I was doing these tests (per Dougy's request ) and I did to his Ubiquity box in Chicago and I got 141ms - which I think it normal.. ish.

    No problems from here in Europe to Ubiquity.

  5. #5
    Join Date
    Jun 2004
    Location
    Europe
    Posts
    3,822
    Same, no problem from our locations to Ubiquity.
    Swiftway.net Your Business deserves our Quality - Experts on Hand since 2005. Europe & US locations, we operate our own network AS35017 Support response time <15 minutes 24/7
    Introducing our new Entry level server line ! Support response time <15 minutes 24/7. Technology Fast 50 & Fast 500 award winning for multiple years, Your Business deserves Swiftway Quality.

  6. #6
    Join Date
    Mar 2009
    Posts
    358
    Doesn't seem to be any issue for me. Ubiquity Chicago:
    Code:
    traceroute to 217.18.70.7 (217.18.70.7), 30 hops max, 60 byte packets
     1  ungracious.info (64.120.13.33)  0.000 ms  0.000 ms  0.000 ms
     2  g0-6.cr01.ord01.mzima.net (72.37.148.177)  8.000 ms  8.000 ms  8.000 ms
     3  te4-5.cr01.lga01.us.mzima.net (69.174.120.73)  28.000 ms  28.000 ms  28.000 ms
     4  gi3-0.nyc-002-inter-1.interoute.net (198.32.160.102)  24.000 ms  24.000 ms *
     5  Gi7-0.nyc-002-access-1.interoute.net (212.23.43.137)  100.000 ms *  100.000 ms
     6  PO6-0.lon-001-access-1.interoute.net (212.23.43.150)  100.000 ms  100.000 ms  100.000 ms
     7  xe-1-3-0-0.lon-004-score-1-re1.interoute.net (84.233.218.182)  100.000 ms  100.000 ms  100.000 ms
     8  dc-server-2.adam.psi.com (195.81.245.2)  100.000 ms  96.000 ms  96.000 ms
     9  PO9-0.rtm-vla-access-1.interoute.net (212.23.41.201)  96.000 ms  100.000 ms  100.000 ms
    10  217.118.121.134 (217.118.121.134)  100.000 ms  100.000 ms  100.000 ms
    11  csw-0.cpl-mkb.grafix.nl (217.67.247.27)  104.000 ms csw-1.cpl-mkb.grafix.nl (217.67.247.26)  104.000 ms csw-0.cpl-mkb.grafix.nl (217.67.247.27)  104.000 ms
    12  emu.serverffs.com (217.18.70.7)  104.000 ms  104.000 ms  104.000 ms
    
    traceroute to frog.serverffs.com (94.23.26.143), 30 hops max, 60 byte packets
     1  ungracious.info (64.120.13.33)  12.000 ms  12.000 ms  12.000 ms
     2  ip65-47-180-113.z180-47-65.customer.algx.net (65.47.180.113)  4.000 ms  4.000 ms  4.000 ms
     3  ge11-1-4d0.mcr2.chicago-il.us.xo.net (207.88.172.13)  4.000 ms  4.000 ms  4.000 ms
     4  ae1d0.mcr1.chicago-il.us.xo.net (216.156.1.81)  4.000 ms  0.000 ms  0.000 ms
     5  216.156.0.161.ptr.us.xo.net (216.156.0.161)  0.000 ms  0.000 ms  0.000 ms
     6  207.88.13.5.ptr.us.xo.net (207.88.13.5)  0.000 ms  0.000 ms  0.000 ms
     7  206.111.2.138.ptr.us.xo.net (206.111.2.138)  0.000 ms  0.000 ms  0.000 ms
     8  30g.ldn-1-6k.routers.ovh.net (94.23.122.125)  96.000 ms * *
     9  20g.vss-1-6k.routers.chtix.eu (94.23.122.66)  100.000 ms * *
    10  frog.serverffs.com (94.23.26.143)  100.000 ms  100.000 ms  100.000 ms
    
    traceroute to cheetah.serverffs.com (174.34.155.106), 30 hops max, 60 byte packets
     1  ungracious.info (64.120.13.33)  8.000 ms  8.000 ms  8.000 ms
     2  ip65-47-180-113.z180-47-65.customer.algx.net (65.47.180.113)  4.000 ms  4.000 ms  4.000 ms
     3  ge11-1-3d0.mcr2.chicago-il.us.xo.net (207.88.172.9)  4.000 ms  4.000 ms  4.000 ms
     4  ae1d0.mcr1.chicago-il.us.xo.net (216.156.1.81)  4.000 ms  4.000 ms  4.000 ms
     5  216.156.0.161.ptr.us.xo.net (216.156.0.161)  60.000 ms  60.000 ms  60.000 ms
     6  te-3-2-0.rar3.dallas-tx.us.xo.net (207.88.12.14)  64.000 ms  60.000 ms  60.000 ms
     7  vb12.rar3.la-ca.us.xo.net (207.88.12.46)  60.000 ms  60.000 ms  60.000 ms
     8  ae0d0.mcr1.la-ca.us.xo.net (216.156.0.114)  60.000 ms  60.000 ms  60.000 ms
     9  216.156.11.66.ptr.us.xo.net (216.156.11.66)  60.000 ms  60.000 ms  60.000 ms
    10  ip65-46-14-106.z14-46-65.customer.algx.net (65.46.14.106)  68.000 ms  64.000 ms  64.000 ms
    11  cheetah.serverffs.com (174.34.155.106)  64.000 ms  64.000 ms  64.000 ms

  7. #7
    Like I said, it only happens a few times per day for only a few minutes.
    It works fine for me as well, you will only notice this problem if you run something constant (such as monitoring).
    - Dedicated servers with instant setup - http://www.instantdedi.com
    - Gameservers, Webhosting, Domains, IRC Bouncers, Dedicated Servers and more with instant setup - https://www.serverffs.com

    All covered by our phone support, low pricing and unique custom control panel.

  8. #8
    Join Date
    Jul 2007
    Location
    Pennsylvania, USA
    Posts
    686
    Quote Originally Posted by serverFFS View Post
    Like I said, it only happens a few times per day for only a few minutes.
    It works fine for me as well, you will only notice this problem if you run something constant (such as monitoring).
    Seems like some type of firewall or IPtables blocking consistent connections like a 2-3 minute monitor that pings and/or tests SSH connection.

  9. #9
    This has never been a problem in the months before this, nothing has changed and there is no such firewall running.
    Don't the traceroutes clearly show there is something wrong far before it reaches the server?
    - Dedicated servers with instant setup - http://www.instantdedi.com
    - Gameservers, Webhosting, Domains, IRC Bouncers, Dedicated Servers and more with instant setup - https://www.serverffs.com

    All covered by our phone support, low pricing and unique custom control panel.

  10. #10
    Join Date
    Dec 2004
    Location
    Chicago
    Posts
    1,000
    serverFFS, I'd like to help you with this. I have to say that at this point, we probably have hundreds if not thousands of users that monitor their websites and servers from all over the map, including all sorts of monitoring that we do ourselves. We have not been aware of any recent widespread problems. Like you, we also do all of the monitoring for our NOC from Chicago, which has shown no widespread issues.

    I can certainly see how seeing such a trace would be frustrating, however, whatever the real problem might lie. If you could provide me with a ticket ID I'd like to personally assist you in private in troubleshooting further.
    Corey Northcutt | Electric Goat Media
    Currently building this nifty small business ROI calculator.

  11. #11
    Join Date
    Oct 2002
    Location
    Vancouver, B.C.
    Posts
    2,699
    Quote Originally Posted by serverFFS View Post
    Since 2 weeks of so, we're having horrible connections between Europe and our servers in the United States (Ubiqiuty).
    Our monitoring server is located in Chicago and is constantly sending false alerts that servers are offline.
    Even connectivity between their own POPs (Chicago to Los Angeles) fails frequently.
    Ticket has been open since the 2nd of March, and each time they are putting the blame on one of their carriers.

    Is anyone having the same kind of issues with them?

    Here some traceroutes:
    Chances are rather than 3 different carriers having the same problem, the problem's probably either with a common carrier on the path back and/or dampening on your prefix.

    Can you provide traceroutes in the opposite direction when these problems are happening?
    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

  12. #12
    It seems to be rock solid again right now (as usual), so I can't provide a meaningful traceroute.
    As soon as something goes bad again I'll get a new traceroute from both sides to have a look.
    - Dedicated servers with instant setup - http://www.instantdedi.com
    - Gameservers, Webhosting, Domains, IRC Bouncers, Dedicated Servers and more with instant setup - https://www.serverffs.com

    All covered by our phone support, low pricing and unique custom control panel.

  13. #13
    Join Date
    Dec 2009
    Posts
    64
    Perhaps you should contact Ubiquity directly next time rather than making a topic on WHT? It seems their staff is more than willing to help with issues such as this.

  14. #14
    Perhaps you should read the actual topic before replying?
    Ticket has been open since the 2nd of March, and each time they are putting the blame on one of their carriers.
    I was just posting here to find out whether there were more people having the problems and whether people had any idea what could be causing this.
    - Dedicated servers with instant setup - http://www.instantdedi.com
    - Gameservers, Webhosting, Domains, IRC Bouncers, Dedicated Servers and more with instant setup - https://www.serverffs.com

    All covered by our phone support, low pricing and unique custom control panel.

  15. #15
    Join Date
    Dec 2009
    Posts
    64
    I did read, but I also read:

    serverFFS, I'd like to help you with this. I have to say that at this point, we probably have hundreds if not thousands of users that monitor their websites and servers from all over the map, including all sorts of monitoring that we do ourselves. We have not been aware of any recent widespread problems. Like you, we also do all of the monitoring for our NOC from Chicago, which has shown no widespread issues.

    I can certainly see how seeing such a trace would be frustrating, however, whatever the real problem might lie. If you could provide me with a ticket ID I'd like to personally assist you in private in troubleshooting further.
    I just see a topic like this as something that could possibly detour potential new customers of Ubiquity. Not trying to be mean or anything, just looking out for a good company.

  16. #16
    I'm definitely not trying to scare away people from Ubiquity, that's why I posted this later on:
    It seems to be rock solid again right now (as usual)
    Ubiquity is a great provider and their network has been rock solid for months.
    I just needed a second opinion on this issue.
    - Dedicated servers with instant setup - http://www.instantdedi.com
    - Gameservers, Webhosting, Domains, IRC Bouncers, Dedicated Servers and more with instant setup - https://www.serverffs.com

    All covered by our phone support, low pricing and unique custom control panel.

  17. #17
    Join Date
    Dec 2009
    Posts
    64
    Quote Originally Posted by serverFFS View Post
    I'm definitely not trying to scare away people from Ubiquity, that's why I posted this later on:


    Ubiquity is a great provider and their network has been rock solid for months.
    I just needed a second opinion on this issue.

    I agree fully, sorry if I came off a little rude.

  18. #18
    Glad we reached an agreement, I'll post back here in a few weeks with the resolution of this issue
    - Dedicated servers with instant setup - http://www.instantdedi.com
    - Gameservers, Webhosting, Domains, IRC Bouncers, Dedicated Servers and more with instant setup - https://www.serverffs.com

    All covered by our phone support, low pricing and unique custom control panel.

  19. #19
    Join Date
    Mar 2007
    Posts
    61
    Rock solid network no questions about that. I have the same problem with two servers in the same data center.

    traceroute to ubiquityservers.com (69.147.227.178), 30 hops max, 40 byte packets
    1 ungracious.info (64.120.13.33) 1.356 ms 1.312 ms 1.292 ms
    2 * * *
    3 * * *
    4 * * *
    5 * * *
    6 * * *
    7 * * *
    8 * * *
    9 * * *
    10 * * *
    11 * * *
    12 * * *
    13 * * *
    14 * * *
    15 * * *
    16 * * *
    17 * * *
    18 * * *
    19 * * *
    20 * * *
    21 * * *
    22 * * *
    23 * * *
    24 * * *
    25 * * *
    26 * * *
    27 * * *
    28 * * *
    29 * * *
    30 * * *
    [root@server1 ~]#


    traceroute -I ubiquityservers.com
    traceroute to ubiquityservers.com (69.147.227.178), 30 hops max, 40 byte packets
    1 ungracious.info (64.120.13.33) 12.045 ms 12.031 ms 12.029 ms
    2 ubiquityservers.com (69.147.227.178) 12.010 ms 12.011 ms 12.009 ms
    [root@server1 ~]#

    Do you have your firewall on? even with the firewall down i get the same resoults.

  20. #20
    Join Date
    Dec 2009
    Posts
    64
    That's a strange traceroute, but -I uses ICMP pings and it seems it replied just fine. So what's the problem with that?

  21. #21
    Join Date
    Mar 2007
    Posts
    61
    There is no problem with ping, just the "That's a strange traceroute" part.

  22. #22
    Join Date
    Dec 2009
    Posts
    64
    I get strange traceroutes like that sometimes, I'm actually not 100% sure what the default kind of packet traceroute sends out, but I think it's perfectly fine to ignore. It's only one hop away and such and in the end it actually gets there.

    Here is an example:

    [brandon@v.exhort.ca:~] traceroute amor.exhort.es
    traceroute to amor.exhort.es (82.98.148.112), 30 hops max, 40 byte packets
    1 67.212.67.221 (67.212.67.221) 0.912 ms 1.078 ms 1.064 ms
    2 64.15.64.62 (64.15.64.62) 0.583 ms 0.702 ms 0.699 ms
    3 ge-6-13.car2.Montreal2.Level3.net (4.59.178.5) 0.558 ms 0.674 ms 0.782 ms
    4 ae-11-11.car1.Montreal2.Level3.net (4.69.141.2) 0.755 ms 0.754 ms 0.763 ms
    5 ae-5-5.ebr4.NewYork1.Level3.net (4.69.141.6) 13.880 ms 13.853 ms 13.847 ms
    6 ae-74-74.csw2.NewYork1.Level3.net (4.69.134.118) 9.909 ms ae-94-94.csw4.NewYork1.Level3.net (4.69.134.126) 8.468 ms ae-64-64.csw1.NewYork1.Level3.net (4.69.134.114) 13.886 ms
    7 ae-71-71.ebr1.NewYork1.Level3.net (4.69.134.69) 8.715 ms ae-81-81.ebr1.NewYork1.Level3.net (4.69.134.73) 8.841 ms ae-91-91.ebr1.NewYork1.Level3.net (4.69.134.77) 8.683 ms
    8 ae-43-43.ebr2.London1.Level3.net (4.69.137.73) 77.360 ms ae-44-44.ebr2.London1.Level3.net (4.69.137.77) 77.165 ms ae-41-41.ebr2.London1.Level3.net (4.69.137.65) 77.340 ms
    9 ae-21-52.car1.London1.Level3.net (4.69.139.98) 78.955 ms 131.651 ms 131.641 ms
    10 212.113.16.110 (212.113.16.110) 77.171 ms 77.231 ms 77.360 ms
    11 ae0-0.lon-004-score-1-re1.interoute.net (84.233.218.158) 100.098 ms 100.485 ms 100.466 ms
    12 ae1-0.par-gar-score-1-re1.interoute.net (212.23.42.21) 83.599 ms 83.844 ms 83.835 ms
    13 ae1-0.mad-001-score-1-re0.interoute.net (89.202.161.21) 100.432 ms 100.409 ms 100.208 ms
    14 195.81.198.90 (195.81.198.90) 111.559 ms 111.541 ms 111.317 ms
    15 * * *
    16 * * *
    17 * * *
    18 * * *
    19 * * *
    20 * * *
    21 * * *
    22 * * *
    23 * * *
    24 * * *
    25 * * *
    26 * * *
    27 * * *
    28 * * *
    29 * * *
    30 * * *
    [brandon@v.exhort.ca:~] ping amor.exhort.es
    PING amor.exhort.es (82.98.148.112) 56(84) bytes of data.
    64 bytes from amor.exhort.es (82.98.148.112): icmp_seq=1 ttl=53 time=111 ms
    64 bytes from amor.exhort.es (82.98.148.112): icmp_seq=2 ttl=53 time=110 ms
    64 bytes from amor.exhort.es (82.98.148.112): icmp_seq=3 ttl=53 time=111 ms
    64 bytes from amor.exhort.es (82.98.148.112): icmp_seq=4 ttl=53 time=111 ms

    As you can see the traceroute was messed up, but the traffic reaches its destination perfectly fine.

  23. #23
    Join Date
    Mar 2007
    Posts
    61
    Well the network is solid so I'm not worry about the routes, i newer got a clean route from my servers in the last 2-3 weeks, not even from server to server however ping is fine.

    traceroute to exhort.es (82.98.145.14), 30 hops max, 40 byte packets
    1 ungracious.info (64.120.13.33) 0.695 ms 0.668 ms 1.603 ms
    2 ip65-47-180-113.z180-47-65.customer.algx.net (65.47.180.113) 1.598 ms 1.587 ms *
    3 * * *
    4 * * *
    5 * * *
    6 * * *
    7 gi2-32.mpd01.ord03.atlas.cogentco.com (154.54.12.229) 1.748 ms 1.936 ms 1.916 ms
    8 te3-4.ccr01.ord01.atlas.cogentco.com (154.54.25.65) 1.897 ms * *
    9 * te0-2-0-3.ccr21.jfk02.atlas.cogentco.com (154.54.29.154) 27.731 ms 27.695 ms
    10 te3-2.ccr02.par04.atlas.cogentco.com (154.54.1.94) 113.965 ms te7-2.ccr01.par01.atlas.cogentco.com (154.54.30.90) 107.902 ms 107.870 ms
    11 * te0-0-0-7.ccr22.par01.atlas.cogentco.com (130.117.49.53) 111.790 ms te4-7.mpd03.par01.atlas.cogentco.com (130.117.50.149) 114.773 ms
    12 * * *
    13 * * *
    14 * * *
    15 * dinahosting.demarc.cogentco.com (149.6.150.70) 141.823 ms *
    16 vls13.dinaserver.com (82.98.145.14) 135.882 ms 138.617 ms 136.560 ms
    [root@server1 ~]#


    traceroute to exhort.es (82.98.145.14), 30 hops max, 40 byte packets
    1 64.120.12.17.novanetworks.net (64.120.12.17) 0.389 ms 0.466 ms 0.547 ms
    2 ip65-47-180-113.z180-47-65.customer.algx.net (65.47.180.113) 1.010 ms 1.000 ms *
    3 * * *
    4 ae1d0.mcr1.chicago-il.us.xo.net (216.156.1.81) 1.371 ms * *
    5 * * *
    6 * * *
    7 * * *
    8 * vl3489.mpd01.ord01.atlas.cogentco.com (154.54.5.17) 1.659 ms te1-1.mpd01.ord01.atlas.cogentco.com (154.54.2.93) 1.554 ms
    9 te0-2-0-3.ccr21.jfk02.atlas.cogentco.com (154.54.29.154) 27.206 ms te0-1-0-2.ccr21.jfk02.atlas.cogentco.com (154.54.29.150) 27.030 ms te0-2-0-3.mpd21.jfk02.atlas.cogentco.com (154.54.29.162) 27.066 ms
    10 * te3-7.ccr02.lhr01.atlas.cogentco.com (130.117.51.158) 105.844 ms 105.822 ms
    11 * * te0-0-0-7.ccr22.par01.atlas.cogentco.com (130.117.49.53) 110.836 ms
    12 * * *
    13 * * *
    14 * dinahosting.demarc.cogentco.com (149.6.150.70) 137.666 ms *
    15 vls13.dinaserver.com (82.98.145.14) 137.734 ms 137.647 ms 137.902 ms
    [root@server2 ~]#

Similar Threads

  1. Ubiquity Servers Review - Excellent Service, Great Network!
    By mdfederici in forum Colocation, Data Centers, IP Space and Networks
    Replies: 7
    Last Post: 05-15-2009, 11:00 AM
  2. Replies: 0
    Last Post: 05-05-2009, 06:00 PM
  3. Replies: 0
    Last Post: 04-27-2009, 04:45 PM
  4. Replies: 0
    Last Post: 04-20-2009, 04:33 PM
  5. Replies: 2
    Last Post: 04-14-2009, 02:29 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
  •