Afrihost New Network Feedback - Part 2

Status
Not open for further replies.
Our cache was only recently brought online, so some of the more popular content may still reside on Mweb while our cache "fills up". Just a guess though, I'll ask the experts.

When I browse Facebook, the following server is not reachable:

scontent.fgcj1-1.fna.fbcdn.net

$ ping scontent.fgcj1-1.fna.fbcdn.net
PING scontent.fgcj1-1.fna.fbcdn.net (41.169.98.17): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
^C
--- scontent.fgcj1-1.fna.fbcdn.net ping statistics ---
4 packets transmitted, 0 packets received, 100.0% packet loss


$ traceroute scontent.fgcj1-1.fna.fbcdn.net
traceroute to scontent.fgcj1-1.fna.fbcdn.net (41.169.98.17), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 4.918 ms 4.912 ms 5.255 ms
2 * * *
3 cpt-up1.ip.adsl.co.za (169.1.5.105) 52.032 ms 49.635 ms 49.824 ms
4 cpt-in1.ip.adsl.co.za (169.1.5.118) 53.784 ms 48.448 ms 49.924 ms
5 cpt-net1.ip.adsl.co.za (169.1.5.128) 61.627 ms 57.573 ms 56.487 ms
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *


41.169.98.17 is a neotel IP
 
When I browse Facebook, the following server is not reachable:

scontent.fgcj1-1.fna.fbcdn.net

$ ping scontent.fgcj1-1.fna.fbcdn.net
PING scontent.fgcj1-1.fna.fbcdn.net (41.169.98.17): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
^C
--- scontent.fgcj1-1.fna.fbcdn.net ping statistics ---
4 packets transmitted, 0 packets received, 100.0% packet loss


$ traceroute scontent.fgcj1-1.fna.fbcdn.net
traceroute to scontent.fgcj1-1.fna.fbcdn.net (41.169.98.17), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 4.918 ms 4.912 ms 5.255 ms
2 * * *
3 cpt-up1.ip.adsl.co.za (169.1.5.105) 52.032 ms 49.635 ms 49.824 ms
4 cpt-in1.ip.adsl.co.za (169.1.5.118) 53.784 ms 48.448 ms 49.924 ms
5 cpt-net1.ip.adsl.co.za (169.1.5.128) 61.627 ms 57.573 ms 56.487 ms
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *


41.169.98.17 is a neotel IP

Would you mind clearing your browser cache and then testing your connection to Facebook.com again please.
 
Last edited:
The Facebook image problem doesn't happy to me on PC, but on their mobile site on my phone (connected to wifi).
 
Would you mind clearing your browser cache and then test your connection to Facebook.com again please.

Cleared the cache, not loading the images still

Still trying to reach the same server scontent.fgcj1-1.fna.fbcdn.net

Instagram also having a problem with instagram.fgcj1-1.fna.fbcdn.net which resolves to 41.169.98.32
 
Marvel Heroes 2016 which also routes to USA seems fine. STO's like that each end every time I start it, doesn't matter which time of day.
Other services seems ok. Except for torrents, which speeds were all over the place last night.

:(

Would you be able to run a traceroute to the STO servers?
 
We're definitely not routing P2P traffic differently, and any shaping would only be applied to Home or Premium Uncapped when there is demand on the network. We generally test as many games as we can rigorously to ensure that we properly identify any gaming traffic to not be shaped and to receive priority on the network.

Average ping after-hours (on capped account) to a Steam server is in excess of 130ms, now that may sound good here in SA, but gamers overseas don't appreciate a gamer causing LAG on a multi-player game.

I'm just calling it as it is.

By the way the FB thing is down again, it worked for about an hour - now its back to square 1. No images loading.
 
round trip ping to fbcdn-photos-a-a.akamaihd.net from Eastern side of Cape Town is 12ms - but no images loading on FB.

Ran a IPv6 test

Your DNS server (possibly run by your ISP) appears to have no access to the IPv6 Internet, or is not configured to use it. This may in the future restrict your ability to reach IPv6-only sites.

Facebook’s current data center fabric is all IPv6 - Todd Hollmann Network Engineer at Facebook
 
Last edited:
Please don't ask people not to assist and troubleshoot with us. That is really the purpose of this forum, to work together to improve the experience on our network.

Thanks :)

My apologies, I should have worded that better. I was simply speaking from experience; where I spent over a month "troubleshooting" with you guys to no avail and in the end moving to a different ISP solved the problem.
 
round trip ping to fbcdn-photos-a-a.akamaihd.net from Eastern side of Cape Town is 12ms - but no images loading on FB.

Ran a IPv6 test

