Metrofibre Latency

P

Peder

Hobbit
Joined
Oct 16, 2006
Messages
9,397
Reaction score
64
Location
Pretoria South Africa
Do you guys maybe know if there is an issue on the metrofibre network?

Sometimes its like any google site takes a long time to resolve, so i'll sit and wait for about 3secs and then the page will suddenly start loading, it won't load immediately.

Anyone maybe got an idea what I can do? I tried adjusting the DNS settings to no avail.
 
Is this for the MetroFibre FNO or ISP or both because on MetroFibre FNO with Afrihost in Centurion things seems fine?
 
I am with Metrofibre as ISP and FNO. Also in Centurion, but since about 2-3 weeks ago I am having issues.

Even mybroadband now took a few moments to start loading.
 
Peder said:
I am with Metrofibre as ISP and FNO. Also in Centurion, but since about 2-3 weeks ago I am having issues.

Even mybroadband now took a few moments to start loading.
Click to expand...

This sounds like Cloudflare.

What does your traceroute to mybroadband.co.za look like?

Cloudflare has been redirecting JHB intermittently the last couple of weeks.
 
Here is Mybroadband and Google.

Google took ages to do hop 6,7,8

Code: 
traceroute to mybroadband.co.za (104.22.46.73), 30 hops max, 60 byte packets
 1  _gateway (192.168.1.1)  3.087 ms  5.513 ms  5.633 ms
 2  196.50.234.65 (196.50.234.65)  10.806 ms  10.899 ms  11.357 ms
 3  102.33.30.237 (102.33.30.237)  11.428 ms  11.414 ms  11.401 ms
 4  196.50.234.42 (196.50.234.42)  12.082 ms 196.50.234.38 (196.50.234.38)  12.605 ms 196.50.234.54 (196.50.234.54)  12.006 ms
 5  196.50.234.97 (196.50.234.97)  17.523 ms 196.50.234.62 (196.50.234.62)  12.629 ms  13.240 ms
 6  ae-2-37.er-02-jnb.za.seacomnet.com (105.22.40.25)  13.427 ms  5.478 ms  10.583 ms
 7  ae-1.cr-02-jnb.za.seacomnet.com (105.16.29.2)  24.328 ms ae-0.cr-02-jnb.za.seacomnet.com (105.16.28.2)  23.330 ms ae-1.cr-02-jnb.za.seacomnet.com (105.16.29.2)  24.303 ms
 8  * ae-0.cr-01-jnb.za.seacomnet.com (105.16.28.1)  24.281 ms ce-0-1-4.cr-02-cpt.za.seacomnet.com (105.16.14.194)  25.938 ms
 9  ce-0-1-4.cr-02-cpt.za.seacomnet.com (105.16.14.194)  25.925 ms ce-0-0-5.cr-01-cpt.za.seacomnet.com (105.25.160.210)  26.659 ms ce-0-1-4.cr-01-cpt.za.seacomnet.com (105.16.15.250)  26.648 ms
10  ce-0-0-0.pp-01-cpt.za.seacomnet.com (105.16.30.8)  26.926 ms cloudflare.cinx.net.za (196.223.22.109)  29.181 ms ce-0-0-1.pp-01-cpt.za.seacomnet.com (105.16.31.8)  26.903 ms
11  cloudflare.cinx.net.za (196.223.22.109)  29.386 ms cloudflare.ixp.capetown (196.60.70.198)  27.794 ms cloudflare.cinx.net.za (196.223.22.109)  30.472 ms
12  104.22.46.73 (104.22.46.73)  22.853 ms  23.082 ms  22.750 ms

Code: 
traceroute to google.com (142.251.47.206), 30 hops max, 60 byte packets
 1  _gateway (192.168.1.1)  3.752 ms  3.949 ms  3.929 ms
 2  196.50.234.65 (196.50.234.65)  7.198 ms  7.274 ms  7.542 ms
 3  102.33.30.237 (102.33.30.237)  7.655 ms  7.638 ms  7.621 ms
 4  196.50.234.54 (196.50.234.54)  8.565 ms 196.50.234.13 (196.50.234.13)  8.685 ms  9.082 ms
 5  196.50.234.97 (196.50.234.97)  8.855 ms 196.50.234.62 (196.50.234.62)  9.064 ms  9.048 ms
 6  72.14.205.226 (72.14.205.226)  12.634 ms  7.969 ms *
 7  * * *
 8  * 172.253.73.104 (172.253.73.104)  5.489 ms  6.823 ms
 9  74.125.245.212 (74.125.245.212)  8.122 ms 74.125.245.210 (74.125.245.210)  7.328 ms 74.125.245.198 (74.125.245.198)  6.787 ms
10  142.251.200.65 (142.251.200.65)  8.258 ms 142.251.200.49 (142.251.200.49)  9.482 ms  9.487 ms
11  192.178.73.133 (192.178.73.133)  8.846 ms 192.178.73.131 (192.178.73.131)  6.826 ms 192.178.73.133 (192.178.73.133)  7.032 ms
12  jnb03s11-in-f14.1e100.net (142.251.47.206)  6.349 ms  7.572 ms  7.575 ms
 
