Afrihost New Network Feedback - Part 2

Status
Not open for further replies.
AfriGuy said:
Hhmm, definitely shouldn't have any issues there.
From the results above, I assume your router is handling the DNS forwarding/ caching?
Click to expand...
Correct and I never have issues with YouTube. :)
 
scienide said:
correct and everything was fine till 18:30 :(
Click to expand...

Very odd.
Mind clearing that DNS cache, turning the router/ modem off for 5 mins and back on again?

Also, mind posting that video URL here so I can run some tests on that specific video?
 
that is why i just changed to another isp , as doing on the testing etc etc has been 30 odd minutes and stuff still buffers, change isp info , 5 minutes and can watch stuff without buffering again...

anyways...
 
scienide said:
that is why i just changed to another isp , as doing on the testing etc etc has been 30 odd minutes and stuff still buffers, change isp info , 5 minutes and can watch stuff without buffering again...

anyways...
Click to expand...

Could have been trying to pull content from a different source which saw the reduced through.
Do you have a Linux or OS X box to test with?
 
scienide said:
only ipad, or my phone.
did test on windows pc
Click to expand...

No worries.
What's that video URL? I'd like to run some tests on my end :)

Does your router have a network monitor for you to try and get the source IP for the content you're streaming?
 
AfriGuy said:
No worries.
What's that video URL? I'd like to run some tests on my end :)

Does your router have a network monitor for you to try and get the source IP for the content you're streaming?
Click to expand...

You should be able to go
Task manager > performance > open resource monitor > navigate to network > select process and tick it > all IP Addresses that that process is connecting to should be displayed + port + latency. (it's how I ping test League servers :p)
 
No issues my side with youtube or netflix. Is free time done?

Sigh now i have to use from my data :D
 
Johnatan56 said:
You should be able to go
Task manager > performance > open resource monitor > navigate to network > select process and tick it > all IP Addresses that that process is connecting to should be displayed + port + latency. (it's how I ping test League servers :p)
Click to expand...

Ah awesome dude, I did not know this :) I'm a complete Microsoft newb.
is this only good for Windows 10 or other variants too?
 
Evening starts and international ping is 40 to 50 ms higher as this morning
cf567e567401ac66ddfb064311741f8e.jpg
 
AfriGuy said:
Ah awesome dude, I did not know this :) I'm a complete Microsoft newb.
is this only good for Windows 10 or other variants too?
Click to expand...

Think W7 and maybe XP as well, remember using it on them as well. The performance monitor might look slightly different though, but Microsoft hasn't really changed the functionality since before XP.

The glory days of playing that diamond pushing game on one of the first Windows machines, that thing still worked till ~2012.
 
kohlhtor said:
Evening starts and international ping is 40 to 50 ms higher as this morning
Click to expand...

Mine and I'm not very far from you. :)

Code: 
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\Users\Lara>tracert 217.10.79.9

Tracing route to sipgate.de [217.10.79.9]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    24 ms    23 ms    23 ms  cpt-tx2.ip.adsl.co.za [169.1.5.81]
  4    24 ms    24 ms    23 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82]
  5    24 ms    23 ms    23 ms  cpt-net1.ip.adsl.co.za [169.1.5.128]
  6    17 ms    17 ms    16 ms  41.164.52.40
  7    48 ms    50 ms    51 ms  if-ae-7-0.tcore2.KLT-Cape-Town.as6453.net [41.206.165.25]
  8   230 ms   214 ms   218 ms  if-ae-2-2.tcore1.KLT-Cape-Town.as6453.net [41.206.164.253]
  9   196 ms   189 ms   176 ms  if-p-6.core2.PV9-Lisbon.as6453.net [41.206.164.6]
 10   204 ms   206 ms   210 ms  if-xe-0-0-0-2000.tcore1.PV9-Lisbon.as6453.net [80.231.158.1]
 11   199 ms   247 ms   221 ms  if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
 12   214 ms   217 ms   205 ms  if-ae-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.139.1]
 13   221 ms   220 ms   226 ms  if-ae-11-2.tcore1.L78-London.as6453.net [80.231.139.42]
 14   210 ms     *      185 ms  if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
 15   183 ms   184 ms   201 ms  195.219.83.102
 16   234 ms   220 ms   208 ms  ae-2-70.edge4.Frankfurt1.Level3.net [4.69.154.72]
 17   235 ms   226 ms   221 ms  ae-2-70.edge4.Frankfurt1.Level3.net [4.69.154.72]
 18     *      225 ms   228 ms  te2-2.c102.f.de.plusline.net [212.162.24.58]
 19   203 ms   212 ms   231 ms  82.98.102.13
 20   203 ms   211 ms   205 ms  82.98.98.250
 21   219 ms   218 ms   215 ms  212.19.42.26
 22   224 ms   206 ms   202 ms  sipgate.de [217.10.79.9]

