Here is a tracert of the packet from here to your RA:
The packets start to get dropped when they reach SA, especially when it gets to your router.Tracing route to xxxxxxx [197.228.xxx.xxx]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 69.198.171.165
2 4 ms 5 ms 4 ms 172.28.141.148
3 6 ms * 6 ms 192.168.67.94
4 6 ms 6 ms 6 ms 209.49.249.93
5 26 ms 7 ms 7 ms ae1d0.mcr1.fremont-ca.us.xo.net [216.156.1.69]
6 12 ms 10 ms 11 ms vb1500.rar3.sanjose-ca.us.xo.net [216.156.0.137]
7 7 ms 7 ms 7 ms 207.88.14.226.ptr.us.xo.net [207.88.14.226]
8 7 ms 7 ms 7 ms 129.250.9.65
9 8 ms 7 ms 7 ms 129.250.5.52
10 81 ms 79 ms 79 ms 129.250.4.102
11 171 ms * 162 ms 129.250.2.145
12 164 ms 170 ms 163 ms 129.250.2.159
13 167 ms 166 ms 166 ms 81.20.67.226
14 372 ms 374 ms 372 ms tpr-ip-esr-6-pos-6-0-0.telkom-ipnet.co.za [196.43.26.46]
15 377 ms 370 ms 377 ms telkom-sa-mcnet-gw.telkom-ipnet.co.za [196.25.49.74]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 2206 ms 594 ms 539 ms 8ta-228-32-06.telkomadsl.co.za [197.228.xxx.xxx]
Trace complete.
I've seen this happening once in the past and it was related to 3G router connection.
The person was in Thailand, not SA though, but I think it is the same problem.
I think in his case, he confirmed the connection problem when he took his RA to someone's house and used a different internet provider and things started working.