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

› › Weloveservers - Serious issue
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.

Weloveservers - Serious issue

KeyJeyKeyJey Member
edited October 2014 in Providers

Hi, I just got an interesting offer from weloveservers.net. 6GB Guaranteed RAM + 6GB vSwap, 80GBs HD, 8x cores, etc.

I got the offer in NYC location but facing some network issues and they don't see to to be interested to understand the problem. Seems to be a routing problem.

I have some other servers in NY area, and my ping from one of my servers (in digital ocean, NY2 DC) is this (plz check the 58% of packet loss):

 root@sip:~ $ ping 192.210.240.111


 PING 192.210.240.111 (192.210.240.111) 56(84) bytes of data.
 64 bytes from 192.210.240.111: icmp_seq=1 ttl=55 time=19.9 ms
 64 bytes from 192.210.240.111: icmp_seq=2 ttl=55 time=13.1 ms
 64 bytes from 192.210.240.111: icmp_seq=3 ttl=55 time=12.8 ms
 64 bytes from 192.210.240.111: icmp_seq=4 ttl=55 time=16.6 ms
 64 bytes from 192.210.240.111: icmp_seq=5 ttl=55 time=12.0 ms
 64 bytes from 192.210.240.111: icmp_seq=6 ttl=55 time=11.7 ms
 64 bytes from 192.210.240.111: icmp_seq=7 ttl=55 time=11.7 ms
 64 bytes from 192.210.240.111: icmp_seq=8 ttl=55 time=12.2 ms
 64 bytes from 192.210.240.111: icmp_seq=9 ttl=55 time=12.3 ms
 64 bytes from 192.210.240.111: icmp_seq=10 ttl=55 time=11.9 ms
 64 bytes from 192.210.240.111: icmp_seq=11 ttl=55 time=18.5 ms
 64 bytes from 192.210.240.111: icmp_seq=12 ttl=55 time=13.2 ms
 64 bytes from 192.210.240.111: icmp_seq=13 ttl=55 time=26.0 ms
 64 bytes from 192.210.240.111: icmp_seq=14 ttl=55 time=15.3 ms
 64 bytes from 192.210.240.111: icmp_seq=15 ttl=55 time=18.9 ms
 64 bytes from 192.210.240.111: icmp_seq=30 ttl=55 time=28.0 ms
 64 bytes from 192.210.240.111: icmp_seq=33 ttl=55 time=23.0 ms
 64 bytes from 192.210.240.111: icmp_seq=37 ttl=55 time=23.8 ms
 64 bytes from 192.210.240.111: icmp_seq=48 ttl=55 time=22.3 ms
 64 bytes from 192.210.240.111: icmp_seq=49 ttl=55 time=22.6 ms
 64 bytes from 192.210.240.111: icmp_seq=53 ttl=55 time=22.5 ms
 64 bytes from 192.210.240.111: icmp_seq=56 ttl=55 time=11.7 ms
 64 bytes from 192.210.240.111: icmp_seq=57 ttl=55 time=11.8 ms
 64 bytes from 192.210.240.111: icmp_seq=58 ttl=55 time=11.9 ms
 --- 192.210.240.111 ping statistics ---
 58 packets transmitted, 24 received, 58% packet loss, time 57627ms
 rtt min/avg/max/mdev = 11.737/16.865/28.009/5.285 ms

Also, I use to have a ping of 115-130ms to all NY servers from home (Rio de Janeiro) and to this one I get between 170 and 290ms.

And also check this:

http://pastebin.com/SiqaFU6x

From one of my servers in germany same problem (14% loss):

 Respuesta desde 192.210.240.111: bytes=32 tiempo=130ms TTL=50
 Tiempo de espera agotado para esta solicitud.
 Tiempo de espera agotado para esta solicitud.
 Respuesta desde 192.210.240.111: bytes=32 tiempo=139ms TTL=50
 Respuesta desde 192.210.240.111: bytes=32 tiempo=139ms TTL=50
 Respuesta desde 192.210.240.111: bytes=32 tiempo=139ms TTL=50
 Tiempo de espera agotado para esta solicitud.
 Tiempo de espera agotado para esta solicitud.
 Respuesta desde 192.210.240.111: bytes=32 tiempo=140ms TTL=50
 Tiempo de espera agotado para esta solicitud.
 Respuesta desde 192.210.240.111: bytes=32 tiempo=134ms TTL=50
 Respuesta desde 192.210.240.111: bytes=32 tiempo=137ms TTL=50
 Respuesta desde 192.210.240.111: bytes=32 tiempo=130ms TTL=50
 Respuesta desde 192.210.240.111: bytes=32 tiempo=133ms TTL=50
 Respuesta desde 192.210.240.111: bytes=32 tiempo=130ms TTL=50
 Respuesta desde 192.210.240.111: bytes=32 tiempo=140ms TTL=50
 Tiempo de espera agotado para esta solicitud.
 Tiempo de espera agotado para esta solicitud.
 Tiempo de espera agotado para esta solicitud.
 Tiempo de espera agotado para esta solicitud.
 Respuesta desde 192.210.240.111: bytes=32 tiempo=139ms TTL=50
 Tiempo de espera agotado para esta solicitud.
 Respuesta desde 192.210.240.111: bytes=32 tiempo=130ms TTL=50
 Respuesta desde 192.210.240.111: bytes=32 tiempo=130ms TTL=50

 Estadísticas de ping para 192.210.240.111:
     Paquetes: enviados = 1418, recibidos = 1209, perdidos = 209
     (14% perdidos),
 Tiempos aproximados de ida y vuelta en milisegundos:
     Mínimo = 129ms, Máximo = 246ms, Media = 130ms