Trace complete.
 
kohlhtor said:
Evening starts and international ping is 40 to 50 ms higher as this morning
-snip
Click to expand...

I believe you're in touch with our Critical Care team to work on a way forward with this.
Latency seems OK for me.

Code: 
HOST: Jeffs-Macbook.local         Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- er-8.ubnt                  0.0%    10    0.3   0.3   0.2   0.4   0.1
  2.|-- ???                       100.0    10    0.0   0.0   0.0   0.0   0.0
  3.|-- cpt-up1.ip.adsl.co.za     30.0%    10   16.4  18.0  16.4  19.4   1.1
  4.|-- cpt-up2.ip.adsl.co.za      0.0%    10   17.7  18.6  17.4  26.2   2.7
  5.|-- cpt-net1.ip.adsl.co.za     0.0%    10   17.7  18.4  16.3  22.0   1.6
  6.|-- 41.164.52.40               0.0%    10   19.0  18.2  17.5  19.2   0.6
  7.|-- if-ae-7-0.tcore2.klt-cape  0.0%    10   61.2  59.5  49.7  69.1   7.4
  8.|-- if-ae-2-2.tcore1.klt-cape  0.0%    10  206.8 216.0 206.8 225.0   5.9
  9.|-- if-ae-5-80.tcore2.pv9-lis  0.0%    10  206.9 205.6 198.1 215.0   6.3
 10.|-- if-ae-2-2.tcore1.pv9-lisb  0.0%    10  195.9 211.2 195.9 219.4   8.0
 11.|-- if-ae-1-3.tcore1.sv8-high  0.0%    10  199.5 212.3 199.5 218.5   6.7
 12.|-- if-ae-19-2.tcore2.l78-lon 30.0%    10  193.8 203.1 193.8 209.6   6.1
 13.|-- if-ae-2-2.tcore1.l78-lond  0.0%    10  192.5 200.6 190.6 208.0   6.1
 14.|-- if-ae-17-2.tcore1.ldn-lon  0.0%    10  203.0 205.7 190.3 228.8  12.4
 15.|-- 195.219.83.102             0.0%    10  201.6 205.6 189.3 218.4   8.5
 16.|-- ae-2-70.edge4.frankfurt1.  0.0%    10  212.1 213.5 197.9 222.6   7.3
 17.|-- ae-2-70.edge4.frankfurt1.  0.0%    10  217.0 214.2 198.8 220.7   7.8
 18.|-- te2-2.c102.f.de.plusline. 10.0%    10  214.5 213.5 197.7 223.7   7.2
 19.|-- 82.98.102.13              10.0%    10  206.2 219.5 206.2 227.4   6.8
 20.|-- 82.98.98.250              20.0%    10  210.0 219.6 210.0 226.1   5.6
 21.|-- 212.19.42.26              10.0%    10  231.1 215.7 199.0 231.1  10.2
 22.|-- sipgate.de                10.0%    10  209.1 218.8 209.1 229.2   6.5
 
Johnatan56 said:
Think W7 and maybe XP as well, remember using it on them as well. The performance monitor might look slightly different though, but Microsoft hasn't really changed the functionality since before XP.

