Sorry about that, working hard on a fix.
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: What is your primary source of drinking water?
- Status
Sorry about that, working hard on a fix.
renagade-wolf
Well-Known Member
- Joined
- Jun 16, 2012
- Messages
- 366
- Reaction score
- 39
It varies, recently though the weather has played a major part. will check tomorrow if if it happens with clearer skies
What the hell is going on now....
Tracing route to ql.kreaper.co.za [196.44.45.98]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 * * 141 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 * 151 ms 140 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
5 179 ms 137 ms 137 ms 169-1-5-132.ip.afrihost.co.za [169.1.5.132]
6 137 ms 137 ms 137 ms adept.ct1.napafrica.net [196.10.140.72]
7 145 ms * 143 ms v498.pe0.adc.adept.za.net [196.44.40.193]
8 143 ms 141 ms 141 ms g0-9.bb3.adc.adept.za.net [196.44.40.118]
9 145 ms 142 ms 155 ms e1.fw0.adc.adept.za.net [196.44.32.197]
10 142 ms 155 ms 140 ms ql.kreaper.co.za [196.44.45.98]
Here is bras:
Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Ping statistics for 155.239.255.250:
Packets: Sent = 185, Received = 185, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 112ms, Average = 13ms
Tracing route to ql.kreaper.co.za [196.44.45.98]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 * * 141 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 * 151 ms 140 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
5 179 ms 137 ms 137 ms 169-1-5-132.ip.afrihost.co.za [169.1.5.132]
6 137 ms 137 ms 137 ms adept.ct1.napafrica.net [196.10.140.72]
7 145 ms * 143 ms v498.pe0.adc.adept.za.net [196.44.40.193]
8 143 ms 141 ms 141 ms g0-9.bb3.adc.adept.za.net [196.44.40.118]
9 145 ms 142 ms 155 ms e1.fw0.adc.adept.za.net [196.44.32.197]
10 142 ms 155 ms 140 ms ql.kreaper.co.za [196.44.45.98]
Here is bras:
Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Ping statistics for 155.239.255.250:
Packets: Sent = 185, Received = 185, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 112ms, Average = 13ms
I did, unfortunately the net content of it is "something broke" and "we are seeing reports...".Read up
We're seeing issues on the South IPC, sorry about that.
http://mybroadband.co.za/vb/showthr...ack-Part-2?p=18010012&viewfull=1#post18010012
Reign
Well-Known Member
- Joined
- Apr 20, 2009
- Messages
- 380
- Reaction score
- 26
Any idea when this problem will be resolved?
No ETR confirmed at this stage I'm afraid.
I'll have updates posted here as soon as they're made available to me.
Slow DSL Speeds And Latency South Region
We are receiving reports that DSL clients in the South Region (Cape Town, Port Elizabeth, East London and others parts of the Eastern and Western Cape) are experiencing slow speeds and increased latency.
We are investigating the cause of the poor performance and we will provide the best internet experience possible under the circumstances.
We sincerely apologise to affected clients for any inconvenience this may cause.
We are receiving reports that DSL clients in the South Region (Cape Town, Port Elizabeth, East London and others parts of the Eastern and Western Cape) are experiencing slow speeds and increased latency.
We are investigating the cause of the poor performance and we will provide the best internet experience possible under the circumstances.
We sincerely apologise to affected clients for any inconvenience this may cause.
Reign
Well-Known Member
- Joined
- Apr 20, 2009
- Messages
- 380
- Reaction score
- 26
Thanks for the response. Hopefully soon
CTBP
Executive Member
- Joined
- Nov 22, 2010
- Messages
- 6,761
- Reaction score
- 8,224
Last Result:
Download Speed: 404 kbps (50.5 KB/sec transfer rate)
Upload Speed: 801 kbps (100.1 KB/sec transfer rate)
Latency: 131 ms
Jitter: 82 ms
2016/07/20, 4:15:13 PM
In the South, I haven't seen internet this slow in many years, takes you back doesn't it lol.
20Mbs line btw.
Edit: My 2nd and 3rd test timed out, just how serious is this problem?
Download Speed: 404 kbps (50.5 KB/sec transfer rate)
Upload Speed: 801 kbps (100.1 KB/sec transfer rate)
Latency: 131 ms
Jitter: 82 ms
2016/07/20, 4:15:13 PM
In the South, I haven't seen internet this slow in many years, takes you back doesn't it lol.
20Mbs line btw.
Edit: My 2nd and 3rd test timed out, just how serious is this problem?
Last edited:
You'll see high latency and slow speeds for the moment, it's something we're working on.
Shouldn't be much longer.
electrofreeze
Expert Member
we have been seeing this for some time now so what is new are you getting more ipc?
This is in no way related, it's an isolated outage that's only been present since my initial post.
If you're having issues you'll need to back up your posts with some test results, as requested numerous times before.
Local counterstrike matchmaking is quite awful in the South Right now. 3 of us in Port Elizabeth had a consistent 170 ping. The other two are in the same area but had a normal ping. Strangely enough, discord's website cannot be accessed either from afrihost at the moment either. Voice chat over discord however works completely fine still.
electrofreeze
Expert Member
i think there is enough test results here already and lets not forget your denial with the previous problems this year so dont blame the us for not believing
we are paying for a working service not a broken one
Sorry about the issues here, we're aware of the problems affecting the South IPC and are working on a fix.
https://www.afrihost.com/site/network_status#tabs
Chill dude, your porn wont run away.
We really need to move forward with this now, we're happy to help - but running on assumptions from the past simply won't resolve any issues.
Once this issue is resolved and you're still having issues you're welcome to post some test data here for us to look at. That's the only way we can help.
- Status