DigiChilli Trial Account Feedback/Status/Results

heynnow said:
Hi Dave,

I have been testing the account from different IP's /locations. Intl browsing and local gaming seems great, except for one problem which i think the international gamers will have is the following:

The account randomly times out pinging to intl servers:


Pinging www.l.google.com [74.125.87.103] with 32 bytes of data:
Reply from 74.125.87.103: bytes=32 time=310ms TTL=51
Reply from 74.125.87.103: bytes=32 time=307ms TTL=51
Reply from 74.125.87.103: bytes=32 time=306ms TTL=51
Request timed out.
Reply from 74.125.87.103: bytes=32 time=309ms TTL=51
Request timed out.
Reply from 74.125.87.103: bytes=32 time=309ms TTL=51
Request timed out.
Reply from 74.125.87.103: bytes=32 time=307ms TTL=51
Reply from 74.125.87.103: bytes=32 time=307ms TTL=51
Reply from 74.125.87.103: bytes=32 time=308ms TTL=51
Reply from 74.125.87.103: bytes=32 time=309ms TTL=51
Reply from 74.125.87.103: bytes=32 time=309ms TTL=51
Request timed out.
Reply from 74.125.87.103: bytes=32 time=310ms TTL=51
Reply from 74.125.87.103: bytes=32 time=308ms TTL=51
Reply from 74.125.87.103: bytes=32 time=309ms TTL=51
Reply from 74.125.87.103: bytes=32 time=309ms TTL=51
Reply from 74.125.87.103: bytes=32 time=306ms TTL=51
Reply from 74.125.87.103: bytes=32 time=309ms TTL=51
Reply from 74.125.87.103: bytes=32 time=311ms TTL=51
Reply from 74.125.87.103: bytes=32 time=309ms TTL=51
Reply from 74.125.87.103: bytes=32 time=308ms TTL=51
Reply from 74.125.87.103: bytes=32 time=303ms TTL=51
Reply from 74.125.87.103: bytes=32 time=308ms TTL=51
Reply from 74.125.87.103: bytes=32 time=306ms TTL=51
Reply from 74.125.87.103: bytes=32 time=307ms TTL=51
Request timed out.
Reply from 74.125.87.103: bytes=32 time=308ms TTL=51
Request timed out.
Reply from 74.125.87.103: bytes=32 time=306ms TTL=51
Reply from 74.125.87.103: bytes=32 time=306ms TTL=51
Reply from 74.125.87.103: bytes=32 time=309ms TTL=51



as opposed to Telkom Do package:

Pinging www.l.google.com [209.85.227.104] with 32 bytes of data:
Reply from 209.85.227.104: bytes=32 time=376ms TTL=45
Reply from 209.85.227.104: bytes=32 time=394ms TTL=45
Reply from 209.85.227.104: bytes=32 time=369ms TTL=45
Reply from 209.85.227.104: bytes=32 time=368ms TTL=45
Reply from 209.85.227.104: bytes=32 time=367ms TTL=45
Reply from 209.85.227.104: bytes=32 time=366ms TTL=45
Reply from 209.85.227.104: bytes=32 time=369ms TTL=45
Reply from 209.85.227.104: bytes=32 time=389ms TTL=45
Reply from 209.85.227.104: bytes=32 time=372ms TTL=45
Reply from 209.85.227.104: bytes=32 time=416ms TTL=45
Reply from 209.85.227.104: bytes=32 time=368ms TTL=45
Reply from 209.85.227.104: bytes=32 time=370ms TTL=45
Reply from 209.85.227.104: bytes=32 time=368ms TTL=45
Reply from 209.85.227.104: bytes=32 time=365ms TTL=45
Reply from 209.85.227.104: bytes=32 time=370ms TTL=45
Reply from 209.85.227.104: bytes=32 time=370ms TTL=45
Reply from 209.85.227.104: bytes=32 time=369ms TTL=45
Reply from 209.85.227.104: bytes=32 time=368ms TTL=45
Reply from 209.85.227.104: bytes=32 time=370ms TTL=45
Reply from 209.85.227.104: bytes=32 time=369ms TTL=45
Reply from 209.85.227.104: bytes=32 time=364ms TTL=45
Reply from 209.85.227.104: bytes=32 time=374ms TTL=45
Reply from 209.85.227.104: bytes=32 time=367ms TTL=45
Reply from 209.85.227.104: bytes=32 time=366ms TTL=45
Reply from 209.85.227.104: bytes=32 time=366ms TTL=45
Reply from 209.85.227.104: bytes=32 time=365ms TTL=45
Reply from 209.85.227.104: bytes=32 time=364ms TTL=45
Reply from 209.85.227.104: bytes=32 time=368ms TTL=45
Reply from 209.85.227.104: bytes=32 time=367ms TTL=45
Reply from 209.85.227.104: bytes=32 time=365ms TTL=45
Reply from 209.85.227.104: bytes=32 time=369ms TTL=45
Reply from 209.85.227.104: bytes=32 time=366ms TTL=45


