Plugg Uncapped ADSL Feedback

shogun · Jan 9, 2013

Niren_M said:
Been really happy with Plugg since I moved from Afrihost about 2 months ago.

Have to second this. Been happy enough with plugg so far. 2 concurrent connections ha been awesome to take advantage of.

TMoose · Jan 9, 2013

Niren_M said:
Been really happy with Plugg since I moved from Afrihost about 2 months ago.

Also have to +1 this. I've been super happy with plugg, did more than 120GB in December on 'n 1Mbps. No disconnects, no downtime, no crawling along. The connection is always snappy and always seems to run at full speed. I've yet to experience shaping.

janitor@plugg · Jan 9, 2013

Howdy!

blunt said:
I notice the IS accounts don't use the SA mirrors for Gmail, even though there are SA mirrors.
What is the reason for this?

We do have Google CDN devices deployed on our network, however, it is up to Google to decide what get cached, where and when to offload content. This is purely based on where Google believe the biggest performance boost will be.

As for Google Mail; we believe that it is often not offloaded purely due to the nature of the service and the user specific content. In other words, even if you are connecting to a local IP chances are that the content that you are retrieving will still be fetched internationally.

--
The Janitor @ PluGG

PluGG - Consumer division of Internet Solutions
[email protected] | [email protected]
www.plugg.co.za | 08611 PluGG | www.is.co.za

#include <std-disclaimer.h>

blunt · Jan 9, 2013

thanks janitor

Tinuva · Jan 10, 2013

janitor@plugg said:
Howdy!

We do have Google CDN devices deployed on our network, however, it is up to Google to decide what get cached, where and when to offload content. This is purely based on where Google believe the biggest performance boost will be.

As for Google Mail; we believe that it is often not offloaded purely due to the nature of the service and the user specific content. In other words, even if you are connecting to a local IP chances are that the content that you are retrieving will still be fetched internationally.

--
The Janitor @ PluGG

PluGG - Consumer division of Internet Solutions
[email protected] | [email protected]
www.plugg.co.za | 08611 PluGG | www.is.co.za

#include <std-disclaimer.h>

What about peering with the local Google clusters? The ones hosted by Google, not the CDN servers.

I know the one at CINX will be discontinued soon, but there is a new one at NapAfrica in JHB soon, as well as later at NapAfrica CPT later?

CPTBoy · Jan 10, 2013

Tinuva said:
What about peering with the local Google clusters? The ones hosted by Google, not the CDN servers.

I know the one at CINX will be discontinued soon, but there is a new one at NapAfrica in JHB soon, as well as later at NapAfrica CPT later?

Are there any ramifications for average Joe in CPT when CINX is discontinued?

Tinuva · Jan 10, 2013

CPTBoy said:
Are there any ramifications for average Joe in CPT when CINX is discontinued?

Highly doubt it, users that are directed to it will just be redirected to another cluster, like Google does with all their services.

janitor@plugg · Jan 10, 2013

Howdy!

CPTBoy said:
when CINX is discontinued?

I have seen no notifications from ISPA that they are planning to take down CINX.

Can you supply us with more information regarding this, since it would make no sense to do so.

Tinuva · Jan 10, 2013

janitor@plugg said:
Howdy!

I have seen no notifications from ISPA that they are planning to take down CINX.

Can you supply us with more information regarding this, since it would make no sense to do so.

No he was referring to this post where I asked:

Tinuva said:
What about peering with the local Google clusters? The ones hosted by Google, not the CDN servers.

I know the one at CINX will be discontinued soon, but there is a new one at NapAfrica in JHB soon, as well as later at NapAfrica CPT later?

CPTBoy · Jan 10, 2013

My bad, my wording made it sound like the entire CINX is going to be discontinued ...

blunt · Jan 10, 2013

Tinuva said:
What about peering with the local Google clusters? The ones hosted by Google, not the CDN servers.

I know the one at CINX will be discontinued soon, but there is a new one at NapAfrica in JHB soon, as well as later at NapAfrica CPT later?

Whats the story with discontinuing the CPT CINX google cluster?

Tinuva · Jan 10, 2013

blunt said:
Whats the story with discontinuing the CPT CINX google cluster?

