Same here.
Try flushing your cache & cookies.
Nah, this is is not a browser issue, tracert suggests otherwise:
Tracing route to
www.capetown.gov.za [41.208.10.34]
over a maximum of 30 hops:
1 2 ms <1 ms <1 ms home [192.168.0.1]
2 * * * Request timed out.
3 19 ms 18 ms 18 ms wbs-ip-hsll-2-gi4-0-0-vl102.telkom-ipnet.co.za [105.226.0.21]
4 18 ms 18 ms 18 ms ipc-4-up.south.dsl.telkomsa.net [105.226.0.30]
5 19 ms 19 ms 18 ms ipc-aggr-2.south.dsl.telkomsa.net [105.226.0.57]
6 18 ms 18 ms 18 ms 196.25.190.209
7 19 ms 18 ms 19 ms 196.43.25.206
8 20 ms 19 ms 19 ms mtn-gw.telkom-ipnet.co.za [196.25.165.198]
9 19 ms 19 ms 19 ms 196.44.5.93
10 22 ms 23 ms 23 ms 196.44.29.116
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.
Trace complete.
As I have said, I have tried this from Telkom Mobile and Telkom ADSL, so this is more likely a location based routing issue. Will refer this to TelkomZA. In the meanwhile if anyone in Melkbos or near surrounds in Cape Town could test, that would be appreciated.