The glory days of playing that diamond pushing game on one of the first Windows machines, that thing still worked till ~2012.
Click to expand...

This is awesome, adding to my book of knowledge. Thanks for sharing dude, much appreciated!!
 
AfriGuy said:
I believe you're in touch with our Critical Care team to work on a way forward with this.
Latency seems OK for me.

Code: 
HOST: Jeffs-Macbook.local         Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- er-8.ubnt                  0.0%    10    0.3   0.3   0.2   0.4   0.1
  2.|-- ???                       100.0    10    0.0   0.0   0.0   0.0   0.0
  3.|-- cpt-up1.ip.adsl.co.za     30.0%    10   16.4  18.0  16.4  19.4   1.1
  4.|-- cpt-up2.ip.adsl.co.za      0.0%    10   17.7  18.6  17.4  26.2   2.7
  5.|-- cpt-net1.ip.adsl.co.za     0.0%    10   17.7  18.4  16.3  22.0   1.6
  6.|-- 41.164.52.40               0.0%    10   19.0  18.2  17.5  19.2   0.6
  7.|-- if-ae-7-0.tcore2.klt-cape  0.0%    10   61.2  59.5  49.7  69.1   7.4
  8.|-- if-ae-2-2.tcore1.klt-cape  0.0%    10  206.8 216.0 206.8 225.0   5.9
  9.|-- if-ae-5-80.tcore2.pv9-lis  0.0%    10  206.9 205.6 198.1 215.0   6.3
 10.|-- if-ae-2-2.tcore1.pv9-lisb  0.0%    10  195.9 211.2 195.9 219.4   8.0
 11.|-- if-ae-1-3.tcore1.sv8-high  0.0%    10  199.5 212.3 199.5 218.5   6.7
 12.|-- if-ae-19-2.tcore2.l78-lon 30.0%    10  193.8 203.1 193.8 209.6   6.1
 13.|-- if-ae-2-2.tcore1.l78-lond  0.0%    10  192.5 200.6 190.6 208.0   6.1
 14.|-- if-ae-17-2.tcore1.ldn-lon  0.0%    10  203.0 205.7 190.3 228.8  12.4
 15.|-- 195.219.83.102             0.0%    10  201.6 205.6 189.3 218.4   8.5
 16.|-- ae-2-70.edge4.frankfurt1.  0.0%    10  212.1 213.5 197.9 222.6   7.3
 17.|-- ae-2-70.edge4.frankfurt1.  0.0%    10  217.0 214.2 198.8 220.7   7.8
 18.|-- te2-2.c102.f.de.plusline. 10.0%    10  214.5 213.5 197.7 223.7   7.2
 19.|-- 82.98.102.13              10.0%    10  206.2 219.5 206.2 227.4   6.8
 20.|-- 82.98.98.250              20.0%    10  210.0 219.6 210.0 226.1   5.6
 21.|-- 212.19.42.26              10.0%    10  231.1 215.7 199.0 231.1  10.2
 22.|-- sipgate.de                10.0%    10  209.1 218.8 209.1 229.2   6.5
Click to expand...
Hi Jeff ;) :D
 
LaraC said:
Mine and I'm not very far from you. :)

Code: 
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\Users\Lara>tracert 217.10.79.9