They moving it to NapAfrica in Cape Town.

Still want to know why Plugg doesn't peer with them.

Abe · Jan 10, 2013

I have been working on a 4 Meg trial account for the last 2 days and am very impressed. I use a large WebAfrica capped account as my primary account and was using a 35 Meg Afrihost capped account as a backup but after a few months of serious problems with the AH account I cancelled it. I never considered uncapped before because I need to be able use the account on 2 lines. Since Plugg supports this I decided to give it a go.

My experiences so far:

Youtube - only buffered a bit on 1080. Everything else was perfect. Downloading a 1080 video has it coming down at about 230k so it's just over half of the line speed.
Normal Use (Browsing Emails, etc) - No problems at all. Feels very responsive.
Speed test - about 3.5 meg down 0.5 up. Same result on international and local. Forgot the ping times.
Gaming - No issues at all. Latency seems fine. No disconnects although I had 1 spike.
Torrents - Don't use.
Game Download (Tested with SWTOR) - Spent most of the time at full speed (420k) with the odd dip down to 60k. I had to pause and restart the download once but that could easily have been a problem on the SWTOR servers.

janitor@plugg · Jan 10, 2013

Howdy!

Apologies for the delay in response, but this Janitor is still enjoying his holiday

Tinuva said:
Still want to know why Plugg doesn't peer with them.

Internet Solutions do peer locally with Google (in Cape Town).

---
The Janitor @ PluGG

PluGG - Consumer division of Internet Solutions
[email protected] | [email protected]
www.plugg.co.za | 08611 PluGG | www.is.co.za

#include <std-disclaimer.h>

Tinuva · Jan 10, 2013

janitor@plugg said:
Howdy!

Apologies for the delay in response, but this Janitor is still enjoying his holiday

Hope you enjoying the holidays, everyone needs them once in a while

janitor@plugg said:
Internet Solutions do peer locally with Google (in Cape Town).

I tested a traceroute on the IS route server, but it looks like it still goes international looking at the latencies.

Code:

local-route-server>traceroute 74.125.233.19

Type escape sequence to abort.
Tracing the route to cpt01s01-in-f19.1e100.net (74.125.233.19)

  1 196.4.160.1 [AS 3741] 0 msec 0 msec 0 msec
  2 ar2-rba-tnr-gi0-3-11.ip.isnet.net (196.34.7.195) [AS 3741] 0 msec 0 msec 4 msec
  3 core1-pkl-tg0-7-0-0.ip.isnet.net (168.209.1.162) [AS 3741] 4 msec 4 msec 4 msec
  4 core1b-dock-tenge-0-4-0-0-127.ip.isnet.net (168.209.201.77) [AS 3741] 188 msec 188 msec 184 msec
  5 195.66.224.125 172 msec 176 msec 176 msec
  6 209.85.240.63 180 msec 172 msec 176 msec
  7 209.85.252.45 [MPLS: Label 570965 Exp 4] 204 msec 208 msec 204 msec
  8 209.85.248.227 332 msec 332 msec 336 msec
  9 64.233.174.105 328 msec 328 msec 328 msec
 10 cpt01s01-in-f19.1e100.net (74.125.233.19) 324 msec 324 msec 324 msec

When I do the same test on MTN-Business router server in JHB, it looks fairly different:

Code:

lg1.jnb6.za#traceroute ip www.google.com
Translating "www.google.com"...domain server (196.7.0.138) [OK]

Type escape sequence to abort.
Tracing the route to www.google.com (74.125.233.17)

  1 ge2-24.hr8.jnb6.za.mtnbusiness.net (196.31.44.142) 4 msec 0 msec 0 msec
  2 74.125.49.218 [AS 15169] 28 msec 28 msec 24 msec
  3 64.233.174.105 [AS 15169] 28 msec 28 msec 28 msec
  4 www.google.com (74.125.233.17) [AS 15169] 24 msec 64 msec 28 msec

So it would seem IS do peer with Google in London, but not in South Africa.

Maybe I should rephrase my question. When will you guys peer with Google in South Africa?

janitor@plugg · Jan 10, 2013

Tinuva said:
Hope you enjoying the holidays, everyone needs them once in a while

