After the upgrade exactly on Friday 7th of October something bad happened for me, my SNR dropped the exact same day they increased the cap on my modem from 1024 to 4095, this was my modem's statistics before:
SNR Margin (0.1 dB Down/UP): 302 310
Attenuation (0.1 dB Down/UP): 290 175
Output Power (0.1 dBm): 89 118
Attainable Rate (Kbps): 11360 1376
After:
SNR Margin (0.1 dB Down/UP): 221 303
Attenuation (0.1 dB Down/UP): 320 172
Output Power (0.1 dBm): 195 126
Attainable Rate (Kbps): 15696 945
As you notice, SNR dropped from 30 to 22 and the attainable speed increased ??
Now this is the bad part, my latency between me and Sodetel was 15-16 ms day and night, no matter any time I ping sodetel it is always low and stable but now things changed during the day it is 37-40 ms, and after 11:00 PM it starts to become really unstable between 70-90 ms, that's only between me to Sodetel not to an international website, check this:
Before:
Tracing route to sodetel.net.lb [89.108.129.77]
over a maximum of 30 hops:
1 24 ms <1 ms <1 ms 192.168.1.1
2 17 ms 14 ms 12 ms DSL-pool1.sodetel.net.lb [93.126.160.1]
3 25 ms 27 ms 13 ms 89.108.149.117
4 14 ms 14 ms 14 ms 89.108.128.225
5 16 ms 15 ms 13 ms 89.108.129.1
6 15 ms 14 ms 14 ms ns2.sodetel.net.lb [89.108.129.77]
Trace complete.
After:
Tracing route to sodetel.net.lb [89.108.129.77]
over a maximum of 30 hops:
1 13 ms <1 ms <1 ms 192.168.1.1
2 37 ms 36 ms 36 ms DSL-pool1.sodetel.net.lb [93.126.160.1]
3 37 ms 36 ms 36 ms 89.108.149.117
4 39 ms 39 ms 40 ms 89.108.128.245
5 39 ms 39 ms 37 ms 89.108.129.1
6 96 ms 40 ms 39 ms ns2.sodetel.net.lb [89.108.129.77]
Trace complete.
Ping After 11:00 PM:
C:\Users\Aly>ping sodetel.net.lb -t
Pinging sodetel.net.lb [89.108.129.77] with 32 bytes of data:
Reply from 89.108.129.77: bytes=32 time=75ms TTL=59
Reply from 89.108.129.77: bytes=32 time=70ms TTL=59
Reply from 89.108.129.77: bytes=32 time=76ms TTL=59
Reply from 89.108.129.77: bytes=32 time=69ms TTL=59
Reply from 89.108.129.77: bytes=32 time=76ms TTL=59
Reply from 89.108.129.77: bytes=32 time=70ms TTL=59
Reply from 89.108.129.77: bytes=32 time=74ms TTL=59
Reply from 89.108.129.77: bytes=32 time=69ms TTL=59
Reply from 89.108.129.77: bytes=32 time=74ms TTL=59
Reply from 89.108.129.77: bytes=32 time=76ms TTL=59
Reply from 89.108.129.77: bytes=32 time=71ms TTL=59
Reply from 89.108.129.77: bytes=32 time=74ms TTL=59
Request timed out.
Reply from 89.108.129.77: bytes=32 time=76ms TTL=59
Reply from 89.108.129.77: bytes=32 time=73ms TTL=59
Reply from 89.108.129.77: bytes=32 time=76ms TTL=59
Reply from 89.108.129.77: bytes=32 time=69ms TTL=59
Ping statistics for 89.108.129.77:
Packets: Sent = 17, Received = 16, Lost = 1 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 69ms, Maximum = 76ms, Average = 73ms
Control-C
Please can any sodetel user check ? did you know what was your ping (
to sodetel) before the upgrade and after and share please ? if it will stay like that I wont stay with Sodetel, in the past the bottleneck was on the backbones, now that international capacity is not "the issue" anymore, local links saturation is bullsh*t :S