MWEB internal peering issue?

Foxeye

Member
Joined
Mar 29, 2010
Messages
25
Reaction score
0
A couple of times since the launch of Homefront I have tried to get some "Friends Only" matches going.
Between me and 3 of my friends 3 of us are on MWEB and one is on an IS account.

Firstly I tried hosting (on my MWEB uncapped 4096). Everyone was able to connect. My 2 friends also on MWEB Uncapped 4096 accounts had over 200ms ping to me, and my friend on IS had 14ms ping...

That was the opposite to what I was expecting. Surely within MWEB accounts the ping should have been extremely low.

We tried having the other 2 MWEB guys to host, and the same thing. MWEB to MWEB post 200ms latency,with IS to MWEB being sub 30ms

In the end we had the guy on IS host. End result was we all had sub 30ms ping.

Anyone from MWEB here that can comment on this oddity?
 
A couple of times since the launch of Homefront I have tried to get some "Friends Only" matches going.
Between me and 3 of my friends 3 of us are on MWEB and one is on an IS account.

Firstly I tried hosting (on my MWEB uncapped 4096). Everyone was able to connect. My 2 friends also on MWEB Uncapped 4096 accounts had over 200ms ping to me, and my friend on IS had 14ms ping...

That was the opposite to what I was expecting. Surely within MWEB accounts the ping should have been extremely low.

We tried having the other 2 MWEB guys to host, and the same thing. MWEB to MWEB post 200ms latency,with IS to MWEB being sub 30ms

In the end we had the guy on IS host. End result was we all had sub 30ms ping.

Anyone from MWEB here that can comment on this oddity?

Hi Foxeye,

Please can you PM me your Mweb account details in order for me to look into this. I will have to confirm a few things and get some feedback from the relevant persons before commenting.

Regards,
MWEB Guy
 
Pinging www.mweb.co.za and www.cellc.co.za from my Mweb Uncapped ADSL yields this:

C:\Users\PatrickM>ping www.mweb.co.za

Pinging www.mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=55ms TTL=110
Reply from 196.2.63.110: bytes=32 time=71ms TTL=110
Reply from 196.2.63.110: bytes=32 time=56ms TTL=110
Reply from 196.2.63.110: bytes=32 time=60ms TTL=110

Ping statistics for 196.2.63.110:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 55ms, Maximum = 71ms, Average = 60ms

C:\Users\PatrickM>ping www.cellc.co.za

Pinging www.cellc.co.za [41.72.143.60] with 32 bytes of data:
Reply from 41.72.143.60: bytes=32 time=44ms TTL=52
Reply from 41.72.143.60: bytes=32 time=54ms TTL=52
Reply from 41.72.143.60: bytes=32 time=41ms TTL=52
Reply from 41.72.143.60: bytes=32 time=36ms TTL=52

Ping statistics for 41.72.143.60:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 54ms, Average = 43ms

Maybe Mweb needs some WHOOOSH too ? :D
 
That was the opposite to what I was expecting. Surely within MWEB accounts the ping should have been extremely low.

We tried having the other 2 MWEB guys to host, and the same thing. MWEB to MWEB post 200ms latency,with IS to MWEB being sub 30ms

In the end we had the guy on IS host. End result was we all had sub 30ms ping.

Shame issue here.. But on a PS3..I am on IS Uncapped and my bud is on Mweb :mad:uncapped.. If he host we lag mos days.. If i host he gets good enuf signal.. That is why i rather just play with my bro's WA account when playin with Mweb mense
 
Mweb - Peer shaping yourselves = Epic fail
How long does it take to get an answer? :sick:
 
Hi all

Please can we get some details on the exact issues being experienced here. Are we talking PC, or console platform and is anyone willing to assist with some traffic checks so that we can make sure the game is being handled correctly?

Thanks
Will
 
Hey Will,

All participants are on Steam purchased PC version of the game. You can pm me for contact details to assist in specific testing
 
Pinging www.mweb.co.za and www.cellc.co.za from my Mweb Uncapped ADSL yields this:

Maybe Mweb needs some WHOOOSH too ? :D

@Hazman our Portal servers are located in the Cape Town data center. If you're routing via our JHB IPC node as I suspect and getting to Cell-C via JINX then the route would be physically shorter, hence the lower ping. We could verify this if you posted some tracert results.

@Foxeye I have sent you a PM regarding Homefront testing.
 
Top
Sign up to the MyBroadband newsletter
X