Any users having awful latency (in game or by pinging www.google.com for example), especially after 11:00PM , lately ?

If yes
- Who is your ISP ?
- When did this start (1 week ago, 1 month ago...) ?
- What day of the week / time of the day do you experience this the most ?

I am with Sodetel and I have the gaming plan. I can tell you right now their service is not the best I have seen.

The last modem led, which is the one for the "Internet" goes off several times per day and comes back to green around 30 seconds later. I have emailed them about this and all I get is an email (2 days later) simply saying "Problem solved". What an unbelievably professional reply/service. Really...

Here is a ping to google.com yesterday at 11:18 PM.

Pinging www.l.google.com [173.194.37.104] with 32 bytes of data:
Reply from 173.194.37.104: bytes=18 (sent 1) time=141ms TTL=52
Request timed out.
Reply from 173.194.37.104: bytes=18 (sent 1) time=148ms TTL=52
Reply from 173.194.37.104: bytes=18 (sent 1) time=148ms TTL=52
Request timed out.
Request timed out.
Reply from 173.194.37.104: bytes=18 (sent 1) time=146ms TTL=52
Reply from 173.194.37.104: bytes=18 (sent 1) time=144ms TTL=52
Reply from 173.194.37.104: bytes=18 (sent 1) time=149ms TTL=52
Reply from 173.194.37.104: bytes=18 (sent 1) time=146ms TTL=52
Request timed out.
Reply from 173.194.37.104: bytes=18 (sent 1) time=145ms TTL=52
Reply from 173.194.37.104: bytes=18 (sent 1) time=138ms TTL=52
Request timed out.
Request timed out.
Request timed out.
Reply from 173.194.37.104: bytes=18 (sent 1) time=139ms TTL=52
Reply from 173.194.37.104: bytes=18 (sent 1) time=141ms TTL=52
Reply from 173.194.37.104: bytes=18 (sent 1) time=132ms TTL=52

Needless to say this is anything but a gaming plan. Try playing WoW and let me know if you can manage to do anything in-game.
I am facing awful latency since 13, december.
ISP: terranet

ping to bbc.co.uk was 130 ms at most.
it became 360 ms at least.

sometimes i have 35% packet loss
I have Terranet DSL 512Kbps. Yes pings rates got bad lately. I play on garena; had ping 180ms. Now its up to 460ms; unplayable.
Why does the command ping www.bbc.co.uk produces different results from when I use pingtest.com? Which one is more reliable?
it's been like 36 hours i can't connect to messenger like i should be , browsing is crap and ingame WoW latency is completly unplayable , im with VISP 256k
are you sure 256Kbps is enough to play WOW ?
MrClass wroteare you sure 256Kbps is enough to play WOW ?
it is for questing and 5mans but in 25/10 mans he may need to reduce add-ons to bare minimum.
@Kassem: it depends on the location of the server you pinged, i believe in the ping-command results since it is a real icmp ping.
Please change countries and move to a more developed country.
You should know by now that online gaming in Lebanon is nearly impossible.
People stop complaining, we all know how internet/latency sucks,
get over it find a different hobby or just live with it "tannish tanta3esh" right?? :)
C:\Users\Jajoja>ping google.com

Pinging google.com [173.194.37.104] with 32 bytes of data:
Reply from 173.194.37.104: bytes=32 time=93ms TTL=52
Reply from 173.194.37.104: bytes=32 time=95ms TTL=52
Reply from 173.194.37.104: bytes=32 time=94ms TTL=52
Reply from 173.194.37.104: bytes=32 time=96ms TTL=52

Ping statistics for 173.194.37.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 93ms, Maximum = 96ms, Average = 94ms
Yawn :P
MrClass wroteare you sure 256Kbps is enough to play WOW ?
supposed to... i sometimes get 200ms during daytime on 256k with no real ip , and some other times.. don't ask :\ but usually it's playable except these 2 days.
Hi,
I concluded that terranet routes our upload via international fiber, but routes the download via Satellite Link (Sategate) , so this is the reason behind awful latency, at least for terranet users.

These are the results of tracerouting my machine from IP address 88.198.46.51
1                           *    *    *
2     HOSGate.your-server.de     213.239.224.1     de     0.152 ms           
    213-239-224-65.clients.your-server.de     213.239.224.65     de     0.132 ms      
    HOSGate.your-server.de     213.239.224.1     de     0.152 ms
