Random latency/ping issue - CPT

I'm not sure if this only affects Cape Town, but for the last month or two I've noticed that pings to anywhere local (adds to international too) outside of the iBurst network are around 200ms+, instead of the "usual" 60-100ms.

This happens mostly during the day, but at anytime it can get this high, up to 350ms, it makes quite a bit of lag gaming and in general.

Eg:
Telkom:
Pinging saix.net [196.25.1.200] with 32 bytes of data:

Reply from 196.25.1.200: bytes=32 time=202ms TTL=249
Reply from 196.25.1.200: bytes=32 time=211ms TTL=249
Reply from 196.25.1.200: bytes=32 time=232ms TTL=249
Reply from 196.25.1.200: bytes=32 time=182ms TTL=249

Ping statistics for 196.25.1.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 182ms, Maximum = 232ms, Average = 206ms

iBurst DNS:
Pinging 196.46.70.1 with 32 bytes of data:

Reply from 196.46.70.1: bytes=32 time=65ms TTL=252
Reply from 196.46.70.1: bytes=32 time=64ms TTL=252
Reply from 196.46.70.1: bytes=32 time=63ms TTL=252
Reply from 196.46.70.1: bytes=32 time=68ms TTL=252

Ping statistics for 196.46.70.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 63ms, Maximum = 68ms, Average = 65ms

This will reflect on almost any local and international websites.

This never used to happen, and it will still stay within the normal ranges some of the time. Is everyone else experiencing this?

That's quite good compared to mine. Intl are all over 300ms.

Pinging google.com [64.233.183.147] with 32 bytes of data:

Reply from 64.233.183.147: bytes=32 time=302ms TTL=239
Reply from 64.233.183.147: bytes=32 time=301ms TTL=239
Reply from 64.233.183.147: bytes=32 time=491ms TTL=239
Reply from 64.233.183.147: bytes=32 time=339ms TTL=239

Ping statistics for 64.233.183.147:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 301ms, Maximum = 491ms, Average = 358ms

---------------------------------------------------------

Pinging iburst.co.za [196.30.31.120] with 32 bytes of data:

Reply from 196.30.31.120: bytes=32 time=136ms TTL=125
Reply from 196.30.31.120: bytes=32 time=146ms TTL=125
Reply from 196.30.31.120: bytes=32 time=124ms TTL=125
Reply from 196.30.31.120: bytes=32 time=207ms TTL=125

Ping statistics for 196.30.31.120:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 124ms, Maximum = 207ms, Average = 153ms

No, well those saix.net pings are local, when it's working as it should they are around 70ms. International is usually +-500ms when this problem is happening, instead of the 300ms you normally get.

In that case, Saix.net is not too bad over here.

Pinging saix.net [196.25.1.200] with 32 bytes of data:

Reply from 196.25.1.200: bytes=32 time=153ms TTL=245
Reply from 196.25.1.200: bytes=32 time=122ms TTL=245
Reply from 196.25.1.200: bytes=32 time=134ms TTL=245
Reply from 196.25.1.200: bytes=32 time=154ms TTL=245

Ping statistics for 196.25.1.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 122ms, Maximum = 154ms, Average = 140ms