I tested a traceroute on the IS route server, but it looks like it still goes international looking at the latencies.
So it would seem IS do peer with Google in London, but not in South Africa.

Maybe I should rephrase my question. When will you guys peer with Google in South Africa?

I'll respond this evening when am in front of my laptop. Typing out on my mobile phone a slight challenge

Tinuva · Jan 10, 2013

janitor@plugg said:
I'll respond this evening when am in front of my laptop. Typing out on my mobile phone a slight challenge

Thank you janitor

janitor@plugg · Jan 10, 2013

Howdy Howdy!

Tinuva said:
I tested a traceroute on the IS route server, but it looks like it still goes international looking at the latencies. So it would seem IS do peer with Google in London, but not in South Africa.

Maybe I should rephrase my question. When will you guys peer with Google in South Africa?

As per my previous response; IS currently peer locally with Google in Cape Town and therefor our coastal regions would benefit from that arrangement.

Trace from DSL in Cape Town:

Code:

janitor-ctn#traceroute www.google.co.za source vlan1

Tracing the route to www.google.co.za (196.23.168.163)

  1 196-210-152-1.dynamic.isadsl.co.za (196.210.152.1) 12 msec 12 msec 12 msec
  2 cdsl1-ctn-vl2173.ip.isnet.net (196.38.72.113) 16 msec 16 msec 12 msec
  3 196.35.115.128 16 msec 12 msec 12 msec
  4 core2a-ctn-gi0-2.ip.isnet.net (168.209.6.6) 16 msec 16 msec 12 msec
  5 168.209.100.213 36 msec 36 msec 32 msec
  6 csw6-pkl-te1-7.ip.isnet.net (196.26.0.189) 44 msec 36 msec 32 msec
  7  *  *  *
  8  *  *
janitor-ctn#

janitor-ctn#traceroute www.google.com source vlan1

Tracing the route to www.google.com (196.23.168.166)

  1 196-210-152-1.dynamic.isadsl.co.za (196.210.152.1) 12 msec 28 msec 12 msec
  2 196.38.72.125 12 msec 16 msec 12 msec
  3 196.35.115.136 16 msec 12 msec 16 msec
  4 core2a-ctn-gi0-1.ip.isnet.net (168.209.2.6) 16 msec 16 msec 16 msec
  5 168.209.100.213 48 msec 104 msec 36 msec
  6 csw6-pkl-te1-7.ip.isnet.net (196.26.0.189) 32 msec 40 msec
    csw5-pkl-te1-7.ip.isnet.net (196.26.0.188) 44 msec
  7  *  *  *
  8  *  *
janitor-ctn#

Code:

janitor-ctn#ping www.google.co.za source vlan1

Sending 5, 100-byte ICMP Echos to 196.23.168.166, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 32/40/60 ms

janitor-ctn#ping www.google.com source vlan1

Sending 5, 100-byte ICMP Echos to 196.23.168.154, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 32/37/48 ms

versus from my home in Johannesburg

Code:

velocidade#traceroute ip www.google.co.za

Tracing the route to www.google.co.za (74.125.233.88)

  1 196-210-138-129.dynamic.isadsl.co.za (196.210.138.129) 8 msec 8 msec 8 msec
  2 cdsl1-rba-vl2253.ip.isnet.net (196.38.73.181) 8 msec 8 msec 8 msec
  3 cdsl1-rba-vl150.ip.isnet.net (196.38.73.17) 8 msec 8 msec 8 msec
  4 core2b-pkl-te0-0-0-0.ip.isnet.net (196.26.0.63) 12 msec 12 msec 12 msec
  5 core2b-dock-tenge-0-3-0-0-126.ip.isnet.net (168.209.201.81) 200 msec 196 msec 192 msec
  6 195.66.236.125 184 msec 188 msec 184 msec
  7 209.85.240.63 192 msec 192 msec 192 msec
  8 209.85.253.94 188 msec 196 msec
    209.85.253.92 196 msec
  9 72.14.232.210 212 msec 200 msec 200 msec
 10 216.239.43.43 296 msec 204 msec 208 msec
 11 72.14.232.103 372 msec 372 msec 372 msec
 12 64.233.174.57 372 msec 372 msec 372 msec
 13 www.google.co.za (74.125.233.88) 368 msec 364 msec 364 msec
