Web Squad ISP

Status
Not open for further replies.
Looney said:
I’m in JHB, not sure what ping to expect. I was more focused on my download and upload speed lol.
Click to expand...
lucky fish, yeah im highlighting ping to asia jumped again
8195767772.png
 
Cowboy619 said:
Is websquad getting aws connectivity?
Click to expand...

We've got AWS DirectConnect as well as peering.

wingnut771 said:
or are you only supposed to get 1gig local, not national?
Click to expand...

Depends on the route and peering (basically the bandwidth available on the return route). On net we limit national Speedtest traffic to our own servers (Can't have speedtest traffic adversely affecting users in a region) - I think most ISPs will do this as we don't all have a hole to burn in our wallets waiting for speedtest traffic. Basically, if a user on any ISP connects to our JHB server from DBN/CPT, because we peer openly in all regions - we're transiting that traffic between JHB and DBN/CPT on their behalf, and we don't want that eating the traffic that our users actually pay for. Whereas if someone from a region (eg. Durban) on any ISP connects to our local server in the same region Eg. Durban), they won't adversely affect traffic for our own clients.

If you're picking up traffic from an IS server, you'll probably get 1G, from Optinet in the region of 500M (based on our tests) and so on an so forth. It's the nature of hot potato routing that we'll pick up traffic from the closest source in any region - but there's no guarantee that every operator will deliver traffic nationally at 1G. Our other option is to pick up all local traffic at NAP JHB, but then you'll see a 11-22ms knock to access local content and we're not an open peer.

NAP joburg is the biggest exchange, so higher likelihood of attaining traffic at higher speeds (1G +). Cape Town and Durban are less established and lots of peers still run <1G networks.
 
Code: 
Tracing route to speedtest.cn.mtn.co.za [41.208.50.154]
over a maximum of 30 hops:

  1     1 ms    <1 ms     1 ms  192.168.0.1
  2     1 ms     1 ms     1 ms  as-vuma.jb-is-pld-02.za.ws.net.za [160.119.228.129]
  3     3 ms     *        *     core.vuma-l3.jb1.za.ws.net.za [160.119.224.97]
  4     3 ms     2 ms     1 ms  core.as-xe-02.jb1.za.ws.net.za [160.119.224.89]
  5     2 ms     2 ms     1 ms  core.cr-xe-01.jb1.za.ws.net.za [160.119.224.29]
  6     3 ms     3 ms     3 ms  160.119.224.53
  7   175 ms   176 ms   176 ms  mtnns-2.jinx.net.za [196.223.14.31]
  8   177 ms   177 ms   177 ms  41.181.205.90
  9     *     ^C

Oh
 
Waylander said:
@websquadza can you comment?
Click to expand...

Just Commented. Remember the nature of peering is that we pick up the traffic at the closest exchange. So in the two tests above, both those ISPs hand over traffic to us at the closest exchange. (In this case, we pick up ISP V and S in JHB via peering - so that bandwidth is what they allow for national transit (I don't think it's a reflection of their actual national capacity, but rather a limitation to protect their networks))
 
Waylander said:
Code: 
Tracing route to speedtest.cn.mtn.co.za [41.208.50.154]
over a maximum of 30 hops:

  1     1 ms    <1 ms     1 ms  192.168.0.1
  2     1 ms     1 ms     1 ms  as-vuma.jb-is-pld-02.za.ws.net.za [160.119.228.129]
  3     3 ms     *        *     core.vuma-l3.jb1.za.ws.net.za [160.119.224.97]
  4     3 ms     2 ms     1 ms  core.as-xe-02.jb1.za.ws.net.za [160.119.224.89]
  5     2 ms     2 ms     1 ms  core.cr-xe-01.jb1.za.ws.net.za [160.119.224.29]
  6     3 ms     3 ms     3 ms  160.119.224.53
  7   175 ms   176 ms   176 ms  mtnns-2.jinx.net.za [196.223.14.31]
  8   177 ms   177 ms   177 ms  41.181.205.90
  9     *     ^C

Oh
Click to expand...
I know right :')
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X