Please can anything be done about the latency? I can only play after 7PM most of the days and the latency is constantly above 2000ms now.
Quality of the latency for online gaming really went downhill last two weeks.
Edit:
Ok, let me be honest. it's 12:12AM and even icmp ping won't go below 1100ms. Even connection to msn disconnects every few minutes.
Every last week of each month I ask if this will improve so I can know if I should stick with VISP or not but get either no reply of a vague reply. There are other things on the Internet than just browsing. When there are outages, I call VISP phone support, report the outage but I get accused that I'm lying and they insist everything is working.
https://customer.visp.net would still work but everything else wouldn't so I'm obviously not lying. Then an hour later, things work again which proves I wasn't lying.
I realize 35 USD a month is very cheap but it's not a excuse to treat customers badly. My account expires on the third of next month. If something doesn't drastically change, please don't renew my account. I don't appreciate being accused of making up stories. This is far below the worst definition of professionalism.
ping game.eternal-lands.com
PING game.eternal-lands.com (213.152.3.5) 56(84) bytes of data.
64 bytes from game.eternal-lands.com (213.152.3.5): icmp_seq=1 ttl=51 time=1556 ms
64 bytes from game.eternal-lands.com (213.152.3.5): icmp_seq=3 ttl=51 time=1699 ms
ping 2.2.2.10
PING 2.2.2.10 (2.2.2.10) 56(84) bytes of data.
64 bytes from 2.2.2.10: icmp_seq=1 ttl=61 time=10.0 ms
64 bytes from 2.2.2.10: icmp_seq=2 ttl=61 time=7.19 ms
64 bytes from 2.2.2.10: icmp_seq=3 ttl=61 time=10.0 ms
64 bytes from 2.2.2.10: icmp_seq=4 ttl=61 time=8.84 ms
64 bytes from 2.2.2.10: icmp_seq=5 ttl=61 time=6.86 ms
I'm pretty sure you are as annoyed of our complaints as we are of the quality of the connection. So please do something about it.
at 4:37 AM,
ping
www.google.com
PING
www.l.google.com (72.14.234.104) 56(84) bytes of data.
64 bytes from mil01s07-in-f104.1e100.net (72.14.234.104): icmp_seq=1 ttl=52 time=2644 ms
64 bytes from mil01s07-in-f104.1e100.net (72.14.234.104): icmp_seq=2 ttl=52 time=2223 ms
64 bytes from mil01s07-in-f104.1e100.net (72.14.234.104): icmp_seq=3 ttl=52 time=2100 ms
64 bytes from mil01s07-in-f104.1e100.net (72.14.234.104): icmp_seq=4 ttl=52 time=1923 ms
64 bytes from mil01s07-in-f104.1e100.net (72.14.234.104): icmp_seq=5 ttl=52 time=1959 ms
64 bytes from mil01s07-in-f104.1e100.net (72.14.234.104): icmp_seq=6 ttl=52 time=2099 ms
64 bytes from mil01s07-in-f104.1e100.net (72.14.234.104): icmp_seq=7 ttl=52 time=2384 ms