Packet loss and International Bandwith at night

Ultrafy

Member
Joined
Nov 4, 2018
Messages
13
Hi guys im with cell c 100mb fibre and openserve as my fibre line holder .... ive been having packet loss internationally and very low bandwith to overseas at night for a month now .... here ill be posting a few traceroutes and stuff ... can someone please give me advice and please look at these traceroutes and see if they see something fishy

traceroute to news.com [ take a look at the ping to cape town seacom] i live in pretoria btw.

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.

traceroute to amazon web server in europe , one i use to play fortnite to


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:

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.


Traceroute to seacom capetown

C:\Users\User-PC>tracert 105.16.8.226

Tracing route to xe-0-0-0-2.cr-01-cpt.za.seacomnet.com [105.16.8.226]
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 4 ms 5 ms 41.50.1.89
4 21 ms 18 ms 20 ms 41.50.1.90
5 43 ms 42 ms 36 ms 41.50.12.66
6 13 ms 11 ms 7 ms ae-2-93.er-01-jnb.za.seacomnet.com [105.22.32.149]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
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.
 
Top