Peder said:
Here is Mybroadband and Google.

Google took ages to do hop 6,7,8

Code: 
traceroute to mybroadband.co.za (104.22.46.73), 30 hops max, 60 byte packets
 1  _gateway (192.168.1.1)  3.087 ms  5.513 ms  5.633 ms
 2  196.50.234.65 (196.50.234.65)  10.806 ms  10.899 ms  11.357 ms
 3  102.33.30.237 (102.33.30.237)  11.428 ms  11.414 ms  11.401 ms
 4  196.50.234.42 (196.50.234.42)  12.082 ms 196.50.234.38 (196.50.234.38)  12.605 ms 196.50.234.54 (196.50.234.54)  12.006 ms
 5  196.50.234.97 (196.50.234.97)  17.523 ms 196.50.234.62 (196.50.234.62)  12.629 ms  13.240 ms
 6  ae-2-37.er-02-jnb.za.seacomnet.com (105.22.40.25)  13.427 ms  5.478 ms  10.583 ms
 7  ae-1.cr-02-jnb.za.seacomnet.com (105.16.29.2)  24.328 ms ae-0.cr-02-jnb.za.seacomnet.com (105.16.28.2)  23.330 ms ae-1.cr-02-jnb.za.seacomnet.com (105.16.29.2)  24.303 ms
 8  * ae-0.cr-01-jnb.za.seacomnet.com (105.16.28.1)  24.281 ms ce-0-1-4.cr-02-cpt.za.seacomnet.com (105.16.14.194)  25.938 ms
 9  ce-0-1-4.cr-02-cpt.za.seacomnet.com (105.16.14.194)  25.925 ms ce-0-0-5.cr-01-cpt.za.seacomnet.com (105.25.160.210)  26.659 ms ce-0-1-4.cr-01-cpt.za.seacomnet.com (105.16.15.250)  26.648 ms
10  ce-0-0-0.pp-01-cpt.za.seacomnet.com (105.16.30.8)  26.926 ms cloudflare.cinx.net.za (196.223.22.109)  29.181 ms ce-0-0-1.pp-01-cpt.za.seacomnet.com (105.16.31.8)  26.903 ms
11  cloudflare.cinx.net.za (196.223.22.109)  29.386 ms cloudflare.ixp.capetown (196.60.70.198)  27.794 ms cloudflare.cinx.net.za (196.223.22.109)  30.472 ms
12  104.22.46.73 (104.22.46.73)  22.853 ms  23.082 ms  22.750 ms

Code: 
traceroute to google.com (142.251.47.206), 30 hops max, 60 byte packets
 1  _gateway (192.168.1.1)  3.752 ms  3.949 ms  3.929 ms
 2  196.50.234.65 (196.50.234.65)  7.198 ms  7.274 ms  7.542 ms
 3  102.33.30.237 (102.33.30.237)  7.655 ms  7.638 ms  7.621 ms
 4  196.50.234.54 (196.50.234.54)  8.565 ms 196.50.234.13 (196.50.234.13)  8.685 ms  9.082 ms
 5  196.50.234.97 (196.50.234.97)  8.855 ms 196.50.234.62 (196.50.234.62)  9.064 ms  9.048 ms
 6  72.14.205.226 (72.14.205.226)  12.634 ms  7.969 ms *
 7  * * *
 8  * 172.253.73.104 (172.253.73.104)  5.489 ms  6.823 ms
 9  74.125.245.212 (74.125.245.212)  8.122 ms 74.125.245.210 (74.125.245.210)  7.328 ms 74.125.245.198 (74.125.245.198)  6.787 ms
10  142.251.200.65 (142.251.200.65)  8.258 ms 142.251.200.49 (142.251.200.49)  9.482 ms  9.487 ms
11  192.178.73.133 (192.178.73.133)  8.846 ms 192.178.73.131 (192.178.73.131)  6.826 ms 192.178.73.133 (192.178.73.133)  7.032 ms
12  jnb03s11-in-f14.1e100.net (142.251.47.206)  6.349 ms  7.572 ms  7.575 ms
Click to expand...

This looks like it's over wifi as your latency to the router/ont is higher than expected. Overall the trace route looks fine no underlying issue on their network. Interersting MetroFibre decides to reach Cloudflare over transit in CPT but that is not the issue.

I think wifi is the issue to be honest.
 
cavedog said:
This looks like it's over wifi as your latency to the router/ont is higher than expected. Overall the trace route looks fine no underlying issue on their network. Interersting MetroFibre decides to reach Cloudflare over transit in CPT but that is not the issue.

I think wifi is the issue to be honest.I
Click to expand...
I have tried to change DNS settings too. But I'll hook it straight on to LAN and see whats going on. What is strange for me is its specifically google websites that do this, and not easily other websites.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X