Tracing route to sipgate.de [217.10.79.9]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    24 ms    23 ms    23 ms  cpt-tx2.ip.adsl.co.za [169.1.5.81]
  4    24 ms    24 ms    23 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82]
  5    24 ms    23 ms    23 ms  cpt-net1.ip.adsl.co.za [169.1.5.128]
  6    17 ms    17 ms    16 ms  41.164.52.40
  7    48 ms    50 ms    51 ms  if-ae-7-0.tcore2.KLT-Cape-Town.as6453.net [41.206.165.25]
  8   230 ms   214 ms   218 ms  if-ae-2-2.tcore1.KLT-Cape-Town.as6453.net [41.206.164.253]
  9   196 ms   189 ms   176 ms  if-p-6.core2.PV9-Lisbon.as6453.net [41.206.164.6]
 10   204 ms   206 ms   210 ms  if-xe-0-0-0-2000.tcore1.PV9-Lisbon.as6453.net [80.231.158.1]
 11   199 ms   247 ms   221 ms  if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
 12   214 ms   217 ms   205 ms  if-ae-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.139.1]
 13   221 ms   220 ms   226 ms  if-ae-11-2.tcore1.L78-London.as6453.net [80.231.139.42]
 14   210 ms     *      185 ms  if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
 15   183 ms   184 ms   201 ms  195.219.83.102
 16   234 ms   220 ms   208 ms  ae-2-70.edge4.Frankfurt1.Level3.net [4.69.154.72]
 17   235 ms   226 ms   221 ms  ae-2-70.edge4.Frankfurt1.Level3.net [4.69.154.72]
 18     *      225 ms   228 ms  te2-2.c102.f.de.plusline.net [212.162.24.58]
 19   203 ms   212 ms   231 ms  82.98.102.13
 20   203 ms   211 ms   205 ms  82.98.98.250
 21   219 ms   218 ms   215 ms  212.19.42.26
 22   224 ms   206 ms   202 ms  sipgate.de [217.10.79.9]

Trace complete.
Click to expand...

But you using a different pop in cape town
mine is 169.1.5.105 | cpt-up1.ip.adsl.co.za
your pop is cpt-tx2.ip.adsl.co.za [169.1.5.81]
different pop for users my line is fine

Zertop's LineTool Results
Date/Time: Thu Sep 08 21:01:04 CEST 2016

Basic Report:

Your packet loss was 0%.
Your average ping was 22ms.
Your maximum ping was 23ms.

Looking at your average ping, your line seems to be running perfectly.
It seems that your maximum ping is also good. If there are any issues, they most probably lie with your ISP

Detailed Report:
Code: 
PING 155.239.255.250 (155.239.255.250): 56 data bytes
64 bytes from 155.239.255.250: icmp_seq=0 ttl=63 time=22.770 ms
64 bytes from 155.239.255.250: icmp_seq=1 ttl=63 time=22.332 ms
64 bytes from 155.239.255.250: icmp_seq=2 ttl=63 time=23.337 ms
64 bytes from 155.239.255.250: icmp_seq=3 ttl=63 time=22.541 ms
64 bytes from 155.239.255.250: icmp_seq=4 ttl=63 time=22.489 ms
64 bytes from 155.239.255.250: icmp_seq=5 ttl=63 time=22.518 ms
64 bytes from 155.239.255.250: icmp_seq=6 ttl=63 time=22.738 ms
64 bytes from 155.239.255.250: icmp_seq=7 ttl=63 time=22.996 ms
64 bytes from 155.239.255.250: icmp_seq=8 ttl=63 time=22.447 ms
64 bytes from 155.239.255.250: icmp_seq=9 ttl=63 time=22.238 ms
64 bytes from 155.239.255.250: icmp_seq=10 ttl=63 time=23.139 ms
64 bytes from 155.239.255.250: icmp_seq=11 ttl=63 time=22.658 ms
64 bytes from 155.239.255.250: icmp_seq=12 ttl=63 time=22.396 ms
64 bytes from 155.239.255.250: icmp_seq=13 ttl=63 time=22.184 ms
64 bytes from 155.239.255.250: icmp_seq=14 ttl=63 time=22.278 ms
64 bytes from 155.239.255.250: icmp_seq=15 ttl=63 time=22.188 ms
64 bytes from 155.239.255.250: icmp_seq=16 ttl=63 time=22.097 ms
64 bytes from 155.239.255.250: icmp_seq=17 ttl=63 time=22.278 ms
64 bytes from 155.239.255.250: icmp_seq=18 ttl=63 time=22.620 ms
64 bytes from 155.239.255.250: icmp_seq=19 ttl=63 time=22.461 ms
64 bytes from 155.239.255.250: icmp_seq=20 ttl=63 time=22.265 ms
64 bytes from 155.239.255.250: icmp_seq=21 ttl=63 time=22.566 ms
64 bytes from 155.239.255.250: icmp_seq=22 ttl=63 time=22.847 ms
64 bytes from 155.239.255.250: icmp_seq=23 ttl=63 time=22.606 ms
64 bytes from 155.239.255.250: icmp_seq=24 ttl=63 time=22.630 ms
64 bytes from 155.239.255.250: icmp_seq=25 ttl=63 time=23.322 ms
64 bytes from 155.239.255.250: icmp_seq=26 ttl=63 time=22.796 ms
64 bytes from 155.239.255.250: icmp_seq=27 ttl=63 time=21.879 ms
64 bytes from 155.239.255.250: icmp_seq=28 ttl=63 time=22.964 ms
64 bytes from 155.239.255.250: icmp_seq=29 ttl=63 time=21.986 ms

