Plugg Uncapped ADSL Feedback

Ok guys those that jumped ship from other ISP's and moved to Plugg.

What are your thoughts about the service / speeds?

I have an account for a month. It is quite good and have not had any issues. Will stay with my current provider until the end of the month, and will make a decision whether or not to make Plugg my primary provider.

Are they IS resellers?

From their site: "PLuGG is the consumer division of Internet Solutions."

Hi Guys

If you could please indicate latency to;
46.163.100.220 & 94.76.233.68

And throughput on port 5938 & 80 to confirm that it is not too badly shaped during office hours via; http://broadband.mpi-sws.org/transparency/bttest-mlab.php

Yes very interesting indeed. I bought a 1gb Prepaid account for testing and I'm getting pre-MTN levels of latency. Checking out its performance during the coming month.

Yeah same here. It feels the same as before because I'm back with IS. I personally never had problems on IS and never complained about them.

I moved over to Plugg (4mb Uncapped account) at the start of this month. Before that, I was with Afrihost for about 3 or 4 months (10mb Uncapped). I haven't run into any issues yet, and have been really happy with the latency and performance, during office hours and after hours. (Similar to my experience with Afrihost when they were still using IS. I know some didn't have the same luck). At the moment my usage is sitting on 46gb.

who.is.michael said:

Hi Guys

If you could please indicate latency to;
46.163.100.220 & 94.76.233.68

And throughput on port 5938 & 80 to confirm that it is not too badly shaped during office hours via; http://broadband.mpi-sws.org/transparency/bttest-mlab.php

Click to expand...

Ping results: (Ran them at 18:38)

46.163.100.220

Pinging 46.163.100.220 with 32 bytes of data:
Reply from 46.163.100.220: bytes=32 time=209ms TTL=117
Reply from 46.163.100.220: bytes=32 time=209ms TTL=117
Reply from 46.163.100.220: bytes=32 time=209ms TTL=117
Reply from 46.163.100.220: bytes=32 time=209ms TTL=117
Reply from 46.163.100.220: bytes=32 time=209ms TTL=117
Reply from 46.163.100.220: bytes=32 time=209ms TTL=117
Reply from 46.163.100.220: bytes=32 time=209ms TTL=117
Reply from 46.163.100.220: bytes=32 time=209ms TTL=117
Reply from 46.163.100.220: bytes=32 time=211ms TTL=117
Reply from 46.163.100.220: bytes=32 time=209ms TTL=117
Reply from 46.163.100.220: bytes=32 time=211ms TTL=117
Reply from 46.163.100.220: bytes=32 time=209ms TTL=117
Reply from 46.163.100.220: bytes=32 time=209ms TTL=117
Reply from 46.163.100.220: bytes=32 time=209ms TTL=117
Reply from 46.163.100.220: bytes=32 time=209ms TTL=117
Reply from 46.163.100.220: bytes=32 time=209ms TTL=117
Reply from 46.163.100.220: bytes=32 time=209ms TTL=117
Reply from 46.163.100.220: bytes=32 time=209ms TTL=117
Reply from 46.163.100.220: bytes=32 time=209ms TTL=117
Reply from 46.163.100.220: bytes=32 time=210ms TTL=117

Ping statistics for 46.163.100.220:
Packets: Sent = 20, Received = 20, Lost = 0 (0% los
Approximate round trip times in milli-seconds:
Minimum = 209ms, Maximum = 211ms, Average = 209ms

94.76.233.68

Pinging 94.76.233.68 with 32 bytes of data:
Reply from 94.76.233.68: bytes=32 time=182ms TTL=55
Reply from 94.76.233.68: bytes=32 time=182ms TTL=55
Reply from 94.76.233.68: bytes=32 time=183ms TTL=55
Reply from 94.76.233.68: bytes=32 time=182ms TTL=55
Reply from 94.76.233.68: bytes=32 time=181ms TTL=55
Reply from 94.76.233.68: bytes=32 time=181ms TTL=55
Reply from 94.76.233.68: bytes=32 time=182ms TTL=55
Reply from 94.76.233.68: bytes=32 time=182ms TTL=55
Reply from 94.76.233.68: bytes=32 time=182ms TTL=55
Request timed out.
Reply from 94.76.233.68: bytes=32 time=182ms TTL=55
Reply from 94.76.233.68: bytes=32 time=182ms TTL=55
Reply from 94.76.233.68: bytes=32 time=182ms TTL=55
Reply from 94.76.233.68: bytes=32 time=182ms TTL=55
Reply from 94.76.233.68: bytes=32 time=182ms TTL=55
Reply from 94.76.233.68: bytes=32 time=182ms TTL=55
Reply from 94.76.233.68: bytes=32 time=182ms TTL=55
Reply from 94.76.233.68: bytes=32 time=182ms TTL=55

Ping statistics for 94.76.233.68:
Packets: Sent = 18, Received = 17, Lost = 1 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 181ms, Maximum = 183ms, Average = 181ms

Okay so I'm moving to Plugg! Working off a test account right now and am really happy with the performance. Anyone know what the limits would be on a 4Mbps uncapped account? The sales person I spoke to said 60GB which seems a bit low.

uWell when Afrihost used to be with IS, the most I did 1 month was about 150GB and never really noticed throttling, but not sure if there is also some type of rolling windows if u don't spam downloads for a few days that u don't get throttled to much.

Plugg uses IS so they must be good. I have never had any issues on IS

Looking at moving to them this week from Mwebs untrusty speeds. My avg use is around 90gigs a month, this a problem with plugg? Will be on the 2meg line.

For those people asking about usage caps or rolling windows have a look at my usage for last month below



Hope it helps

Is there anyone here from Plugg that can supply me with a test account?
I've cancelled with AfriHost and want to test out Plugg.

Edit : Nevermind. Already sorted elsewhere.

Hi Nimz, just signed with Plugg. Nice stats, what line is that on? I'm on 2meg

ijack said:

Plugg uses IS so they must be good. I have never had any issues on IS

Click to expand...

Plugg doesn't use IS, they are IS...

bradza said:

Hi Nimz, just signed with Plugg. Nice stats, what line is that on? I'm on 2meg

Click to expand...

2 locations

6MB & 2MB line

So after testing my Plugg for a couple days now. I can report all is good and well. NZB's running full line speed and No lag what so ever playing World of Warcraft on European server.

Youtube is also very good did not have any problem with that.

I have been with Plugg for over a year. Not one outtage, good latency, great speeds. I haven't had to call support once.

anyones connection go down just past midnight? Have had excellent connection tho since joining midweek.