Howdy, Stranger!

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

Sign In Register

Quick Links


Categories

In this Discussion

› › Massive packet loss at BlueVM Los Angeles
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.

Massive packet loss at BlueVM Los Angeles

eiYeK8dozai6KahyBeiYeK8dozai6KahyB Member
in Providers

Lots of packet loss on one of my BlueVM nodes out of LA. This has been going on for two weeks now, since at least the 12th, all day long.

DNS lookups are failing and I've been getting lots of errors from my node because of it.

This is all from today:

user@host: traceroute google.com
traceroute to google.com (74.125.224.128), 30 hops max, 60 byte packets
 1  192.210.208.158 (192.210.208.158)  0.033 ms  0.012 ms  0.010 ms
 2  10ge-1.8.3.14.0.la1.colocrossing.com (192.210.148.253)  20.063 ms  20.042 ms 10ge-2.8.3.14.0.la1.colocrossing.com (23.94.11.113)  0.648 ms
 3  xe-5-2-0.er1.lax112.us.above.net (208.185.252.21)  0.270 ms 69.31.114.169 (69.31.114.169)  0.325 ms  0.305 ms
 ...

user@host: while true ; do ping -q -c 10 192.210.148.253 | egrep loss ; sleep 1 ; done
10 packets transmitted, 9 received, 10% packet loss, time 9019ms
10 packets transmitted, 10 received, 0% packet loss, time 9018ms
10 packets transmitted, 6 received, 40% packet loss, time 9034ms
10 packets transmitted, 5 received, 50% packet loss, time 9005ms
10 packets transmitted, 2 received, 80% packet loss, time 9023ms
10 packets transmitted, 10 received, 0% packet loss, time 9056ms
10 packets transmitted, 9 received, 10% packet loss, time 9032ms
10 packets transmitted, 1 received, 90% packet loss, time 9018ms
10 packets transmitted, 2 received, 80% packet loss, time 9016ms
10 packets transmitted, 6 received, 40% packet loss, time 9039ms
10 packets transmitted, 10 received, 0% packet loss, time 9068ms
10 packets transmitted, 5 received, 50% packet loss, time 9004ms
10 packets transmitted, 4 received, 60% packet loss, time 9019ms
10 packets transmitted, 5 received, 50% packet loss, time 9041ms
10 packets transmitted, 10 received, 0% packet loss, time 9011ms
10 packets transmitted, 10 received, 0% packet loss, time 9011ms
10 packets transmitted, 1 received, 90% packet loss, time 9023ms
10 packets transmitted, 2 received, 80% packet loss, time 9001ms
10 packets transmitted, 1 received, 90% packet loss, time 9011ms
10 packets transmitted, 10 received, 0% packet loss, time 9045ms
10 packets transmitted, 2 received, 80% packet loss, time 9004ms
10 packets transmitted, 1 received, 90% packet loss, time 9011ms
10 packets transmitted, 6 received, 40% packet loss, time 9044ms
10 packets transmitted, 10 received, 0% packet loss, time 9032ms
10 packets transmitted, 7 received, 30% packet loss, time 9065ms
10 packets transmitted, 3 received, 70% packet loss, time 9010ms
10 packets transmitted, 1 received, 90% packet loss, time 8999ms
10 packets transmitted, 10 received, 0% packet loss, time 9040ms
10 packets transmitted, 5 received, 50% packet loss, time 9001ms
10 packets transmitted, 2 received, 80% packet loss, time 9095ms
10 packets transmitted, 1 received, 90% packet loss, time 9040ms
10 packets transmitted, 8 received, 20% packet loss, time 9018ms
10 packets transmitted, 10 received, 0% packet loss, time 9035ms
10 packets transmitted, 4 received, 60% packet loss, time 9054ms
10 packets transmitted, 0 received, 100% packet loss, time 9002ms
10 packets transmitted, 10 received, 0% packet loss, time 9012ms
10 packets transmitted, 10 received, 0% packet loss, time 9006ms
10 packets transmitted, 4 received, 60% packet loss, time 9064ms
10 packets transmitted, 3 received, 70% packet loss, time 9040ms
10 packets transmitted, 2 received, 80% packet loss, time 9036ms
10 packets transmitted, 10 received, 0% packet loss, time 9012ms
10 packets transmitted, 8 received, 20% packet loss, time 9001ms
10 packets transmitted, 1 received, 90% packet loss, time 9012ms
10 packets transmitted, 0 received, 100% packet loss, time 9014ms
10 packets transmitted, 10 received, 0% packet loss, time 9016ms
10 packets transmitted, 7 received, 30% packet loss, time 9015ms
10 packets transmitted, 5 received, 50% packet loss, time 9006ms
10 packets transmitted, 6 received, 40% packet loss, time 9009ms
10 packets transmitted, 10 received, 0% packet loss, time 9027ms
10 packets transmitted, 10 received, 0% packet loss, time 9038ms
10 packets transmitted, 6 received, 40% packet loss, time 9017ms
10 packets transmitted, 5 received, 50% packet loss, time 9021ms
10 packets transmitted, 5 received, 50% packet loss, time 9016ms
10 packets transmitted, 9 received, 10% packet loss, time 9029ms
10 packets transmitted, 10 received, 0% packet loss, time 9021ms
10 packets transmitted, 4 received, 60% packet loss, time 9054ms
10 packets transmitted, 2 received, 80% packet loss, time 9031ms
10 packets transmitted, 4 received, 60% packet loss, time 9029ms
10 packets transmitted, 10 received, 0% packet loss, time 9019ms
10 packets transmitted, 10 received, 0% packet loss, time 9039ms
10 packets transmitted, 3 received, 70% packet loss, time 9066ms
10 packets transmitted, 2 received, 80% packet loss, time 9021ms
10 packets transmitted, 6 received, 40% packet loss, time 9059ms
10 packets transmitted, 10 received, 0% packet loss, time 9018ms
10 packets transmitted, 7 received, 30% packet loss, time 9023ms
10 packets transmitted, 4 received, 60% packet loss, time 9109ms
10 packets transmitted, 1 received, 90% packet loss, time 9030ms
10 packets transmitted, 9 received, 10% packet loss, time 9039ms
10 packets transmitted, 10 received, 0% packet loss, time 9057ms
10 packets transmitted, 2 received, 80% packet loss, time 9071ms
10 packets transmitted, 2 received, 80% packet loss, time 9012ms
10 packets transmitted, 8 received, 20% packet loss, time 9035ms
10 packets transmitted, 10 received, 0% packet loss, time 9027ms
10 packets transmitted, 10 received, 0% packet loss, time 9002ms
10 packets transmitted, 2 received, 80% packet loss, time 9031ms
10 packets transmitted, 2 received, 80% packet loss, time 9006ms
10 packets transmitted, 5 received, 50% packet loss, time 9019ms
10 packets transmitted, 10 received, 0% packet loss, time 9020ms
10 packets transmitted, 8 received, 20% packet loss, time 9045ms
10 packets transmitted, 2 received, 80% packet loss, time 9036ms
10 packets transmitted, 4 received, 60% packet loss, time 9031ms
10 packets transmitted, 6 received, 40% packet loss, time 9029ms
10 packets transmitted, 10 received, 0% packet loss, time 9012ms
10 packets transmitted, 6 received, 40% packet loss, time 9029ms
10 packets transmitted, 3 received, 70% packet loss, time 9055ms
10 packets transmitted, 1 received, 90% packet loss, time 9010ms
10 packets transmitted, 9 received, 10% packet loss, time 9012ms
10 packets transmitted, 10 received, 0% packet loss, time 9005ms
10 packets transmitted, 4 received, 60% packet loss, time 9022ms
10 packets transmitted, 8 received, 20% packet loss, time 9025ms
10 packets transmitted, 6 received, 40% packet loss, time 9036ms
10 packets transmitted, 10 received, 0% packet loss, time 9060ms
10 packets transmitted, 9 received, 10% packet loss, time 9053ms
10 packets transmitted, 2 received, 80% packet loss, time 9020ms
10 packets transmitted, 2 received, 80% packet loss, time 9046ms
10 packets transmitted, 7 received, 30% packet loss, time 9009ms
10 packets transmitted, 10 received, 0% packet loss, time 9007ms
10 packets transmitted, 3 received, 70% packet loss, time 9036ms
10 packets transmitted, 3 received, 70% packet loss, time 9011ms
10 packets transmitted, 4 received, 60% packet loss, time 9050ms
10 packets transmitted, 10 received, 0% packet loss, time 9031ms
10 packets transmitted, 10 received, 0% packet loss, time 9022ms
10 packets transmitted, 5 received, 50% packet loss, time 9057ms
10 packets transmitted, 3 received, 70% packet loss, time 9007ms
10 packets transmitted, 7 received, 30% packet loss, time 9079ms
10 packets transmitted, 10 received, 0% packet loss, time 9030ms
10 packets transmitted, 7 received, 30% packet loss, time 9004ms
10 packets transmitted, 3 received, 70% packet loss, time 9069ms
10 packets transmitted, 2 received, 80% packet loss, time 9040ms
10 packets transmitted, 8 received, 20% packet loss, time 9018ms
10 packets transmitted, 10 received, 0% packet loss, time 9045ms
10 packets transmitted, 6 received, 40% packet loss, time 9017ms
10 packets transmitted, 1 received, 90% packet loss, time 9019ms
10 packets transmitted, 0 received, 100% packet loss, time 9000ms
10 packets transmitted, 10 received, 0% packet loss, time 9060ms
10 packets transmitted, 10 received, 0% packet loss, time 9076ms
10 packets transmitted, 2 received, 80% packet loss, time 9039ms
10 packets transmitted, 2 received, 80% packet loss, time 9051ms
10 packets transmitted, 6 received, 40% packet loss, time 9068ms
10 packets transmitted, 10 received, 0% packet loss, time 9069ms
10 packets transmitted, 7 received, 30% packet loss, time 9083ms
10 packets transmitted, 4 received, 60% packet loss, time 9030ms
10 packets transmitted, 1 received, 90% packet loss, time 9002ms
10 packets transmitted, 7 received, 30% packet loss, time 9061ms
10 packets transmitted, 10 received, 0% packet loss, time 9044ms
10 packets transmitted, 3 received, 70% packet loss, time 9008ms
10 packets transmitted, 7 received, 30% packet loss, time 9065ms
10 packets transmitted, 3 received, 70% packet loss, time 9001ms
10 packets transmitted, 10 received, 0% packet loss, time 9018ms
10 packets transmitted, 10 received, 0% packet loss, time 9012ms
10 packets transmitted, 2 received, 80% packet loss, time 9012ms
10 packets transmitted, 2 received, 80% packet loss, time 9063ms
10 packets transmitted, 3 received, 70% packet loss, time 9006ms
10 packets transmitted, 10 received, 0% packet loss, time 9032ms
10 packets transmitted, 8 received, 20% packet loss, time 9053ms
10 packets transmitted, 1 received, 90% packet loss, time 9001ms
10 packets transmitted, 0 received, 100% packet loss, time 9086ms
10 packets transmitted, 10 received, 0% packet loss, time 9028ms
10 packets transmitted, 5 received, 50% packet loss, time 9002ms
10 packets transmitted, 0 received, 100% packet loss, time 9000ms
10 packets transmitted, 6 received, 40% packet loss, time 9029ms
10 packets transmitted, 10 received, 0% packet loss, time 9002ms
10 packets transmitted, 4 received, 60% packet loss, time 9007ms
10 packets transmitted, 0 received, 100% packet loss, time 9057ms
10 packets transmitted, 8 received, 20% packet loss, time 9022ms
10 packets transmitted, 10 received, 0% packet loss, time 9023ms
10 packets transmitted, 10 received, 0% packet loss, time 9006ms
10 packets transmitted, 10 received, 0% packet loss, time 9014ms
10 packets transmitted, 10 received, 0% packet loss, time 9005ms
10 packets transmitted, 10 received, 0% packet loss, time 9004ms
10 packets transmitted, 10 received, 0% packet loss, time 9008ms
10 packets transmitted, 5 received, 50% packet loss, time 9046ms
10 packets transmitted, 7 received, 30% packet loss, time 9060ms
10 packets transmitted, 7 received, 30% packet loss, time 9029ms

