Afrihost Business Uncapped Feedback - Part 3

Status
Not open for further replies.
AfriGuy said:
Can you also run a ping to bras.afrihost.com please?
Click to expand...

C:\WINDOWS\system32>tracert bras.afrihost.com

Tracing route to bras.afrihost.com [155.239.255.250]
over a maximum of 30 hops:

1 2 ms 2 ms 3 ms 192.168.100.50
2 91 ms 92 ms 91 ms 155.239.255.250

Trace complete.
 
zs6cey said:
C:\WINDOWS\system32>tracert bras.afrihost.com

Tracing route to bras.afrihost.com [155.239.255.250]
over a maximum of 30 hops:

1 2 ms 2 ms 3 ms 192.168.100.50
2 91 ms 92 ms 91 ms 155.239.255.250

Trace complete.
Click to expand...


C:\WINDOWS\system32>ping bras.afrihost.com

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Request timed out.
Reply from 155.239.255.250: bytes=32 time=84ms TTL=63
Reply from 155.239.255.250: bytes=32 time=119ms TTL=63
Reply from 155.239.255.250: bytes=32 time=82ms TTL=63

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 82ms, Maximum = 119ms, Average = 95ms
 
zs6cey said:
C:\WINDOWS\system32>ping bras.afrihost.com

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Request timed out.
Reply from 155.239.255.250: bytes=32 time=84ms TTL=63
Reply from 155.239.255.250: bytes=32 time=119ms TTL=63
Reply from 155.239.255.250: bytes=32 time=82ms TTL=63

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 82ms, Maximum = 119ms, Average = 95ms
Click to expand...

Do you perhaps have a backup ISP account to double check the same results?
 
I do have a backup account but unfortunately they are experiencing some issues as well....
Testing that wouldn't be worth it....

C:\Users\JesseG>tracert www.speedtest.com

Tracing route to www.speedtest.com [209.15.13.134]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 * * * Request timed out.
3 22 ms 21 ms 21 ms 41.170.79.229
4 20 ms 20 ms 20 ms 41.170.79.230
5 21 ms 20 ms 21 ms 41.170.79.236
6 20 ms 20 ms 20 ms 41.160.2.33
7 21 ms 20 ms 21 ms ix-0-3-0-0.tcore1.JSO-Johannesburg.as6453.net [2
16.6.55.37]
8 281 ms 310 ms 282 ms if-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.1
78.2]
9 168 ms 168 ms 202 ms if-1-0-0-3.core2.PV9-Lisbon.as6453.net [195.219.
214.34]
10 286 ms 286 ms 285 ms if-0-0-0-2000.tcore1.PV9-Lisbon.as6453.net [80.2
31.158.1]
11 287 ms 286 ms 288 ms if-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.
158.30]
12 289 ms 289 ms 290 ms if-6-2.thar1.NJY-Newark.as6453.net [80.231.138.1
8]
13 282 ms 279 ms 279 ms if-3-2.tcore1.NYY-New-York.as6453.net [66.198.70
.22]
14 286 ms 285 ms 286 ms if-11-2.tcore2.NYY-New-York.as6453.net [216.6.99
.1]
15 282 ms 282 ms 282 ms if-12-6.tcore1.CT8-Chicago.as6453.net [216.6.99.
46]
16 280 ms 280 ms 279 ms if-22-2.tcore2.CT8-Chicago.as6453.net [64.86.79.
1]
17 289 ms 283 ms 283 ms if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96
.45]
18 291 ms 291 ms 290 ms 66.110.8.34
19 * * * Request timed out.
20 ^C

EDIT : Just tested again on Afrigreen account
 
zs6cey said:
C:\WINDOWS\system32>ping bras.afrihost.com

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Request timed out.
Reply from 155.239.255.250: bytes=32 time=84ms TTL=63
Reply from 155.239.255.250: bytes=32 time=119ms TTL=63
Reply from 155.239.255.250: bytes=32 time=82ms TTL=63

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 82ms, Maximum = 119ms, Average = 95ms
Click to expand...

This looks better:

C:\WINDOWS\system32>ping bras.afrihost.com

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 12ms, Average = 11ms
 
zs6cey said:
This looks better:

C:\WINDOWS\system32>ping bras.afrihost.com

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 12ms, Average = 11ms
Click to expand...

That looks good. Good, consistent pings.
 
zs6cey said:
Sorry No I do not. I get the feeling this is wide spread as I see people complaining at Vox and WebAfrica
Click to expand...

Could very well be. There's a dip in throughput in the East specifically at the moment.
Monitoring looks good and I'm not seeing anything published on the Telkom noticeboard either. Odd. I'll see if I can do some digging quickly.
 
Rickster said:
Sure.
Click to expand...

Can connect to any listed hub. Haven't used DC++ in years, so I'm rusty.
Pasted my log below though - only edited the public IP.

