VISP internet service through Sodetel gateways !? - Page 6 - The Orange Room

Red Phoenix

Quote:

Originally Posted by IA64

Did you guys notice the improvements with the ping response time ? Because I did. Im getting 300-400 ms lag instead of 500-900ms. I did some traces and what I notice is that we are now directly connected to Sodetel . I checked the routes this morning and it was like :

Now for the calculations, they managed to reduce the lag by ~400ms.. still, we are lagging another 400ms which is not good enough for gaming.

I believe this is the best they can do for the moment. But who knows... Keep up the good work and good luck.

ya it dropped 200ms from 600 to 400 on my connection, but i think this has something to do with the fact that we are now pinging at 1 AM in the morning :)

IA64

Believe me I though the same thing but yesterday the ping was like 600ms 3:00AM and the traceroute done this morning was at 8:00 AM before heading to the office. I am just trying to be optimistic

Red Phoenix

Quote:

Originally Posted by IA64

Believe me I though the same thing but yesterday the ping was like 600ms 3:00AM and the traceroute done this morning was at 8:00 AM before heading to the office. I am just trying to be optimistic

hehe, good for u.

i think i'm a pessimist by nature.

well, perhaps it's due to all the ppl that left visp already and switched to dsl ??

:P

IA64

Yes you are right. But we are not sheep after all. I prefer staying without internet rather than using that crappy DSL. They are stealing people. And believe me, if VISP comes back ( like it used to be before mid 2008 not before april 2009 !) they all are going to revert back. People are not happy with DSL, trust me. But again, it all depends on networking knowledge of the end-user.

Red Phoenix

Quote:

Originally Posted by IA64

Yes you are right. But we are not sheep after all. I prefer staying without internet rather than using that crappy DSL. They are stealing people. And believe me, if VISP comes back ( like it used to be before mid 2008 not before april 2009 !) they all are going to revert back. People are not happy with DSL, trust me. But again, it all depends on networking knowledge of the end-user.

ya but now there is no normal connection at all, and do u know for how much visp resellers charge for a 128k connection here in achrafieh ??

53 000 freaking LL.

IA64 · 03:03 AM

is it a reseller or Sub-ISP ?

BTW, I think someone is reading us

Ping is now 197ms on google . Not bad. and the route changed :

Tracing route to Google [74.125.43.147]
over a maximum of 30 hops:

1 1 ms 3 ms 14 ms 172.16.*.1
2 * 3 ms * 194.146.*.*
3 2 ms 4 ms 4 ms 172.16.11.105
4 8 ms 3 ms 5 ms 172.16.5.114
5 4 ms 9 ms 23 ms 89.108.129.1
6 * * * Request timed out.
7 175 ms 168 ms 160 ms 12.118.94.93
8 176 ms 158 ms 175 ms 12.122.130.166
9 156 ms 152 ms 152 ms 12.122.130.129
10 296 ms 177 ms 207 ms 192.205.33.94
11 173 ms 171 ms 149 ms 4.68.16.190
12 163 ms 211 ms 185 ms 4.69.134.73
13 166 ms 175 ms 178 ms 4.69.132.93
14 199 ms 179 ms 182 ms 4.69.134.186
15 177 ms 180 ms 167 ms 4.69.134.153
16 178 ms 176 ms 171 ms 4.69.137.53
17 * 188 ms 197 ms 4.69.140.26
18 171 ms 163 ms 207 ms 4.68.23.139
19 205 ms 192 ms 196 ms 212.162.24.18
20 204 ms 202 ms 192 ms 209.85.254.108
21 202 ms 209 ms 218 ms 216.239.48.11
22 203 ms 212 ms 197 ms 64.233.174.53
23 202 ms 218 ms 216 ms 209.85.250.1
24 196 ms 198 ms 203 ms 74.125.43.147

Trace complete.

Can you verify please ?

Red Phoenix

hehe, we are under observation by the powers that be :)

btw IA64, dude ur traceroot copy pastes have ur first name in them. edit them or something hehe

traceroutes are taking forever here for me, so here's the google ping instead.