Comments

  • eiYeK8dozai6KahyBeiYeK8dozai6KahyB Member

    Just to note, neither the gateway nor the 192.210.208.158 router is the cause here. I tested them for awhile and everything was good there. This looks like it's at the peering point, not internal.

  • InfinityInfinity Member, Host Rep

    Use mtr.

  • CharlesACharlesA Member

    @Infinity said:
    Use mtr.

    +1. mtr is awesome.

  • eiYeK8dozai6KahyBeiYeK8dozai6KahyB Member

    Fine. MTR it is.

                                              My traceroute  [v0.82]
myhost (0.0.0.0)                                                                 Thu Jun 26 18:33:47 2014
Keys:  Help   Display mode   Restart statistics   Order of fields   quit
                                                                  Packets               Pings
 Host                                                           Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. 192.210.208.158                                              0.0%   116    0.1   0.0   0.0   0.1   0.0
 2. 10ge-1.8.3.14.0.la1.colocrossing.com                        37.4%   116    1.9   2.9   0.5  31.9   5.9
 3. xe-5-3-0.er1.lax112.us.above.net                            44.3%   116    0.3   3.6   0.2  70.5  11.5
 4. ae16.cr1.lax112.us.above.net                                45.2%   116    0.5   3.8   0.4  28.9   7.0
 5. ae1.mpr1.lax12.us.above.net                                 43.5%   116    0.4   1.8   0.4  30.4   4.8
 6. 72.14.223.206                                               44.3%   116    0.5   3.9   0.4  32.6   7.9
 7. 209.85.248.185                                              59.1%   116    0.5   3.9   0.5  24.8   5.9
 8. 209.85.250.251                                              43.1%   116    1.0   1.9   0.7  31.4   4.1
 9. lax02s20-in-f8.1e100.net                                    44.7%   115    0.5   1.3   0.4  30.2   4.0
  • RalliasRallias Member

    Looks like a cord's loose again.

    Thanked by 2SynergyVPS Boxode
  • MagiobiwanMagiobiwan Member

    Have you opened a ticket? I've been noticing intermittent packet loss, but every time I go to investigate, it stops. That darned "IT Aura" again :|

  • eiYeK8dozai6KahyBeiYeK8dozai6KahyB Member

    @Magiobiwan said:
    Have you opened a ticket? I've been noticing intermittent packet loss, but every time I go to investigate, it stops. That darned "IT Aura" again :|

    I opened a ticket a week or so ago. They closed it and said another customer had been causing a DoS and that it was fixed. Problem was not resolved and the loss continued.

  • zionvpszionvps Member

    with the mtr it seems like packet loss is having at dc level (coloc)

  • MagiobiwanMagiobiwan Member

    Reply to it to re-open it. Unfortunately users keep getting their VPSes compromised by botnets (................) and as such we kill ONE DoSer, more pop up thanks to the botnet. I've been working on scripts to try and detect the binaries BEFORE they hammer the nodes, but the malware creators keep changing the names on me. SO FRUSTRATING!

  • jbilohjbiloh Administrator, Veteran

    Nothing wrong on our side. Looks like the server's link is saturated at times.

  • eiYeK8dozai6KahyBeiYeK8dozai6KahyB Member

    FYI an update on this issue... it's still ongoing and never really stopped. There are still DNS timeouts and connectivity problems at all hours of the day. The issue is less severe than when I first posted, but congestion is still occurring and I am losing packets to/from my host. I've written off BlueVM at this point.

    Thanked by 1upfreak
  • 345941272345941272 Member

    bluevm.com too irresponsible to my vps one less reason its ip and vps is assigned to the other customers, remote login is to reinstall the operating system found,

  • jbilohjbiloh Administrator, Veteran

    Most an MTR in both directions, from you to your server and from your server to you.

  • eiYeK8dozai6KahyBeiYeK8dozai6KahyB Member

    345941272 said:

    bluevm.com too irresponsible to my vps one less reason its ip and vps is assigned to the other customers, remote login is to reinstall the operating system found,

    Your grasp of written English could use strengthening, lest your grasp on the bottle could use easing.

  • eiYeK8dozai6KahyBeiYeK8dozai6KahyB Member

    Just to update on this issue, it kept going on for at least a month. I've given up on BlueVM as a possible host. Last I knew, this was still happening occasionally, though I noticed the congestion had reduced from nearly 24 hours per day to something more like 6 hours per day, with occasional intermittent DNS timeouts.

Sign In or Register to comment.