Internationall Packet loss and Bandwith

U

Ultrafy

Member
Joined
Nov 4, 2018
Messages
13
Reaction score
0
Hope everyone is doing good , over a month now and still having internationall packet loss upto 20 percent and extremely high ping like 300 - to eu btw ... which normally through the day is 150 ... im so depressed and so mad at the same time ... cant even watch streams at night cause everything buffers ... if anyone has any help on what i can tell the isp cell c fibre on openserve and what you guys think about this it would mean alot .. i think its the routing but yeah
 
MTR traces are normally a good idea.

WINMTR is easy to use.
 
THIS MY TRACEROUTE TO SEACOM CAPETOWN ... DOES THIS LOOK NORMALL ??


|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| HomeWare.lan - 0 | 70 | 70 | 0 | 0 | 1 | 0 |
| No response from host - 100 | 14 | 0 | 0 | 0 | 0 | 0 |
| 41.50.1.89 - 0 | 70 | 70 | 4 | 20 | 50 | 5 |
| 41.50.1.90 - 0 | 70 | 70 | 12 | 50 | 114 | 48 |
| 41.50.12.66 - 0 | 70 | 70 | 11 | 49 | 113 | 48 |
| ae-2-93.er-01-jnb.za.seacomnet.com - 0 | 70 | 70 | 11 | 49 | 113 | 48 |
| No response from host - 100 | 14 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 14 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 14 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 14 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 14 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 14 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 14 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 14 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 14 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 14 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 14 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 14 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 14 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 14 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 14 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 14 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 14 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 14 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 14 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 14 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 14 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 14 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 14 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 14 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
 
THIS MY TRACEROUTE TO AMAZON WEB SERVERS IN EUROPE ... THIS DOESNT LOOK RIGHT ?




------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| HomeWare.lan - 0 | 64 | 64 | 0 | 0 | 4 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| 41.50.1.89 - 0 | 64 | 64 | 4 | 10 | 85 | 5 |
| 41.50.1.90 - 0 | 64 | 64 | 19 | 57 | 101 | 75 |
| 41.50.12.66 - 0 | 64 | 64 | 19 | 56 | 100 | 74 |
| 41.48.253.69 - 0 | 64 | 64 | 4 | 5 | 12 | 5 |
| 196-60-9-110.ixp.joburg - 0 | 64 | 64 | 4 | 5 | 12 | 5 |
| 52.93.56.26 - 0 | 64 | 64 | 4 | 5 | 12 | 6 |
| 52.93.56.37 - 0 | 64 | 64 | 4 | 5 | 11 | 5 |
| 54.239.46.76 - 0 | 64 | 64 | 180 | 219 | 281 | 223 |
| 54.239.46.85 - 0 | 64 | 64 | 172 | 174 | 196 | 173 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| 54.239.44.140 - 0 | 64 | 64 | 172 | 175 | 196 | 173 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| 52.93.6.132 - 0 | 64 | 64 | 181 | 236 | 408 | 251 |
| 52.93.101.17 - 0 | 64 | 64 | 172 | 175 | 195 | 173 |
| 52.93.101.32 - 0 | 64 | 64 | 174 | 191 | 219 | 175 |
| 52.93.7.121 - 0 | 64 | 64 | 172 | 175 | 195 | 173 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
 
C:\Users\User-PC>TRACERT 52.17.5.81

Tracing route to ec2-52-17-5-81.eu-west-1.compute.amazonaws.com [52.17.5.81]
over a maximum of 30 hops:

once again to amazon web servers in europe

1 <1 ms <1 ms <1 ms HomeWare.lan [192.168.1.1]
2 * * * Request timed out.
3 14 ms 11 ms 13 ms 41.50.1.89
4 48 ms 44 ms 43 ms 41.50.1.90
5 40 ms 44 ms 45 ms 41.50.12.66
6 5 ms 5 ms 5 ms 41.48.253.69
7 5 ms 5 ms 5 ms 196-60-9-110.ixp.joburg [196.60.9.110]
8 6 ms 5 ms 6 ms 52.93.56.26
9 5 ms 5 ms 5 ms 52.93.56.37
10 212 ms 271 ms 230 ms 54.239.46.76
11 174 ms 185 ms 183 ms 54.239.46.85
12 * * * Request timed out.
13 174 ms 176 ms 175 ms 54.239.44.140
14 * * * Request timed out.
15 276 ms 255 ms 315 ms 52.93.6.132
16 173 ms 200 ms 191 ms 52.93.101.17
17 206 ms 189 ms 192 ms 52.93.101.32
18 179 ms 185 ms 183 ms 52.93.7.121
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
 
why is my ping to capetowns seacom so high this isnt right ?



C:\Users\User-PC>tracert news.com