Code: 
[17:38] *** Connecting to <traphouse.tankafett.biz:420>...
[17:38] *** Connected
[17:38] <TrapBot> 

		 \\\\//
		l_   _ l
		(Q Q )		Welcome hydrasec to Trap House Productions •][Tankafett Network][• 
		l   ^  l			
		 \ ~  /			Enjoy your stay....
	 __oOOO--~#~--OOOo ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ___
	l____l____l____l____l____l____l____l____l____l____l____l____l____l____l____l_
	  l____l____l____l____l____l____l____l____l____l____l____l____l____l____l____l
		
		.:: HUBINFO ::.

		.:: Now users online: 876
		.:: Files available: 222.62 TB
	   ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____     
	  l____l____l____l____l____l____l____l____l____l____l____l____l____l____l____l

		.:: USERCOMMANDS ::.

		.:: +reg 		-- Displays information to become registered
		.:: +rules		-- Displays a listing of the hub rules.
		.:: +network	-- Displays hubs in network
	   ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____     
	  l____l____l____l____l____l____l____l____l____l____l____l____l____l____l____l

		.:: YOUR INFO ::.

		.:: hydrasec [ 105.237.238.xxx • 0.00 B ]
	   ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____     
	  l____l____l____l____l____l____l____l____l____l____l____l____l____l____l____l
	  
	 	Looking for an hublist use our Officel HubList it is available from:

		.:: http://thehublist.com/?do=hublist.xml.bz2
 		.:: http://thehublist.com/?do=hublist.config.bz2 (for DC++ clients older than 0.4033)

		Add Your Hub:
 		.:: htts://thehublist.com/?do=new

		Help:
		.:: http://thehublist.com/?do=help
	   ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____     
	  l____l____l____l____l____l____l____l____l____l____l____l____l____l____l____l
 
AfriGuy said:
Could very well be. There's a dip in throughput in the East specifically at the moment.
Monitoring looks good and I'm not seeing anything published on the Telkom noticeboard either. Odd. I'll see if I can do some digging quickly.
Click to expand...

In other words it's someone else's fault? The client or telkom's or something international but never Afrihost. Is that why you try hard to ask for tracerts and pings and when it shows it's lagging or timing out over your network you simply don't respond to those client?
 
NarcoticJ said:
In other words it's someone else's fault? The client or telkom's or something international but never Afrihost. Is that why you try hard to ask for tracerts and pings and when it shows it's lagging or timing out over your network you simply don't respond to those client?
Click to expand...

That's not what I'm saying at all :)
Always good to look at the data first and make decisions based off that data.
 
Really am about to give up ffs haven't been able to do more than 100kb/s today now tonight getting insane latency while trying to game.


Ping statistics for 188.165.200.200:
Packets: Sent = 956, Received = 801, Lost = 155 (16% loss),
Approximate round trip times in milli-seconds:
Minimum = 191ms, Maximum = 968ms, Average = 194ms
Control-C

C:\Users\admin>tracert 188.165.200.200

Tracing route to ns345728.ip-188-165-200.eu [188.165.200.200]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 * * 11 ms 41.181.222.101
4 12 ms 11 ms 11 ms 41.181.222.102
5 10 ms 11 ms 12 ms tb-dca-2.za--qux-i.za.mtnbusiness.net [66.8.11.1
86]
6 11 ms 10 ms 10 ms unc-cpt-1.mtnns.net [196.44.18.8]
7 198 ms 199 ms * 196.44.29.53
8 198 ms 197 ms 196 ms caxtn-indust-1--jp-ad-1-a.mtnns.net [209.212.98.
30]
9 242 ms 197 ms 198 ms 41.181.245.178
10 170 ms 170 ms 169 ms 41.181.190.197
11 191 ms 189 ms 192 ms 41.181.245.187
12 * * * Request timed out.
13 171 ms 170 ms 170 ms rbx-g2-a9.fr.eu [94.23.122.78]
14 208 ms 209 ms 207 ms vss-3-6k.routers.ovh.net [213.251.130.77]
15 192 ms 192 ms 191 ms ns345728.ip-188-165-200.eu [188.165.200.200]

Trace complete.
 
Trying to download my Witcher 3 dlc, pathetic speeds, not trying a torrent version, well seeded, and speeds are 25% of the speed it should get. This file is only 4.25GB, and it will take e most of the day to download.
 
8-BALL said:
Really am about to give up ffs haven't been able to do more than 100kb/s today now tonight getting insane latency while trying to game.


Ping statistics for 188.165.200.200:
Packets: Sent = 956, Received = 801, Lost = 155 (16% loss),
Approximate round trip times in milli-seconds:
Minimum = 191ms, Maximum = 968ms, Average = 194ms
Control-C

C:\Users\admin>tracert 188.165.200.200

Tracing route to ns345728.ip-188-165-200.eu [188.165.200.200]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 * * 11 ms 41.181.222.101
4 12 ms 11 ms 11 ms 41.181.222.102
5 10 ms 11 ms 12 ms tb-dca-2.za--qux-i.za.mtnbusiness.net [66.8.11.1
86]
6 11 ms 10 ms 10 ms unc-cpt-1.mtnns.net [196.44.18.8]
7 198 ms 199 ms * 196.44.29.53
8 198 ms 197 ms 196 ms caxtn-indust-1--jp-ad-1-a.mtnns.net [209.212.98.
30]
9 242 ms 197 ms 198 ms 41.181.245.178
10 170 ms 170 ms 169 ms 41.181.190.197
11 191 ms 189 ms 192 ms 41.181.245.187
12 * * * Request timed out.
13 171 ms 170 ms 170 ms rbx-g2-a9.fr.eu [94.23.122.78]
14 208 ms 209 ms 207 ms vss-3-6k.routers.ovh.net [213.251.130.77]
15 192 ms 192 ms 191 ms ns345728.ip-188-165-200.eu [188.165.200.200]

Trace complete.
Click to expand...

Your latency seems mostly OK, though there are spikes that are concerning. We know that the production network is still showing signs of strain, and we're doing our best to improve performance while preserving low latency.

This will definitely be addresses finally when we change networks as Gian promised in his email.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X