Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Crissic VPS Having Packet Loss - Page 2
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Crissic VPS Having Packet Loss

2»

Comments

  • @SkylarM said:
    Atrato we have a solution in-progress. Tinet I am not sure of as I do not have direct contact with them as they are part of the DC blend we pick up. Can you do a traceroute from the VPS to your Ramnode VPS? Return path would be useful as well.

    Here you go:

    traceroute to (23.226.229.***), 30 hops max, 60 byte packets
     1  107.150.0.9 (107.150.0.9)  0.050 ms  0.023 ms  0.021 ms
     2  65.85.92.23.static.reverse.as62639.com (23.92.85.65)  0.470 ms  0.485 ms  0.482 ms
     3  ae5-165.atl11.ip4.tinet.net (77.67.79.245)  6.190 ms  6.186 ms  6.163 ms
     4  xe-11-1-2.sea23.ip4.tinet.net (141.136.111.205)  100.051 ms  100.034 ms  100.009 ms
     5   (23.226.229.***)  91.925 ms  91.812 ms  91.818 ms
    
  • namhuynamhuy Member

    any update with pccw it's been a while

      1    <1 ms    <1 ms    <1 ms  192.168.1.1
      2    34 ms    34 ms    34 ms  L100.LSANCA-DSL-59.verizon-gni.net [98.119.43.1]
    
      3    37 ms    39 ms    39 ms  G0-10-0-5.LSANCA-LCR-22.verizon-gni.net [130.81.
    46.226]
      4    39 ms    38 ms    39 ms  ae2-0.LAX01-BB-RTR2.verizon-gni.net [130.81.22.2
    38]
      5    37 ms    37 ms    36 ms  0.xe-8-1-0.BR3.LAX15.ALTER.NET [152.63.115.69]
      6    42 ms    50 ms    39 ms  204.255.168.126
      7    94 ms    93 ms    94 ms  giglinx.te4-4-21.br01.atl02.pccwbtn.net [63.218.
    69.62]
      8    94 ms    99 ms    94 ms  199.48.166.250
      9    99 ms    95 ms    94 ms  107.150.0.15
    
  • SkylarMSkylarM Member

    @namhuy said:
    any update with pccw it's been a while

    As mentioned, we forwarded the information up. Still no response.

  • xDutchyxDutchy Member

    Im seeing a different route at this moment then yesterday, without any packet loss, so it seems to be going fine as of now :)

  • @xDutchy said:
    Im seeing a different route at this moment then yesterday, without any packet loss, so it seems to be going fine as of now :)

    Just saw this in my monitor log:

    2014-05-26 12:10:09 0% Packet Loss  91.62ms Response Time
    2014-05-26 12:05:10 0% Packet Loss  104.78ms Response Time
    2014-05-26 12:00:11 20% Packet Loss 120.38ms Response Time
    2014-05-26 11:55:09 0% Packet Loss  97.79ms Response Time
    2014-05-26 11:50:10 0% Packet Loss  78.87ms Response Time
    2014-05-26 11:45:09 0% Packet Loss  138.47ms Response Time
    2014-05-26 11:40:09 0% Packet Loss  88.31ms Response Time
    2014-05-26 11:35:09 0% Packet Loss  99.24ms Response Time
    2014-05-26 11:30:10 0% Packet Loss  80.88ms Response Time
    2014-05-26 11:25:09 0% Packet Loss  123.49ms Response Time
    
  • xDutchyxDutchy Member

    Idk what time zone that is, but 11:45 matches the time I posted my comment, saying 0%! :D

Sign In or Register to comment.