ping google.com -t

Pinging google.com [209.85.171.100] with 32 bytes of data:

Reply from 209.85.171.100: bytes=32 time=506ms TTL=228
Request timed out.
Reply from 209.85.171.100: bytes=32 time=497ms TTL=228
Reply from 209.85.171.100: bytes=32 time=494ms TTL=228
Request timed out.
Reply from 209.85.171.100: bytes=32 time=495ms TTL=228
Reply from 209.85.171.100: bytes=32 time=487ms TTL=228
Reply from 209.85.171.100: bytes=32 time=494ms TTL=228
Request timed out.
Reply from 209.85.171.100: bytes=32 time=501ms TTL=228
Reply from 209.85.171.100: bytes=32 time=505ms TTL=228
Reply from 209.85.171.100: bytes=32 time=501ms TTL=228
Reply from 209.85.171.100: bytes=32 time=493ms TTL=228
Reply from 209.85.171.100: bytes=32 time=503ms TTL=228
Reply from 209.85.171.100: bytes=32 time=503ms TTL=228
Reply from 209.85.171.100: bytes=32 time=497ms TTL=228
Reply from 209.85.171.100: bytes=32 time=499ms TTL=228
Reply from 209.85.171.100: bytes=32 time=499ms TTL=228
Request timed out.
Reply from 209.85.171.100: bytes=32 time=497ms TTL=228
Reply from 209.85.171.100: bytes=32 time=498ms TTL=228
Reply from 209.85.171.100: bytes=32 time=494ms TTL=228
Reply from 209.85.171.100: bytes=32 time=503ms TTL=228
Reply from 209.85.171.100: bytes=32 time=497ms TTL=228
Reply from 209.85.171.100: bytes=32 time=506ms TTL=228
Reply from 209.85.171.100: bytes=32 time=500ms TTL=228
Reply from 209.85.171.100: bytes=32 time=502ms TTL=228
Reply from 209.85.171.100: bytes=32 time=497ms TTL=228
Reply from 209.85.171.100: bytes=32 time=495ms TTL=228
Reply from 209.85.171.100: bytes=32 time=498ms TTL=228
Reply from 209.85.171.100: bytes=32 time=499ms TTL=228
Reply from 209.85.171.100: bytes=32 time=493ms TTL=228
Reply from 209.85.171.100: bytes=32 time=496ms TTL=229
Reply from 209.85.171.100: bytes=32 time=498ms TTL=229
Reply from 209.85.171.100: bytes=32 time=493ms TTL=229
Reply from 209.85.171.100: bytes=32 time=493ms TTL=229
Reply from 209.85.171.100: bytes=32 time=2565ms TTL=229
Reply from 209.85.171.100: bytes=32 time=501ms TTL=229
Reply from 209.85.171.100: bytes=32 time=493ms TTL=229
Reply from 209.85.171.100: bytes=32 time=501ms TTL=229
Request timed out.
Request timed out.
Reply from 209.85.171.100: bytes=32 time=502ms TTL=229
Reply from 209.85.171.100: bytes=32 time=497ms TTL=229

Ping statistics for 209.85.171.100:
Packets: Sent = 44, Received = 38, Lost = 6 (13% loss)
Approximate round trip times in milli-seconds:
Minimum = 487ms, Maximum = 2565ms, Average = 552ms
Control-C

Red Phoenix

ok AI64, i edited my old post which quoted ur text which had unfiltered traceroute in them also.

IA64

Hmm weird. I think you better switch to VISP Sub-ISP. 53,000LL is too much for a 128/32 kpbs. Even VISP has a fair usage policy so unlimited downloads is not an argument.

Do you have that double speed thing at night also ? after 1:00AM usually.

Red Phoenix

Quote:

Originally Posted by IA64

Hmm weird. I think you better switch to VISP Sub-ISP. 53,000LL is too much for a 128/32 kpbs. Even VISP has a fair usage policy so unlimited downloads is not an argument.

Do you have that double speed thing at night also ? after 1:00AM usually.

no no no man, all visp resellers in my region are thieves.