--- 155.239.255.250 ping statistics ---
30 packets transmitted, 30 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 21.879/22.552/23.337/0.358 ms
 
AfriGuy said:
I believe you're in touch with our Critical Care team to work on a way forward with this.
Latency seems OK for me.

Code: 
HOST: Jeffs-Macbook.local         Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- er-8.ubnt                  0.0%    10    0.3   0.3   0.2   0.4   0.1
  2.|-- ???                       100.0    10    0.0   0.0   0.0   0.0   0.0
  3.|-- cpt-up1.ip.adsl.co.za     30.0%    10   16.4  18.0  16.4  19.4   1.1
  4.|-- cpt-up2.ip.adsl.co.za      0.0%    10   17.7  18.6  17.4  26.2   2.7
  5.|-- cpt-net1.ip.adsl.co.za     0.0%    10   17.7  18.4  16.3  22.0   1.6
  6.|-- 41.164.52.40               0.0%    10   19.0  18.2  17.5  19.2   0.6
  7.|-- if-ae-7-0.tcore2.klt-cape  0.0%    10   61.2  59.5  49.7  69.1   7.4
  8.|-- if-ae-2-2.tcore1.klt-cape  0.0%    10  206.8 216.0 206.8 225.0   5.9
  9.|-- if-ae-5-80.tcore2.pv9-lis  0.0%    10  206.9 205.6 198.1 215.0   6.3
 10.|-- if-ae-2-2.tcore1.pv9-lisb  0.0%    10  195.9 211.2 195.9 219.4   8.0
 11.|-- if-ae-1-3.tcore1.sv8-high  0.0%    10  199.5 212.3 199.5 218.5   6.7
 12.|-- if-ae-19-2.tcore2.l78-lon 30.0%    10  193.8 203.1 193.8 209.6   6.1
 13.|-- if-ae-2-2.tcore1.l78-lond  0.0%    10  192.5 200.6 190.6 208.0   6.1
 14.|-- if-ae-17-2.tcore1.ldn-lon  0.0%    10  203.0 205.7 190.3 228.8  12.4
 15.|-- 195.219.83.102             0.0%    10  201.6 205.6 189.3 218.4   8.5
 16.|-- ae-2-70.edge4.frankfurt1.  0.0%    10  212.1 213.5 197.9 222.6   7.3
 17.|-- ae-2-70.edge4.frankfurt1.  0.0%    10  217.0 214.2 198.8 220.7   7.8
 18.|-- te2-2.c102.f.de.plusline. 10.0%    10  214.5 213.5 197.7 223.7   7.2
 19.|-- 82.98.102.13              10.0%    10  206.2 219.5 206.2 227.4   6.8
 20.|-- 82.98.98.250              20.0%    10  210.0 219.6 210.0 226.1   5.6
 21.|-- 212.19.42.26              10.0%    10  231.1 215.7 199.0 231.1  10.2
 22.|-- sipgate.de                10.0%    10  209.1 218.8 209.1 229.2   6.5
Click to expand...

I send this to
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X