:(

Thanks for the update, I'll follow-up with our Team.
 
Tracing route to www.afrihost.com [104.20.31.244]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms login.router [10.0.0.2]
2 * * * Request timed out.
3 * * * Request timed out.
4 234 ms 292 ms 365 ms cpt-in1.ip.adsl.co.za [169.1.5.118]
5 18 ms 16 ms 15 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 20 ms 28 ms 17 ms 41.164.52.40
7 189 ms 154 ms 222 ms 172.18.1.164
8 392 ms 420 ms 437 ms cloudflare.ixp.joburg [196.46.25.198]
9 269 ms 342 ms 275 ms www.afrihost.com [104.20.31.244]



Internet been very slow today,fb images/videos doesn't show/load and international sites barely open up.

Must be those R1 leeches sucking the life out of everything..AGAIN!
 
Tracing route to www.afrihost.com [104.20.31.244]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms login.router [10.0.0.2]
2 * * * Request timed out.
3 * * * Request timed out.
4 234 ms 292 ms 365 ms cpt-in1.ip.adsl.co.za [169.1.5.118]
5 18 ms 16 ms 15 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 20 ms 28 ms 17 ms 41.164.52.40
7 189 ms 154 ms 222 ms 172.18.1.164
8 392 ms 420 ms 437 ms cloudflare.ixp.joburg [196.46.25.198]
9 269 ms 342 ms 275 ms www.afrihost.com [104.20.31.244]



Internet been very slow today,fb images/videos doesn't show/load and international sites barely open up.

Must be those R1 leeches sucking the life out of everything..AGAIN!

That should definitely not be the case. :(

What do your speedtests look like at the moment? Could you PM me your username please.
 
Cleared the cache, not loading the images still

Still trying to reach the same server scontent.fgcj1-1.fna.fbcdn.net

Instagram also having a problem with instagram.fgcj1-1.fna.fbcdn.net which resolves to 41.169.98.32

Also having the same issue, the route dies here:

traceroute to instagram.fgcj1-1.fna.fbcdn.net (41.169.98.32), 64 hops max, 52 byte packets
1 gateway6.artifactual.org.za (192.168.20.1) 0.627 ms 0.396 ms 0.486 ms
2 * * *
3 cpt-up1.ip.adsl.co.za (169.1.5.105) 93.291 ms 29.051 ms 45.634 ms
4 cpt-in1.ip.adsl.co.za (169.1.5.118) 49.850 ms 24.211 ms 23.124 ms
5 cpt-net1.ip.adsl.co.za (169.1.5.128) 24.020 ms 27.845 ms 24.887 ms
6 * * *
7 * * *


No problem accessing this IP from other networks.
 
Also having the same issue, the route dies here:

traceroute to instagram.fgcj1-1.fna.fbcdn.net (41.169.98.32), 64 hops max, 52 byte packets
1 gateway6.artifactual.org.za (192.168.20.1) 0.627 ms 0.396 ms 0.486 ms
2 * * *
3 cpt-up1.ip.adsl.co.za (169.1.5.105) 93.291 ms 29.051 ms 45.634 ms
4 cpt-in1.ip.adsl.co.za (169.1.5.118) 49.850 ms 24.211 ms 23.124 ms
5 cpt-net1.ip.adsl.co.za (169.1.5.128) 24.020 ms 27.845 ms 24.887 ms
6 * * *
7 * * *


No problem accessing this IP from other networks.

Which DNS servers is your modem pulling at the moment?
 
I am really concerned by AH support

I sent an email at 06H38 in response to my ongoing problem and followed this up in client zone at 08H03.
Edit .... neither have been answered.
There are now two technicians answering the issue ..... to boot with cut and paste responses.

I tell you this ..... I will be paying 25% of the bill because I am getting 25% of the line.

I have asked no fewer than 4 times to log a fault with Telkom ..... you have my line.

Support just couldnt be bothered to respond.

This is not on.

How or who can I escalate my frustration to.
 
I am really concerned by AH support

I sent an email at 06H38 in response to my ongoing problem and followed this up in client zone at 08H03.
Edit .... neither have been answered.
There are now two technicians answering the issue ..... to boot with cut and paste responses.

I tell you this ..... I will be paying 25% of the bill because I am getting 25% of the line.

I have asked no fewer than 4 times to log a fault with Telkom ..... you have my line.

Support just couldnt be bothered to respond.

This is not on.

How or who can I escalate my frustration to.

We logged a fault for your DSL line earlier this month, and there is pending escalation on it, we're just waiting for an update from Telkom.

In the meantime I'm going to ask our Critical Care Team to take over the resolution of this issue.
 
We logged a fault for your DSL line earlier this month, and there is pending escalation on it, we're just waiting for an update from Telkom.

In the meantime I'm going to ask our Critical Care Team to take over the resolution of this issue.

Thank you.

I have had subsequent correspondence to say that the Telkom issue is closed.

In frustration I called support 5 minutes ago.
The dude saw the fluctuation on the line and agrees that a fault be logged.
I have just had confirmation that indeed a fault has been logged ..... finally!!

Its so frustrating when I ask you to log a fault and get a cut and paste response about the router and check this and that.
Someone needs to chat to your support staff ...... really.

Sorry to harp on but dealing with support can be excellent at times and at times, its more painful than being circumcised with a rusty razor and no anesthetic.

Anyway ... thanks for your help, appreciate it.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X