Any tip ? they said last reply:

Sorry, we are the VPS provider.We solve the problem which arrives in the VPS.If you are facing any problem in your VPS means please contact us we will help you immediately.

Thanks

«1

Comments

  • NyrNyr Community Contributor, Veteran

    I would ask for a refund.

    Anyway, looks like Indian outsourced support or something like that.

  • alessioalessio Member

    What does a traceroute say?

  • julfojulfo Member

    Weird, their support is normally fantastic for me and I have no issues apart from low IO speed

  • PatrickPatrick Member 
    HOST: lg                                        Loss%   Snt   Last   Avg  Best  Wrst StDev
 11. 78.152.57.111                               0.0%    10   93.6  98.1  93.6 136.1  13.4
 12. 10ge-1-3-0.01-02.er1.buf1.colocrossing.com  0.0%    10   93.4 155.7  92.7 202.0  47.2
 13. 10ge-1.03-c66.aggr1.buf1.colocrossing.com   0.0%    10  201.9 184.0 148.7 201.9  21.3
 14. 10.8.30.74                                  0.0%    10   93.5  93.4  93.3  93.6   0.1
 15. ???                                        100.0    10    0.0   0.0   0.0   0.0   0.0
 16. 192-210-240-111-host.colocrossing.com      60.0%    10  210.0 195.5 171.0 210.0  17.1

    Looks like DDoS

  • KeyJeyKeyJey Member

    how do u put the code ? forgot ....

  • tarasistarasis Member
    edited October 2014

    @KeyJey said:
    how do u put the code ? forgot ....

    Put the text between two ticks " ` "

    So blah blah becomes (dang I can't escape that so you can see)

    blah blah

    Thanked by 1vladka24
  • KeyJeyKeyJey Member

    @nyr I' have more VPSs with them and usually was very happy with everything, support was awesome.

    @julfo I agree ... until now

  • NekkiNekki Veteran

    Bit of a disappointing support response, might be worth tagging the WLS guys here to see what they say?

  • rmlhhdrmlhhd Member

    I agree with @iniz

    Looks a lot like a DDoS, wait a few hours and the issue will likely be resolved.

  • PatrickPatrick Member

    rmlhhd said: I agree with @iniz

    Looks a lot like a DDoS, wait a few hours and the issue will likely be resolved.

    Seems fixed now, could be due to a lot of things really. In/out DDoS or someone filling conntrack tables and packets being dropped etc.

     11. 78.152.57.111                                   0.0%    10   93.7  98.3  93.6 137.5  13.8
 12. 10ge-1-3-0.01-02.er1.buf1.colocrossing.com      0.0%    10   92.8  93.6  92.7  95.5   0.9
 13. 10ge-1.03-c66.aggr1.buf1.colocrossing.com       0.0%    10   92.7  92.8  92.7  93.0   0.1
 14. 10.8.30.74                                      0.0%    10   93.3  93.5  93.2  94.8   0.5
 15. 192-210-240-3-host.colocrossing.com             0.0%    10   92.5  92.5  92.4  92.7   0.1
 16. 192-210-240-111-host.colocrossing.com          10.0%    10   94.0  93.8  93.7  94.0   0.1
  • KeyJeyKeyJey Member

    Yeah, looks like that, but this replies?

    Like "servers work fine" or "it's an issue from your side" ????? It's horrible when they talk you as if u're really stupid. V:ery unprofessional. I hate it.

  • KeyJeyKeyJey Member

    tarasis said: Put the text between two ticks " ` "

    So blah blah becomes (dang I can't escape that so you can see)

    blah blah

    Still didn't get it, must be my english, sorry LOL

  • akzakz Member

    WLS support only gets better when Chris is the actual one responding. Noticed this after the painful episode in their Florida location. All is fixed after moving to Kent but I dont even use it anymore.. just idle.

  • kkrajkkkrajk Member

    KeyJey said: Still didn't get it, must be my english, sorry LOL

    enclose whatever you want within asterisks like how you would do quotes on a word
    i.e. " becomes *

  • netomxnetomx Moderator, Veteran

    @ez2uk said:

    or use < pre > like this:

     hello
yaaaaal
    Thanked by 1kkrajk
  • KeyJeyKeyJey Member

    I just saw that the editor has a "Ctrl + O" to post code :P

    Code, code xD

  • netomxnetomx Moderator, Veteran

    orly

    nice!

    Thanked by 1KeyJey
  • hostnoobhostnoob Member

    yellow boxes be like

  • jbilohjbiloh Administrator, Veteran

    I looked at the BW graph for that server, looks like its got some traffic abusers on it. I've notified your provider for you. :)

    Thanked by 4KeyJey DalekOfSkaro Mark_R TriDoxiuM
  • KeyJeyKeyJey Member

    Still facing horrible problems with colocrossing, this a trace from another server in NYC (DigitalOcean). All my servers there having same latency and network issues:

     Host                                                        Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. 107.170.7.254                                             0.0%    20    1.1   1.8   0.4  11.4   2.6
 2. 192.241.164.233                                           0.0%    20    0.4   0.7   0.3   3.2   0.8
 3. nyk-b5-link.telia.net                                     0.0%    20    5.0   6.4   0.6  39.4  12.7
 4. nyk-bb2-link.telia.net                                    0.0%    20    0.9   4.9   0.9  42.3  12.0
 5. nyk-b3-link.telia.net                                     0.0%    19    1.3   3.5   1.3  41.0   9.1
 6. tripartz-ic-155271-nyk-b3.c.telia.net                     0.0%    19    4.9   5.5   1.0  13.5   4.6
 7. eth1-4.edge1.nyc4.us.as5580.net                           0.0%    19    2.2   6.1   2.1  14.6   4.5
 8. 78.152.57.111                                             0.0%    19  125.6 127.1 123.0 152.5   6.5
 9. ???
10. ???
11. host.colocrossing.com                                     0.0%    19   11.8  11.8  11.6  11.9   0.1
12. host.colocrossing.com                                    15.8%    19  125.0 125.0 124.7 125.4   0.2
  • jbilohjbiloh Administrator, Veteran

    The issue is Not us as I mentioned earlier, the problem is that the node your hosted on by we love servers clearly has abusive traffic being sent from it hence the packet loss at the machines hop. Nothing we can do, the provider will need to login to the server and resolve it.

  • KeyJeyKeyJey Member

    Well, I asked for a refund yesterday and they didn't refund, just tomd me that "they will fix it". But network is still crazy and they have problems on nodes (that didn't fix yet).

    I asked again to refund coz this reasons:

    1.- check my last tickets.
2.- look this, from a local server in same area (nyc), digital ocean, a local server in same NY area: http://pastebin.com/72SiZ3Gf
3.- U lost the quality of your support
4.- U didn't tell me that u're experiencing any attacks and other network problems that are obvious
5.- I'm still waiting for a reply of the ticket #776754 for 3 days. Now u don't need to reply it now, no worries

    And they just replied:

    We do not offer refunds after three days of active service.

    LOL.

  • KeyJeyKeyJey Member

    @jbiloh I know it's a problem of them, but they are being really unprofessional, as you can see ....

    I never expected this from weloveservers.net, I had very good feedback from them with my other 4 servers active in my panel.

  • trexostrexos Member
    edited October 2014

    I always wonder what happens behind WLS. I have one UK server and to put it simple it runs great. I only faced one problem, where the server was running but no access from outside was possible. I opened a ticket and they resolved everything within 1 hour. Anyway, I only use their UK node and it looks like these problems occur on US nodes.

  • KeyJeyKeyJey Member

    Yes, as I said before, I didn't have anything serious 'til now. I have 4 other VPSs with them 2 in UK and 2 in US.

    This is so weird.

  • trexostrexos Member

    @KeyJey and you only face issues with the US ones?

  • KeyJeyKeyJey Member

    Yes, seem to in US nodes only

    Thanked by 1trexos
  • ronaldgrnronaldgrn Member

    Its not just the OP.. same for me as well.. sad that its still an issue

    Ping statistics for 192.210.240.XXX:
    Packets: Sent = 20, Received = 12, Lost = 8 (40% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 142ms, Maximum = 233ms, Average = 204ms

  • KeyJeyKeyJey Member

    Of course ! anyone who checks this will see what am I talking about ! Also ping from NY (same area zone) is giving more than 100ms !!!!!!!!!!!!

  • KeyJeyKeyJey Member

    And they still say that they don't refund after 3 days ..... how can they play with its users this way ???

Sign In or Register to comment.