There is a great difference between slow and non existent. I tried to make it as clear as possible that it's Android updates that does not work at all. I regard 400Kb in 10min as not working, not slow. So not a general download, but rather a specific service (Play Store).
During that time I can do a speed test at almost full speed.
Latency are much better last night, compared to the last couple of weeks with your peering issues. I still get weird routing to your and mybroadband site every now and then.
This was 8:45am this morning
Code:
Tracing route to www.afrihost.com [104.20.30.244]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.1.0.254
2 * * * Request timed out.
3 9 ms 8 ms 7 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
4 8 ms 7 ms 7 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
5 8 ms 7 ms 8 ms 41.164.52.40
6 8 ms 10 ms 20 ms if-ae-7-0.tcore2.KLT-Cape-Town.as6453.net [41.206.165.25]
7 167 ms 164 ms 163 ms if-ae-2-2.tcore1.KLT-Cape-Town.as6453.net [41.206.164.253]
8 157 ms 157 ms 157 ms if-ae-5-20.tcore2.PV9-Lisbon.as6453.net [80.231.159.61]
9 154 ms 154 ms 155 ms if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
10 155 ms 160 ms 153 ms if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
11 151 ms 150 ms 155 ms if-ae-19-2.tcore2.L78-London.as6453.net [80.231.138.22]
12 150 ms 150 ms 150 ms if-ae-15-2.tcore2.LDN-London.as6453.net [80.231.131.118]
13 162 ms 163 ms 164 ms 80.231.20.66
14 162 ms 162 ms 162 ms 104.20.30.244
Trace complete.
You'll notice it's going overseas and then back. This has happened before in the last couple of weeks, but only during the hours of 20h - 23h. I'll PM you my massive trace rout spreadsheet as input for your peering work.
In browser and Outlook Office 365, specifically emails, were dead. Not slow, but rather unable to establish a connection at all. This has happened two nights in a row now. Pinging portal.microsoftonline.com just timed out.
During this Android and Office 365 issue when I connect to a Telkom account everything works 100%. When I switch back to Afrihost it's broken immediately not only after connected for a while.
I can't help but make the connection back to the MWEB peering issues you guys have been having. When I do android updates the established connection point here: 197-84-135-14.cpt.mweb.co.za.