Logged 2 complaints about my line speed. You have "resolved" both of them, yet my speed still goes to **** from 7pm onward
Because your line is fine.
There is a major issue effecting most telkom accounts ranging from people having 20% dropped packets to intl,400+ pings,and terrible download speeds.
This is standard practice. Pretty much every weekday. Someone broke something last month.Update on my end. At some random time in the middle of the night last night, all the insane ping timeouts just vanished. Clear 0 packet loss to anything in the US or EU, compared to 20% packet loss to anything leaving the country.
Still seems to be running good. Now to see if the pings and bandwidth end up going to poop at 7-10 even though ive used like 20gbs on a 10mb line, not even near any sort of FUP tier.
Hi streaker,
Just a quick update: I reported these two issues:
1. Packet-loss to selected International destinations
2. Packet-loss to MTN Business
Looks like each of these issues were resolved during a 9pm maintenance window. The local loss issue was resolved at exactly 9pm on the 16th of May and the intl. issue was resolved at exactly 9pm on the 15th of May.
Thanks to those who attended to the problem and solved it. It say the only negative was that it took 10 days to resolve.
--deckert
Hey, there's a problem!deckert,
Also noticed that SAIX fixed the issue on their side, still waiting on feedback.We will continue with our efforts to setup direct peering with MTN to prevent similar issues in future. That should prevent things like the 10 day turn around time.
Ah OK, I change my dns and everything is working again but now EVERYTHING is so SLOWHey, there's a problem!
Psn doesn't load, YouTube on the Ps4 doesn't load!
Well Netflix on the Ps4 does load
Any solution?
I'm missing out on May Savings upto 60% off!!!!

Ah OK, I change my dns and everything is working again but now EVERYTHING is so SLOW
Response time is awful, I was really enjoying being on the Google dns![]()
PING bbc.co.uk (212.58.246.78): 56 data bytes
64 bytes from 212.58.246.78: icmp_seq=0 ttl=53 time=198.4 ms
64 bytes from 212.58.246.78: icmp_seq=1 ttl=53 time=213.2 ms
64 bytes from 212.58.246.78: icmp_seq=2 ttl=53 time=216.8 ms
64 bytes from 212.58.246.78: icmp_seq=3 ttl=53 time=198.1 ms
64 bytes from 212.58.246.78: icmp_seq=4 ttl=53 time=208.4 ms
64 bytes from 212.58.246.78: icmp_seq=5 ttl=53 time=201.4 ms
64 bytes from 212.58.246.78: icmp_seq=6 ttl=53 time=203.9 ms
64 bytes from 212.58.246.78: icmp_seq=7 ttl=53 time=199.0 ms
64 bytes from 212.58.246.78: icmp_seq=8 ttl=53 time=210.3 ms
64 bytes from 212.58.246.78: icmp_seq=9 ttl=53 time=203.9 ms
--- bbc.co.uk ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max = 198.1/205.3/216.8 ms
PING 155.239.255.250 (155.239.255.250): 56 data bytes
64 bytes from 155.239.255.250: icmp_seq=0 ttl=64 time=15.3 ms
64 bytes from 155.239.255.250: icmp_seq=1 ttl=64 time=21.2 ms
64 bytes from 155.239.255.250: icmp_seq=2 ttl=64 time=14.6 ms
64 bytes from 155.239.255.250: icmp_seq=3 ttl=64 time=14.4 ms
64 bytes from 155.239.255.250: icmp_seq=4 ttl=64 time=14.3 ms
64 bytes from 155.239.255.250: icmp_seq=5 ttl=64 time=15.0 ms
64 bytes from 155.239.255.250: icmp_seq=6 ttl=64 time=14.9 ms
64 bytes from 155.239.255.250: icmp_seq=7 ttl=64 time=14.4 ms
64 bytes from 155.239.255.250: icmp_seq=8 ttl=64 time=15.6 ms
64 bytes from 155.239.255.250: icmp_seq=9 ttl=64 time=15.1 ms
--- 155.239.255.250 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max = 14.3/15.4/21.2 ms