No, nothing noticeable, they are performing the same.
OK cool, at least that rules out a few things.
Do you see better performance for Flickr in particular on different networks?
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
No, nothing noticeable, they are performing the same.
Awesome news dude, seemed like the slower sync did the trick![]()
OK cool, at least that rules out a few things.
Do you see better performance for Flickr in particular on different networks?
C:\Users\User>tracert flickr.com
Tracing route to flickr.com [69.147.76.173]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Billion.400G [10.0.0.2]
2 8 ms 8 ms 9 ms 196-210-136-129.dynamic.isadsl.co.za [196.210.13
6.129]
3 10 ms 10 ms 9 ms 196.38.73.85
4 9 ms 9 ms 10 ms cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
5 13 ms 14 ms 13 ms core2b-pkl-te0-0-0-0.ip.isnet.net [196.26.0.63]
6 190 ms 190 ms 189 ms 168.209.201.85
7 209 ms 202 ms 192 ms 168.209.246.65
8 186 ms 181 ms 179 ms ge-1-1-0.pat1.the.yahoo.com [195.66.224.129]
9 288 ms 280 ms 271 ms so-0-1-0.pat2.nyc.yahoo.com [216.115.96.30]
10 * 270 ms 274 ms ae-2.pat2.bfz.yahoo.com [216.115.100.74]
11 296 ms 277 ms 301 ms ae-3.msr2.bf1.yahoo.com [216.115.100.31]
12 284 ms 275 ms 283 ms xe-11-0-1.clr1-a-gdc.bf1.yahoo.com [98.139.129.1
71]
13 274 ms 273 ms 287 ms et-17-1.fab1-1-gdc.bf1.yahoo.com [98.139.128.37]
14 290 ms * 317 ms po-12.bas1-10-prd.bf1.yahoo.com [69.147.72.135]
15 284 ms 279 ms 289 ms fts.flickr.vip.bf1.yahoo.com [69.147.76.173]
Trace complete.
C:\Users\User>
Was better early this morning on Webafrica, now the photos load about the same, slow.
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
Code:C:\Users\User>tracert flickr.com Tracing route to flickr.com [69.147.76.173] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms Billion.400G [10.0.0.2] 2 8 ms 8 ms 9 ms 196-210-136-129.dynamic.isadsl.co.za [196.210.13 6.129] 3 10 ms 10 ms 9 ms 196.38.73.85 4 9 ms 9 ms 10 ms cdsl2-rba-vl150.ip.isnet.net [196.38.73.9] 5 13 ms 14 ms 13 ms core2b-pkl-te0-0-0-0.ip.isnet.net [196.26.0.63] 6 190 ms 190 ms 189 ms 168.209.201.85 7 209 ms 202 ms 192 ms 168.209.246.65 8 186 ms 181 ms 179 ms ge-1-1-0.pat1.the.yahoo.com [195.66.224.129] 9 288 ms 280 ms 271 ms so-0-1-0.pat2.nyc.yahoo.com [216.115.96.30] 10 * 270 ms 274 ms ae-2.pat2.bfz.yahoo.com [216.115.100.74] 11 296 ms 277 ms 301 ms ae-3.msr2.bf1.yahoo.com [216.115.100.31] 12 284 ms 275 ms 283 ms xe-11-0-1.clr1-a-gdc.bf1.yahoo.com [98.139.129.1 71] 13 274 ms 273 ms 287 ms et-17-1.fab1-1-gdc.bf1.yahoo.com [98.139.128.37] 14 290 ms * 317 ms po-12.bas1-10-prd.bf1.yahoo.com [69.147.72.135] 15 284 ms 279 ms 289 ms fts.flickr.vip.bf1.yahoo.com [69.147.76.173] Trace complete. C:\Users\User>
Have you tried Googles DNS servers to see if this makes any difference at all?
No difference.
I have cleared the browser cache and cookies and everything now, logged back in, viewed photos with Webafrica, it loads nicely. Changed over the Afrihost, reset the browser again, viewed the same photos, it takes long to load, not even all images showed. Back to WebAfrica, reset browser, the same photos, loads nicely, less than a minute. Back to AH again, reset browser, photos load slow, until now, some not even displaying.
Thanks, I'll take a look at this ASAP!
Any feedback yet Afriguy?
Waiting for feedback here too...
Whats going on? how far you guys from resolving out issues ?
No finalised feedback yet, our team will be in touch with you personally once there's some feedback.
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)
Pinging 105.236.9.1 with 32 bytes of data:
Reply from 105.236.9.1: bytes=32 time=23ms TTL=254
Reply from 105.236.9.1: bytes=32 time=23ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Request timed out.
Reply from 105.236.9.1: bytes=32 time=20ms TTL=254
Reply from 105.236.9.1: bytes=32 time=23ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=20ms TTL=254
Reply from 105.236.9.1: bytes=32 time=20ms TTL=254
Reply from 105.236.9.1: bytes=32 time=23ms TTL=254
Reply from 105.236.9.1: bytes=32 time=20ms TTL=254
Reply from 105.236.9.1: bytes=32 time=20ms TTL=254
Reply from 105.236.9.1: bytes=32 time=22ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=33ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=20ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=22ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Ping statistics for 105.236.9.1:
Packets: Sent = 30, Received = 29, Lost = 1 (3% loss),
Approximate round trip times in milli-seconds:
Minimum = 20ms, Maximum = 33ms, Average = 21ms
06/11/2014 15:00:30.59
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)
Pinging 41.133.136.1 with 32 bytes of data:
Reply from 41.133.136.1: bytes=32 time=20ms TTL=254
Reply from 41.133.136.1: bytes=32 time=20ms TTL=254
Reply from 41.133.136.1: bytes=32 time=20ms TTL=254
Reply from 41.133.136.1: bytes=32 time=21ms TTL=254
Reply from 41.133.136.1: bytes=32 time=19ms TTL=254
Reply from 41.133.136.1: bytes=32 time=20ms TTL=254
Reply from 41.133.136.1: bytes=32 time=22ms TTL=254
Reply from 41.133.136.1: bytes=32 time=21ms TTL=254
Reply from 41.133.136.1: bytes=32 time=24ms TTL=254
Reply from 41.133.136.1: bytes=32 time=19ms TTL=254
Reply from 41.133.136.1: bytes=32 time=26ms TTL=254
Reply from 41.133.136.1: bytes=32 time=21ms TTL=254
Reply from 41.133.136.1: bytes=32 time=20ms TTL=254
Reply from 41.133.136.1: bytes=32 time=20ms TTL=254
Reply from 41.133.136.1: bytes=32 time=20ms TTL=254
Reply from 41.133.136.1: bytes=32 time=20ms TTL=254
Reply from 41.133.136.1: bytes=32 time=33ms TTL=254
Reply from 41.133.136.1: bytes=32 time=19ms TTL=254
Reply from 41.133.136.1: bytes=32 time=29ms TTL=254
Reply from 41.133.136.1: bytes=32 time=22ms TTL=254
Reply from 41.133.136.1: bytes=32 time=20ms TTL=254
Reply from 41.133.136.1: bytes=32 time=20ms TTL=254
Reply from 41.133.136.1: bytes=32 time=21ms TTL=254
Reply from 41.133.136.1: bytes=32 time=20ms TTL=254
Reply from 41.133.136.1: bytes=32 time=20ms TTL=254
Reply from 41.133.136.1: bytes=32 time=21ms TTL=254
Reply from 41.133.136.1: bytes=32 time=20ms TTL=254
Reply from 41.133.136.1: bytes=32 time=23ms TTL=254
Reply from 41.133.136.1: bytes=32 time=20ms TTL=254
Reply from 41.133.136.1: bytes=32 time=21ms TTL=254
Ping statistics for 41.133.136.1:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 33ms, Average = 21ms
06/11/2014 15:28:12.98
I am waiting... its just taking so long...
Hi
So sorry for the inconvenience caused.
Seems like your email went to our support department.
Right now, we are still awaiting for feedback, regarding the performance on our Business Accounts.
I will revert back to you, once I have solid feedback.
I apologize once again, for the delays.
Thanks
Critical Care
I am waiting... its just taking so long...
Hi
So sorry for the inconvenience caused.
Seems like your email went to our support department.
Right now, we are still awaiting for feedback, regarding the performance on our Business Accounts.
I will revert back to you, once I have solid feedback.
I apologize once again, for the delays.
Thanks
Critical Care
Afriguy, I did some tests on my AH 4 mbps business account and a MWeb 4 mbps trial account.
Here are the results:
AH 4mbps Business:
Zertop's "Is it my Line" Results
Basic Report:
Your average ping was 21ms
Your maximum ping was 33ms
Looking at your average ping, your line seems to be running perfectly![]()
Looking at your maximum ping, however, it seems as though there could be a slight intermittant issue on the line. If required, please post the results to a forum post.
Detailed Report
Code:Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) Pinging 105.236.9.1 with 32 bytes of data: Reply from 105.236.9.1: bytes=32 time=23ms TTL=254 Reply from 105.236.9.1: bytes=32 time=23ms TTL=254 Reply from 105.236.9.1: bytes=32 time=21ms TTL=254 Reply from 105.236.9.1: bytes=32 time=21ms TTL=254 Reply from 105.236.9.1: bytes=32 time=21ms TTL=254 Reply from 105.236.9.1: bytes=32 time=21ms TTL=254 Request timed out. Reply from 105.236.9.1: bytes=32 time=20ms TTL=254 Reply from 105.236.9.1: bytes=32 time=23ms TTL=254 Reply from 105.236.9.1: bytes=32 time=21ms TTL=254 Reply from 105.236.9.1: bytes=32 time=20ms TTL=254 Reply from 105.236.9.1: bytes=32 time=20ms TTL=254 Reply from 105.236.9.1: bytes=32 time=23ms TTL=254 Reply from 105.236.9.1: bytes=32 time=20ms TTL=254 Reply from 105.236.9.1: bytes=32 time=20ms TTL=254 Reply from 105.236.9.1: bytes=32 time=22ms TTL=254 Reply from 105.236.9.1: bytes=32 time=21ms TTL=254 Reply from 105.236.9.1: bytes=32 time=21ms TTL=254 Reply from 105.236.9.1: bytes=32 time=21ms TTL=254 Reply from 105.236.9.1: bytes=32 time=33ms TTL=254 Reply from 105.236.9.1: bytes=32 time=21ms TTL=254 Reply from 105.236.9.1: bytes=32 time=21ms TTL=254 Reply from 105.236.9.1: bytes=32 time=20ms TTL=254 Reply from 105.236.9.1: bytes=32 time=21ms TTL=254 Reply from 105.236.9.1: bytes=32 time=21ms TTL=254 Reply from 105.236.9.1: bytes=32 time=21ms TTL=254 Reply from 105.236.9.1: bytes=32 time=21ms TTL=254 Reply from 105.236.9.1: bytes=32 time=21ms TTL=254 Reply from 105.236.9.1: bytes=32 time=22ms TTL=254 Reply from 105.236.9.1: bytes=32 time=21ms TTL=254 Ping statistics for 105.236.9.1: Packets: Sent = 30, Received = 29, Lost = 1 (3% loss), Approximate round trip times in milli-seconds: Minimum = 20ms, Maximum = 33ms, Average = 21ms 06/11/2014 15:00:30.59
Local Tracert
Tracing route to news24.co.za [41.86.110.143]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 18 ms 19 ms 19 ms 105-236-9-1-esr-lo.mtnbusiness.co.za [105.236.9.1]
3 46 ms 24 ms 66 ms ipc-recieve-rb-1a.za.mtnbusiness.net [41.181.178.53]
4 31 ms 24 ms 20 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 22 ms 21 ms 21 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
6 21 ms 21 ms 62 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 21 ms 21 ms 22 ms 196.44.0.72
8 51 ms 24 ms 24 ms postfix.wipronet.co.za [196.22.161.133]
9 48 ms 51 ms 52 ms tengig-0-7-0-3-vic-p-2.mweb.co.za [197.80.7.98]
10 51 ms 52 ms 59 ms tengig-0-0-0-0-cpt-p-1.mweb.co.za [197.84.4.34]
11 50 ms 48 ms 50 ms vl-12-cpt-hscore-2.mweb.co.za [197.84.5.254]
12 68 ms 96 ms 44 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
13 46 ms 45 ms 60 ms gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166]
14 57 ms 47 ms 46 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
15 45 ms 43 ms 44 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
16 43 ms 48 ms 44 ms 41-86-110-143.mweb.co.za [41.86.110.143]
Trace complete.
International Tracert
Tracing route to thinkbroadband.com [80.249.99.130]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 17 ms 17 ms 18 ms 105-236-9-1-esr-lo.mtnbusiness.co.za [105.236.9.1]
3 25 ms 26 ms 59 ms ipc-recieve-rb-4a.za.mtnbusiness.net [41.181.178.89]
4 32 ms 22 ms 22 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 23 ms 21 ms 21 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
6 24 ms 24 ms 22 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 226 ms 234 ms 223 ms ls-cr-2.uk--rb-cr-1.za-g.mtnns.net [196.44.31.114]
8 225 ms 247 ms 262 ms ls-cr-1.uk--ls-cr-2.uk-a.mtnns.net [196.44.31.156]
9 204 ms 204 ms 212 ms ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83]
10 203 ms 222 ms 207 ms linx-gw1.thn.ncuk.net [195.66.224.240]
11 219 ms 218 ms 219 ms te2-1-9.star10g.bdr-rt3.thdo.ncuk.net [80.249.97.17]
12 212 ms 230 ms 213 ms te1-1-1-31.core-rs2.thdo.ncuk.net [80.249.97.85]
13 204 ms 202 ms 203 ms www.thinkbroadband.com [80.249.99.130]
Trace complete.
International Speedtest
Downloaded 20.0 megabytes in 3:07 seconds. (109.25 KB/s)
Local Speedtest
Downloaded 15.6 megabytes in 1:25 seconds. (187.13 KB/s)
Test End Timestamp
06/11/2014 15:07:34.15
4mbps MWeb Test account:
Mweb 4mbps trial account wired:
Diagnostics Tool
Local Tracert
Tracing route to news24.co.za [41.86.110.143]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 18 ms 18 ms 18 ms 41-133-136-1.dsl.mweb.co.za [41.133.136.1]
3 19 ms 20 ms 20 ms 197-80-96-138.jhb.mweb.co.za [197.80.96.138]
4 20 ms 20 ms 20 ms vl-92-vic-hscore-2.mweb.co.za [197.80.2.2]
5 47 ms 49 ms 47 ms tengig-0-7-0-2-12-vic-p-2.mweb.co.za [197.80.5.242]
6 44 ms 43 ms 43 ms tengig-0-0-0-0-cpt-p-1.mweb.co.za [197.84.4.34]
7 44 ms 45 ms 44 ms vl-11-cpt-hscore-1.mweb.co.za [197.84.5.238]
8 50 ms 129 ms 46 ms 196.28.178.66
9 42 ms 42 ms 40 ms gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234]
10 45 ms 46 ms 46 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
11 44 ms 45 ms 46 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
12 40 ms 41 ms 40 ms 41-86-110-143.mweb.co.za [41.86.110.143]
Trace complete.
International Tracert
Tracing route to thinkbroadband.com [80.249.99.130]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 18 ms 19 ms 21 ms 41-133-136-1.dsl.mweb.co.za [41.133.136.1]
3 20 ms 20 ms 20 ms 197-80-96-138.jhb.mweb.co.za [197.80.96.138]
4 20 ms 20 ms 20 ms vl-92-vic-hscore-2.mweb.co.za [197.80.2.2]
5 204 ms 204 ms 207 ms tengig-0-7-0-2-12-vic-p-1.mweb.co.za [197.80.5.241]
6 204 ms 203 ms 204 ms s2-pos0-3-0-0-pos0-3-2-0-thd-p-2.mweb.co.za [197.80.5.7]
7 227 ms 212 ms 208 ms be-2-778-thd-up-2.mweb.co.za [176.67.177.148]
8 203 ms 199 ms 202 ms be-16-776-thd-linx-1.mweb.co.za [176.67.177.236]
9 202 ms 201 ms 198 ms linx-gw2.thdo.ncuk.net [195.66.236.240]
10 202 ms 210 ms 203 ms te1-1-1-31.core-rs2.thdo.ncuk.net [80.249.97.85]
11 202 ms 206 ms 204 ms www.thinkbroadband.com [80.249.99.130]
Trace complete.
International Speedtest
Downloaded 20.0 megabytes in 1:19 seconds. (257.01 KB/s)
Local Speedtest
Downloaded 15.6 megabytes in 1:04 seconds. (248.16 KB/s)
Test End Timestamp
06/11/2014 15:26:37.35
Line Tool:
Zertop's "Is it my Line" Results
Basic Report:
Your average ping was 21ms
Your maximum ping was 33ms
Looking at your average ping, your line seems to be running perfectly![]()
Looking at your maximum ping, however, it seems as though there could be a slight intermittant issue on the line. If required, please post the results to a forum post.
Detailed Report
Code:Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) Pinging 41.133.136.1 with 32 bytes of data: Reply from 41.133.136.1: bytes=32 time=20ms TTL=254 Reply from 41.133.136.1: bytes=32 time=20ms TTL=254 Reply from 41.133.136.1: bytes=32 time=20ms TTL=254 Reply from 41.133.136.1: bytes=32 time=21ms TTL=254 Reply from 41.133.136.1: bytes=32 time=19ms TTL=254 Reply from 41.133.136.1: bytes=32 time=20ms TTL=254 Reply from 41.133.136.1: bytes=32 time=22ms TTL=254 Reply from 41.133.136.1: bytes=32 time=21ms TTL=254 Reply from 41.133.136.1: bytes=32 time=24ms TTL=254 Reply from 41.133.136.1: bytes=32 time=19ms TTL=254 Reply from 41.133.136.1: bytes=32 time=26ms TTL=254 Reply from 41.133.136.1: bytes=32 time=21ms TTL=254 Reply from 41.133.136.1: bytes=32 time=20ms TTL=254 Reply from 41.133.136.1: bytes=32 time=20ms TTL=254 Reply from 41.133.136.1: bytes=32 time=20ms TTL=254 Reply from 41.133.136.1: bytes=32 time=20ms TTL=254 Reply from 41.133.136.1: bytes=32 time=33ms TTL=254 Reply from 41.133.136.1: bytes=32 time=19ms TTL=254 Reply from 41.133.136.1: bytes=32 time=29ms TTL=254 Reply from 41.133.136.1: bytes=32 time=22ms TTL=254 Reply from 41.133.136.1: bytes=32 time=20ms TTL=254 Reply from 41.133.136.1: bytes=32 time=20ms TTL=254 Reply from 41.133.136.1: bytes=32 time=21ms TTL=254 Reply from 41.133.136.1: bytes=32 time=20ms TTL=254 Reply from 41.133.136.1: bytes=32 time=20ms TTL=254 Reply from 41.133.136.1: bytes=32 time=21ms TTL=254 Reply from 41.133.136.1: bytes=32 time=20ms TTL=254 Reply from 41.133.136.1: bytes=32 time=23ms TTL=254 Reply from 41.133.136.1: bytes=32 time=20ms TTL=254 Reply from 41.133.136.1: bytes=32 time=21ms TTL=254 Ping statistics for 41.133.136.1: Packets: Sent = 30, Received = 30, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 19ms, Maximum = 33ms, Average = 21ms 06/11/2014 15:28:12.98
Sending these results to Donovan at Critical Care.
Thanks, will follow this up with Donovan too.
Is there still an issue with business accounts?
My download speeds have been horrific today. Dropping as low as 20kbps on 6mb line