Howdy, Stranger!

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


Miami - Newark OVH Route - high packet loss
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.

Miami - Newark OVH Route - high packet loss

Hello people,
Does anyone else is experiencing packet loss between Miami and Newark?
In the last few days my traceroute between South America and OVH Canada (BHS) are intermittently suffering packet loss (over 50% packet loss sometimes).

Packets flowing between these 2 points are the most problematic right now:
po97-151.mia-5-6k.fl.us
be100-1034.nwk-1-a9.nj.us

Thanks for any light on this subject.

Comments

  • MunMun Member

    Do you see packet loss at the end destination or just partially along the route ?

  • MikeAMikeA Member, Patron Provider
    edited May 2016

    @Mun said:
    Do you see packet loss at the end destination or just partially along the route ?

    95% chance it's not end point, but I assume that's why you brought it up anyways :-)

  • EricBEricB Member
    edited May 2016

    Usually expected with OVH and their totally not saturated network :)

    Possible it's just ratelimiting along the line.

  • ccaritaccarita Member

    Yes, the packet loss reaches the destination.

    Here are the MTR statistics:

    |---------------------------------------------------------------------------------------|
    | WinMTR statistics |
    | Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
    |---------------------------------------------|------|------|------|------|------|------|
    | 192.168.1.1 - 0 | 101 | 101 | 0 | 0 | 2 | 0 |
    | 187-100-36-225.dsl.telesp.net.br - 0 | 101 | 101 | 1 | 2 | 29 | 1 |
    | 200-148-89-89.dsl.telesp.net.br - 0 | 101 | 101 | 1 | 5 | 70 | 2 |
    | 187-100-83-0.dsl.telesp.net.br - 0 | 101 | 101 | 6 | 7 | 16 | 7 |
    |grtsanem4-et-2-1-0-101-telesp.net.tel - 0 | 101 | 101 | 7 | 9 | 26 | 8 |
    |hu-0-10-0-0-grtmiabr6.priv.net.telefo - 0 | 101 | 101 | 117 | 118 | 121 | 118 |
    |et-19-1-0-0-4-grtmiabr2.net.telefonic - 0 | 101 | 101 | 116 | 117 | 121 | 117 |
    |et-2-0-0-5-grtmiana2.net.telefonicagl - 0 | 101 | 101 | 126 | 130 | 148 | 126 |
    | po97-151.mia-5-6k.fl.us - 17 | 61 | 51 | 130 | 138 | 180 | 132 |
    | be100-1017.nwk-5-a9.nj.us - 14 | 66 | 57 | 0 | 210 | 216 | 208 |
    | be10-1018.bhs-g2-a9.qc.ca - 14 | 66 | 57 | 211 | 223 | 228 | 228 |
    | po7.bhs-3b-6k.qc.ca - 0 | 101 | 101 | 163 | 176 | 318 | 167 |
    | xxx.yyyy.zzz - 8 | 79 | 73 | 205 | 218 | 223 | 219 |
    |_____________________________________________|______|______|______|______|______|______|

  • shellshell Member

    maybe this ?

    http://status.ovh.com/?do=details&id=13257
    
  • ccaritaccarita Member

    Unfortunately it is not. That day the route was diverted to Europe from Miami and then crossed the Atlantic again to Newark then to BHS.

Sign In or Register to comment.