velocidade#

velocidade#traceroute www.google.com

Tracing the route to www.google.com (2C0F:FB50:4002:801::1010)

  1 2C0F:FC00:5000:13::1 16 msec 16 msec 16 msec
  2 2C0F:FC00:0:6::2 16 msec 16 msec 20 msec
  3 2C0F:FC00:2:6::2 40 msec 44 msec 44 msec
  4 2C0F:FC00:0:7::8 52 msec 44 msec 40 msec
  5 2C0F:FC00:5002::2 48 msec 36 msec 44 msec
  6 2001:4860::4:0:118D 164 msec 164 msec 160 msec
  7 2001:4860::1:0:1070 172 msec 180 msec 180 msec
  8 2001:4860::1:0:2478 248 msec 216 msec 196 msec
  9 2001:4860::4:0:4053 352 msec 356 msec 356 msec
 10 2001:4860:0:1::625 352 msec 352 msec 352 msec
 11 2C0F:FB50:8000:3::1 352 msec 352 msec 356 msec
velocidade#

Code:

velocidade#ping ip www.google.co.za

Sending 5, 100-byte ICMP Echos to 74.125.233.88, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 368/368/372 ms
velocidade#

velocidade#ping www.google.com

Sending 5, 100-byte ICMP Echos to 2C0F:FB50:4002:801::1013, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 348/352/368 ms
velocidade#

Internet Solutions is in the process of extending peering with Google to Johannesburg, but it is currently taking longer than initially anticipated. IS' route server is hosted in Johannesburg, hence the results that you received via the UK peering.

Hope this clears it up

--
The Janitor @ PluGG

PluGG - Consumer division of Internet Solutions
[email protected] | [email protected]
www.plugg.co.za | 08611 PluGG | www.is.co.za

#include <std-disclaimer.h>

Tinuva · Jan 10, 2013

Good to hear you will peer in JHB.

However, the traceroute you show for cape town, is to the IS Google CDN servers hosted on the IS network, not the actuak Google Cape Town servers.

Here is my traceroute at home (in Cape Town) to the CINX Google Network:

Code:

C:\Users\Tinuva>tracert www.google.com

Tracing route to www.google.com [74.125.233.20]
over a maximum of 30 hops:

  1     4 ms    <1 ms    <1 ms  router.heaven.za.net [10.0.0.1]
  2     6 ms     5 ms    15 ms  196-210-201-1.dynamic.isadsl.co.za [196.210.201.1]
  3    13 ms     7 ms    17 ms  196.38.72.125
  4    15 ms     7 ms    17 ms  196.35.115.136
  5     7 ms    16 ms     7 ms  core1b-ctn-gi0-2.ip.isnet.net [168.209.6.4]
  6    13 ms     7 ms    28 ms  168.209.6.131
  7   165 ms   158 ms   157 ms  168.209.100.222
  8   157 ms   157 ms   168 ms  64.233.174.105
  9   165 ms   156 ms   156 ms  cpt01s01-in-f20.1e100.net [74.125.233.20]

Trace complete.

Also seems to go to via the UK outbound, but inbound seems to at least return via CINX because the latency is only ~160ms instead of ~340ms.

Either way, still good to hear the peering with google in JHB will happen

janitor@plugg · Jan 10, 2013

Tinuva said:
However, the traceroute you show for cape town, is to the IS Google CDN servers hosted on the IS network, not the actuak Google Cape Town servers.

CDN will always take preference over peering, unless Google decide they need to take it down for <flavour reasoning of the day> and then traffic will be routed over the peering point.

Am just a Janitor ;-) but I fully do understand what you getting at.

Either way, still good to hear the peering with google in JHB will happen

Have a good eve!

---
[email protected]

... Sent via RFC 1149

Join the MyBroadband community

Get started

Plugg Uncapped ADSL Feedback

Expert Member

Expert Member

Plugg representative

Expert Member

The Magician

Expert Member

The Magician

Plugg representative

The Magician

Expert Member

Expert Member

The Magician

Expert Member

Plugg representative

The Magician

Plugg representative

The Magician

Plugg representative

The Magician

Plugg representative