achkar
Is anybody else having ping and download problems with Terranet this week?
So ping to Google is fine: 72ms, Yahoo: 240ms.
Speedtest is giving me pings over 400ms; I usually get 130ms.
I have a backup connection from Ogero (1Mbps down) and I'm getting 80ms pings.
I have the 4Mbps down plan.
I tried connecting through wireless (different channels) and wired so this is not an issue. I also tried with different routers.
This led me to download the test file from Terranet at [url]ftp://speedtest1.terra.net.lb/001-gig-file[/url] . It is downloading at 423KB/s => 3465 kpbs, which is fine.
Downloading test files from thinkbroadband.com and other test sites is capped at 180KB/s.
So basically, it looks like Terranet is having problems.
Is anybody else having similar problems that can confirm my experience?
The-MMMs
mind stating what CO/Central your part of ?
achkar
Elissar. I think my traceroute to google.com shows the problem is from Terranet.
Notice the timeout between steps 4 and 6. Step 6 is in France (213.242.116.25) where as step 4 is in Lebanon.
It looks like Terranet is attempting a route that's failing and then falling back to the France backbone.
Compare to my backup connection from Ogero's traceroute. They both end up at the same IP, 213.242.116.25, in France.
Terranet, however, has a timeout request in its step 5.
Terranet
1 83 ms 99 ms 99 ms dsldevice.lan [192.168.1.254]
2 11 ms 10 ms 10 ms dsl-213-204-70-1.terra.net.lb [REMOVED]
3 10 ms 10 ms 44 ms 172.20.1.10
4 12 ms 14 ms 11 ms 3.gi-0-0-1.core-4.terra.net.lb [212.98.136.44]
5 * * * Request timed out.
6 88 ms 59 ms 50 ms 213.242.116.25
7 63 ms 62 ms 60 ms ae-7-7.ebr1.Paris1.Level3.net [4.69.143.238]
8 67 ms 68 ms 68 ms ae-48-48.ebr1.London1.Level3.net [4.69.143.113]
9 68 ms 67 ms 75 ms ae-56-111.csw1.London1.Level3.net [4.69.153.114]
10 68 ms 67 ms 68 ms ae-1-51.edge3.London1.Level3.net [4.69.139.73]
11 68 ms 73 ms 68 ms unknown.Level3.net [212.113.15.186]
12 67 ms 68 ms 68 ms 209.85.255.76
13 69 ms 69 ms 82 ms 209.85.253.92
14 74 ms 75 ms 77 ms 72.14.232.134
15 76 ms 75 ms 74 ms 209.85.252.83
16 * * * Request timed out.
17 73 ms 75 ms 73 ms wg-in-f101.1e100.net [173.194.78.101]
OGERO
1 18 ms 75 ms 98 ms dsldevice.lan [192.168.1.254]
2 83 ms 123 ms 110 ms [REMOVED]
3 49 ms 41 ms 39 ms 77.42.129.20
4 40 ms 40 ms 45 ms 192.168.111.2
5 84 ms 80 ms 81 ms 213.242.116.25
6 91 ms 92 ms 93 ms ae-7-7.ebr1.paris1.level3.net [4.69.143.238]
7 104 ms 102 ms 97 ms ae-45-45.ebr1.london1.level3.net [4.69.143.101]
8 109 ms 102 ms 96 ms ae-59-114.csw1.London1.Level3.net [4.69.153.126]
9 98 ms 132 ms 97 ms ae-1-51.edge3.london1.level3.net [4.69.139.73]
10 100 ms 96 ms 96 ms unknown.level3.net [212.113.15.186]
11 152 ms 127 ms 102 ms 209.85.255.76
12 100 ms 99 ms 105 ms 209.85.253.92
13 105 ms 116 ms 105 ms 66.249.95.173
14 128 ms 103 ms 103 ms 209.85.250.167
15 * * * Request timed out.
16 102 ms 104 ms 103 ms wi-in-f138.1e100.net [173.194.67.138]
amkahal
@achkar: this timeout doesn't mean anything is not normal, some routers in your way don't reply to the ICMP request, so it is normal.
yasamoka