Tracing route to news.com [64.30.224.82]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms HomeWare.lan [192.168.1.1]
2 * * * Request timed out.
3 5 ms 5 ms 5 ms 41.50.1.89
4 97 ms 97 ms 100 ms 41.50.1.90
5 64 ms 62 ms 59 ms 41.50.12.66
6 62 ms 72 ms 84 ms ae-2-93.er-01-jnb.za.seacomnet.com [105.22.32.149]
7 175 ms 177 ms 170 ms ce-0-2-0-0.cr-02-jnb.za.seacomnet.com [105.16.28.2]
8 239 ms 227 ms 229 ms xe-0-0-0-9.cr-02-cpt.za.seacomnet.com [105.16.13.198]
9 207 ms 212 ms 210 ms xe-0-1-0-3.cr-02-lhr.uk.seacomnet.com [105.16.11.25]
10 228 ms 211 ms 208 ms ae-4-0.pp-01-lhr.uk.seacomnet.com [105.16.35.8]
11 240 ms 244 ms 233 ms akamai.prolexic.com [195.66.224.31]
12 161 ms 161 ms 161 ms po110.bs-b.sech-lon2.netarch.akamai.com [72.52.60.200]
13 188 ms 207 ms 189 ms po565-10.bs-a.sech-ams.netarch.akamai.com [72.52.1.157]
14 195 ms 224 ms 189 ms ae121.access-a.sech-lon2.netarch.akamai.com [72.52.60.205]
15 420 ms 435 ms 370 ms 93.191.173.69
16 319 ms 314 ms 297 ms a209-200-160-232.deploy.static.akamaitechnologies.com [209.200.160.232]
17 296 ms 313 ms 295 ms reth0-1000.fw2.phx1.cbsig.net [216.239.126.193]
18 298 ms 296 ms 305 ms irb-1008.spine1.phx1.cbsig.net [216.239.126.208]
19 305 ms 303 ms 315 ms phx1-rb-gtm3-tron-xw-lb.cnet.com [64.30.224.82]

Trace complete.
 
The traces are normal, both in regards to latency and the hopes that time out or do not respond..

Bear in mind that ICMP, the protocol that traceroute uses be default, is not very high priority for many devices and not always allowed by others.. This inevitably results in most traceroutes showing higher latency on some hops that doesn't occur on subsequent hops and in certain hops not responding..

A latency issue will start on a hop and you will see the same or higher latency on all subsequent hops until it reaches the destination.. High latency on a single hop does not mean too much in the greater scheme of things..
 
Also you're with Cell C lol, not the best FTTH provider tbh.
 
ghostR said:
Also you're with Cell C lol, not the best FTTH provider tbh.
Click to expand...
This his 5th or 6th post complaining about the same thing.. In his first or second post I suggested he looks for a different ISP if his complaints fall on deaf ears..
 
WAslayer said:
This his 5th or 6th post complaining about the same thing.. In his first or second post I suggested he looks for a different ISP if his complaints fall on deaf ears..
Click to expand...
yep thats what im going to do , they say it looks normall and nothing is wrong from theyre side ?
 
Ultrafy said:
yep thats what im going to do , they say it looks normall and nothing is wrong from theyre side ?
Click to expand...
It's like I said in my earlier posts, the traceroutes look fine and because of the low priority nature that most network devices place on the ICMP protocol, the latency on specific hops don't mean much..

There is no doubt that they are running their international links hot.. from 18:00 to about 00:00 every evening, most people with internet start streaming, gaming etc.. Internet usage peaks and any ISP who doesn't have enough capacity to handle this increased traffic will result in their end users seeing packet loss and slow speeds, but not necessarily higher latency..

Packet captures and TCP based traceroutes may show any issues better, but at the same time, 1st line support for any ISP will just do the scripted troubleshooting procedure and they are unlikely to escalate your test results anywhere.. The unfortunate thing is, any good ISP will monitor their links and they will know that they are running them hot, but they will wait to the bitter, bitter end before upgrading those links, because it's expensive, the ISP market is competitive and eats at their profits..
 
WAslayer said:
It's like I said in my earlier posts, the traceroutes look fine and because of the low priority nature that most network devices place on the ICMP protocol, the latency on specific hops don't mean much..

There is no doubt that they are running their international links hot.. from 18:00 to about 00:00 every evening, most people with internet start streaming, gaming etc.. Internet usage peaks and any ISP who doesn't have enough capacity to handle this increased traffic will result in their end users seeing packet loss and slow speeds, but not necessarily higher latency..

Packet captures and TCP based traceroutes may show any issues better, but at the same time, 1st line support for any ISP will just do the scripted troubleshooting procedure and they are unlikely to escalate your test results anywhere.. The unfortunate thing is, any good ISP will monitor their links and they will know that they are running them hot, but they will wait to the bitter, bitter end before upgrading those links, because it's expensive, the ISP market is competitive and eats at their profits..
Click to expand...
i asked him about them running they're links hot and his answer was a very unconvincing 'nooooooooo; lmAO
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X