3     hos-bb1.juniper4.ffm.hetzner.de     213.239.240.230     de     4.843 ms           
    hos-bb1.juniper1.ffm.hetzner.de     213.239.240.224     de     4.840 ms     4.833 ms
4     r9-xe-4-2-0-0-Fra-Anct.DE.DataBone.net     80.81.192.192     de     5.964 ms     5.962 ms     5.955 ms
5     r10-ae0-11-Waw-Lim-PL.linxtelecom.net     212.47.201.143     ee     24.481 ms     24.481 ms     24.470 ms
6     r2-ge-0-0-0-304-Vno-Lnrg.LT.DataBone.net     212.47.201.79     ee     31.694 ms     31.626 ms     31.615 ms
7                       *    *    *
8                       *    *    *
9     owen.satgate.net     77.94.34.103     ru     32.283 ms     31.830 ms     32.274 ms
10                       *    *    *
11     rev-212-98-155-58.terra.net.lb     212.98.155.58     lb     424.809 ms     425.079 ms     425.376 ms
12     rev-212-98-155-57.terra.net.lb     212.98.155.57     lb     425.501 ms     425.816 ms     425.803 ms
13     gi-0-1.core-2.terra.net.lb     212.98.136.55     lb     350.881 ms     348.896 ms     350.827 ms
14     ssg.terra.net.lb     212.98.136.18     lb     351.173 ms     353.878 ms     353.857 ms
15                       *    *    *
16                       *    *    *
17                       *    *    *
and these are the results for traceroute in reverse way (from me to 88.198.46.51)
  1    49 ms    47 ms    50 ms  ssg.terra.net.lb [212.98.136.18]
  2    51 ms    47 ms    49 ms  1.gi-0-3.core-2.terra.net.lb [212.98.136.17]
  3    51 ms    47 ms    49 ms  3.gi-0-0-1.core-4.terra.net.lb [212.98.136.44]
  4     *        *        *     Request timed out.
  5   385 ms   400 ms   384 ms  195.50.120.69
  6   380 ms   377 ms   378 ms  ae-34-52.ebr2.London1.Level3.net [4.69.139.97]
  7   383 ms   373 ms   375 ms  ae-21-21.ebr2.Frankfurt1.Level3.net [4.69.148.18
6]
  8   394 ms   393 ms   382 ms  ae-82-82.csw3.Frankfurt1.Level3.net [4.69.140.26
]
  9   373 ms   377 ms   380 ms  ae-3-89.edge3.Frankfurt1.Level3.net [4.68.23.139
]
 10   366 ms   374 ms   380 ms  HETZNER-ONL.edge3.Frankfurt1.Level3.net [212.162
.40.206]
 11   373 ms   373 ms   386 ms  hos-bb1.juniper1.fs.hetzner.de [213.239.240.242]

 12   375 ms   380 ms   390 ms  hos-tr2.ex3k12.rz13.hetzner.de [213.239.224.45]

 13   391 ms   382 ms   375 ms  nemec2.internet.lv [88.198.46.51]

Trace complete.
little knowledge of networking and you will understand what i mean.

Enjoy the Lebanese Internet :S
512Kbps DSL from Ogero is giving me 160-220ms latency, so gameplay is very fine. But this is with the "latency hack." I'm not sure where it would be without it. Probably around 190-250, but playable all the same. Once or twice an hour it spikes for a few seconds up to 500ms or so, but that's fine with me.


Maybe the storm that hit Beirut 2 weeks ago messed up somethings and they're working on getting them fixed?
jajoja wrote
C:\Users\Jajoja>ping google.com

Pinging google.com [173.194.37.104] with 32 bytes of data:
Reply from 173.194.37.104: bytes=32 time=93ms TTL=52
Reply from 173.194.37.104: bytes=32 time=95ms TTL=52
Reply from 173.194.37.104: bytes=32 time=94ms TTL=52
Reply from 173.194.37.104: bytes=32 time=96ms TTL=52

Ping statistics for 173.194.37.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 93ms, Maximum = 96ms, Average = 94ms
Yawn :P
With that latency, I'd expect you to have been better at Black Ops. I get minimum 5 less kills than I'm supposed to because of the damn lag.
for IDM latency goes up and down around 200-500 but after 11 pm everything is screwed up. everytime i call them they say everything normal LOL