Is there any explanation for this? Is this because of the nature of the "burstable" Seacom link being used?

regards
Click to expand...

Digichilli & Telkom have different routing, hence the IP address of Igoogle are not the same on the two accounts! You should rather ping an IP address on both accounts to get an accurate reading.
 
Linoman said:
General Internet surfing speeds are amazing, everything just seems to load so far. HTTP download speeds are between 25kbps and 35kbps.

Will be testing Quake Live Now
Click to expand...

How I miss these days, it all honesty since going live, the service has dropped terribly. I was actually going to sign up for this service from January, however if is has not improved by the end of December I will be moving back to Afrihost.

I would rather have a capped service that I can actually use than a uncapped service that is slower than 56k dial up.

Browsing is slow, torrents max speed are 0.3kbps, http downloads at max are 8kbps, I am getting pings of 1200 on Quake Live now (That is to the local IS server in JHB:sick:)
 
I'm having the same problems, everything is just SLOOOOOOOOOOOOOOOW! :( Is this going to be fixed?
 
Linoman said:
I would rather have a capped service that I can actually use than a uncapped service that is slower than 56k dial up.
Click to expand...

There are other uncapped & unshaped options out there for about R500 which includes line rental and they work! You have options so no need to go back to a capped account ;)
 
ponder said:
There are other uncapped & unshaped options out there for about R500 which includes line rental and they work! You have options so no need to go back to a capped account ;)
Click to expand...

Excellent thank you ponder
 
ponder said:
There are other uncapped & unshaped options out there for about R500 which includes line rental and they work! You have options so no need to go back to a capped account ;)
Click to expand...

Yup, still not sure If I want to switch over or not :confused:
 
G3rri3 said:
I'm getting error 691 can someone please explain to me please,cant connect to digichilli only telkom.
Click to expand...

PM'd you G3rri3.

Thanks techrat and raedwulf.

We do understand your frustration.

Google isn't the cheapest. They're the best. We're authorised Google partners. And more than that too. The Google Apps that we sell are an upgraded version of the 'free' google apps available to the public. They rock.

The Google DNS was being used to eliminate any possibility that it was our dns servers causing the issue and latency. It's now eliminated.

We have had some over usage issues, not really due to any intention of users. The BIGGEST user - yeah, its still Gustav - is cool. He's behaving since the last hammer episode. He's network stats and monitoring software have even helped us a bit.

So, it's not just your torrents. Some people have deliberately set their torrents to be 'hidden' as http. Its not a common default, and hasn't caused too big an issue before. Even 4Mbps users aren't causing the issues. Further deliberately tweaking of your settings to avoid bandwidth management may be an issue now and then.

The deliberate brute force attack and DOS attacks are a bit annoying. We normally phone these guys and ask them to behave nicely. It would be better if we didn't have to do that at all.

We're are working 24/7 on the issue and will sort it out. We are making some changes which we have identified as possible issues. It is not something that even our BAD test users uncovered. Suffice it to say that it is in that piece between managing throttling to package size and contention with its myriads of settings. It's not something anyone has done successfully yet in this country, but we do intend to be the first.


Hold tite. This won't hurt much and you will be down for 10 min.

Morning all.

Dave
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X