Afrihost New Network Feedback

AfriGuy · Oct 27, 2015

Trace route look fine. Is it only people in Cape Town and Durban who are affected?

Code:

Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\Users\Lara>tracert google.com

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

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    31 ms    30 ms    31 ms  cpt-tx2.ip.adsl.co.za [169.1.5.81]
  4    25 ms    24 ms    24 ms  cpt-rx1.ip.adsl.co.za [169.1.5.94]
  5    30 ms    30 ms    30 ms  cpt-net1.ip.adsl.co.za [169.1.5.128]
  6    24 ms    24 ms    24 ms  41.164.52.40
  7    51 ms    51 ms    51 ms  172.18.1.162
  8    46 ms    45 ms    46 ms  72.14.194.206
  9    46 ms    46 ms    46 ms  72.14.237.239
 10    51 ms    51 ms    50 ms  jnb01s07-in-f14.1e100.net [216.58.223.14]

Trace complete.

Does seem like it, seems intermittent at best at this stage.

AfriGuy · Oct 27, 2015

We've updated our noticeboard.
https://www.afrihost.com/site/network_status?src=website_nav#tabs

We’re experiencing an ADSL network routing problem affecting the routes our ADSL traffic takes between our Northern, Southern and Eastern Point Of Presence.

Our network team is working expeditiously to optimize and improve the routing problem.
Our clients in Eastern and Southern regions may see an increase in latency from local Content Delivery Networks as we work to resolve the routing problem.

We sincerely apologise to affected clients for any inconvenience this may cause.

Tren · Oct 27, 2015

AfriGuy said:
You can just paste the text results, much quicker

C:\>ping 8.8.8.8 -t

Pinging 8.8.8.8 with 32 bytes of data:

Reply from 8.8.8.8: bytes=32 time=481ms TTL=55
Reply from 8.8.8.8: bytes=32 time=642ms TTL=55
Reply from 8.8.8.8: bytes=32 time=455ms TTL=55
Reply from 8.8.8.8: bytes=32 time=875ms TTL=55
Reply from 8.8.8.8: bytes=32 time=653ms TTL=55
Reply from 8.8.8.8: bytes=32 time=568ms TTL=55
Reply from 8.8.8.8: bytes=32 time=580ms TTL=55
Reply from 8.8.8.8: bytes=32 time=790ms TTL=55
Reply from 8.8.8.8: bytes=32 time=731ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1073ms TTL=55
Reply from 8.8.8.8: bytes=32 time=644ms TTL=55
Reply from 8.8.8.8: bytes=32 time=612ms TTL=55
Reply from 8.8.8.8: bytes=32 time=584ms TTL=55
Reply from 8.8.8.8: bytes=32 time=829ms TTL=55
Reply from 8.8.8.8: bytes=32 time=594ms TTL=55
Reply from 8.8.8.8: bytes=32 time=503ms TTL=55
Reply from 8.8.8.8: bytes=32 time=627ms TTL=55
Reply from 8.8.8.8: bytes=32 time=648ms TTL=55
Reply from 8.8.8.8: bytes=32 time=326ms TTL=55
Reply from 8.8.8.8: bytes=32 time=450ms TTL=55
Reply from 8.8.8.8: bytes=32 time=409ms TTL=55
Reply from 8.8.8.8: bytes=32 time=283ms TTL=55
Reply from 8.8.8.8: bytes=32 time=529ms TTL=55
Reply from 8.8.8.8: bytes=32 time=400ms TTL=55
Reply from 8.8.8.8: bytes=32 time=692ms TTL=55
Reply from 8.8.8.8: bytes=32 time=517ms TTL=55
Reply from 8.8.8.8: bytes=32 time=467ms TTL=55
Reply from 8.8.8.8: bytes=32 time=557ms TTL=55
Reply from 8.8.8.8: bytes=32 time=444ms TTL=55

Ping statistics for 8.8.8.8:
Packets: Sent = 29, Received = 29, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 283ms, Maximum = 1073ms, Average = 584ms
Control-C
^C

savage · Oct 27, 2015

ADSL Network Routing Medium Impact 00:05, 28 Oct 2015
We’re experiencing an ADSL network routing problem affecting the routes our ADSL traffic takes between our Northern, Southern and Eastern Point Of Presence.
Our network team is working expeditiously to optimize and improve the routing problem.
Our clients in Eastern and Southern regions may see an increase in latency from local Content Delivery Networks as we work to resolve the routing problem.
We sincerely apologise to affected clients for any inconvenience this may cause.

See, BITCHING and MOANING, is the only way to get you, Afrihost, to do anything....

Amazing, how your own network monitoring doesn't pick something like this up, but again, we as customers, must sit here screaming left, right, and center before you will listen...

LaraC · Oct 27, 2015

AfriGuy said:
Does seem like it, seems intermittent at best at this stage.

I have a few minutes, any other test I could help with?

AfriGuy · Oct 27, 2015

Tren said:
C:\>ping 8.8.8.8 -t

Pinging 8.8.8.8 with 32 bytes of data:

Reply from 8.8.8.8: bytes=32 time=481ms TTL=55
Reply from 8.8.8.8: bytes=32 time=642ms TTL=55
Reply from 8.8.8.8: bytes=32 time=455ms TTL=55
Reply from 8.8.8.8: bytes=32 time=875ms TTL=55
Reply from 8.8.8.8: bytes=32 time=653ms TTL=55
Reply from 8.8.8.8: bytes=32 time=568ms TTL=55
Reply from 8.8.8.8: bytes=32 time=580ms TTL=55
Reply from 8.8.8.8: bytes=32 time=790ms TTL=55
Reply from 8.8.8.8: bytes=32 time=731ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1073ms TTL=55
Reply from 8.8.8.8: bytes=32 time=644ms TTL=55
Reply from 8.8.8.8: bytes=32 time=612ms TTL=55
Reply from 8.8.8.8: bytes=32 time=584ms TTL=55
Reply from 8.8.8.8: bytes=32 time=829ms TTL=55
Reply from 8.8.8.8: bytes=32 time=594ms TTL=55
Reply from 8.8.8.8: bytes=32 time=503ms TTL=55
Reply from 8.8.8.8: bytes=32 time=627ms TTL=55
Reply from 8.8.8.8: bytes=32 time=648ms TTL=55
Reply from 8.8.8.8: bytes=32 time=326ms TTL=55
Reply from 8.8.8.8: bytes=32 time=450ms TTL=55
Reply from 8.8.8.8: bytes=32 time=409ms TTL=55
Reply from 8.8.8.8: bytes=32 time=283ms TTL=55
Reply from 8.8.8.8: bytes=32 time=529ms TTL=55
Reply from 8.8.8.8: bytes=32 time=400ms TTL=55
Reply from 8.8.8.8: bytes=32 time=692ms TTL=55
Reply from 8.8.8.8: bytes=32 time=517ms TTL=55
Reply from 8.8.8.8: bytes=32 time=467ms TTL=55
Reply from 8.8.8.8: bytes=32 time=557ms TTL=55
Reply from 8.8.8.8: bytes=32 time=444ms TTL=55

Ping statistics for 8.8.8.8:
Packets: Sent = 29, Received = 29, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 283ms, Maximum = 1073ms, Average = 584ms
Control-C
^C

Woah, very high pings here

Will have our team check this out.

AfriGuy · Oct 27, 2015

LaraC said:
I have a few minutes, any other test I could help with?

I'd just try pinging Google services, gmail.com 8.8.8.8 or google.co.za - seems to be mostly affected by this

Thanks for offering to help, really is appreciated!

LaraC · Oct 27, 2015

Tren said:
Ping statistics for 8.8.8.8:
Packets: Sent = 29, Received = 29, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 283ms, Maximum = 1073ms, Average = 584ms
Control-C
^C

Comparative post.

Code:

Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\Users\Lara>ping 8.8.8.8 -t

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=52ms TTL=57
Reply from 8.8.8.8: bytes=32 time=51ms TTL=57
Reply from 8.8.8.8: bytes=32 time=50ms TTL=57
Reply from 8.8.8.8: bytes=32 time=51ms TTL=57
Reply from 8.8.8.8: bytes=32 time=51ms TTL=57
Reply from 8.8.8.8: bytes=32 time=50ms TTL=57
Reply from 8.8.8.8: bytes=32 time=51ms TTL=57
Reply from 8.8.8.8: bytes=32 time=51ms TTL=57
Reply from 8.8.8.8: bytes=32 time=51ms TTL=57
Reply from 8.8.8.8: bytes=32 time=51ms TTL=57
Reply from 8.8.8.8: bytes=32 time=51ms TTL=57
Reply from 8.8.8.8: bytes=32 time=51ms TTL=57
Reply from 8.8.8.8: bytes=32 time=51ms TTL=57
Reply from 8.8.8.8: bytes=32 time=50ms TTL=57
Reply from 8.8.8.8: bytes=32 time=51ms TTL=57
Reply from 8.8.8.8: bytes=32 time=51ms TTL=57
Reply from 8.8.8.8: bytes=32 time=57ms TTL=57

Ping statistics for 8.8.8.8:
    Packets: Sent = 17, Received = 17, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 50ms, Maximum = 57ms, Average = 51ms
Control-C
^C

LaraC · Oct 27, 2015

AfriGuy said:
I'd just try pinging Google services, gmail.com 8.8.8.8 or google.co.za - seems to be mostly affected by this
Thanks for offering to help, really is appreciated!

Gmail ping.

Code:

Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\Users\Lara>ping gmail.com

Pinging gmail.com [216.58.223.5] with 32 bytes of data:
Reply from 216.58.223.5: bytes=32 time=47ms TTL=57
Reply from 216.58.223.5: bytes=32 time=46ms TTL=57
Reply from 216.58.223.5: bytes=32 time=46ms TTL=57
Reply from 216.58.223.5: bytes=32 time=45ms TTL=57

Ping statistics for 216.58.223.5:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 45ms, Maximum = 47ms, Average = 46ms

AfriGuy · Oct 27, 2015

LaraC said:

Gmail ping.

Code:

Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\Users\Lara>ping gmail.com

Pinging gmail.com [216.58.223.5] with 32 bytes of data:
Reply from 216.58.223.5: bytes=32 time=47ms TTL=57
Reply from 216.58.223.5: bytes=32 time=46ms TTL=57
Reply from 216.58.223.5: bytes=32 time=46ms TTL=57
Reply from 216.58.223.5: bytes=32 time=45ms TTL=57

Ping statistics for 216.58.223.5:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 45ms, Maximum = 47ms, Average = 46ms

Thanks! Looks pretty stable for you.

How's everyone else's results looking to gmail.com?

savage · Oct 27, 2015

C:\Users\Chris Knipe>tracert outlook.office365.com

Tracing route to outlook-emeasouth.office365.com [132.245.56.98]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms vl101.wbtg-cn01-cs01.opticnetworks.corp [198.19.255.33]
2 77 ms 68 ms 49 ms 169-0-62-1.ip.afrihost.co.za [169.0.62.1]
3 1563 ms 969 ms * cpt-up1.ip.adsl.co.za [169.1.5.105]
4 29 ms 20 ms 24 ms cpt-in1.ip.adsl.co.za [169.1.5.118]
5 60 ms 60 ms 35 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 70 ms 93 ms 53 ms 41.164.52.40
7 369 ms 348 ms 413 ms microsoft.ct1.napafrica.net [196.10.140.47]
8 893 ms 687 ms 463 ms ae7-0.lon04-96cbe-1a.ntwk.msn.net [191.234.82.143]
9 604 ms 670 ms 559 ms be-9-0.ibr01.dbb.network.microsoft.com [104.44.4.134]
10

*yawn*

It must be my DNS, yes?

AfriGuy · Oct 27, 2015

Seeing better results from monitoring, our tests and some results pasted here.
Our network team will continue to monitor and update the noticeboard on any changes.

I'll be back tomorrow morning to check up on things.

If you want to submit any urgent results you can do so via our Support team on support@afrihost.com.

Tren · Oct 27, 2015

Pinging gmail.com [216.58.223.5] with 32 bytes of data:

Reply from 216.58.223.5: bytes=32 time=520ms TTL=55
Reply from 216.58.223.5: bytes=32 time=372ms TTL=55
Reply from 216.58.223.5: bytes=32 time=403ms TTL=55
Reply from 216.58.223.5: bytes=32 time=318ms TTL=55
Reply from 216.58.223.5: bytes=32 time=357ms TTL=55
Reply from 216.58.223.5: bytes=32 time=378ms TTL=55
Reply from 216.58.223.5: bytes=32 time=317ms TTL=55
Reply from 216.58.223.5: bytes=32 time=303ms TTL=55
Reply from 216.58.223.5: bytes=32 time=375ms TTL=55
Reply from 216.58.223.5: bytes=32 time=295ms TTL=55
Reply from 216.58.223.5: bytes=32 time=507ms TTL=55
Reply from 216.58.223.5: bytes=32 time=413ms TTL=55
Reply from 216.58.223.5: bytes=32 time=164ms TTL=55

Ping statistics for 216.58.223.5:
Packets: Sent = 13, Received = 13, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 164ms, Maximum = 520ms, Average = 363ms
Control-C

LaraC · Oct 27, 2015

savage said:
*yawn*

It must be my DNS, yes?

Our routes aren't the same.

Code:

Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\Users\Lara>tracert outlook.office365.com

Tracing route to outlook-emeasouth.office365.com [132.245.61.210]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    23 ms    24 ms    23 ms  cpt-tx2.ip.adsl.co.za [169.1.5.81]
  4    18 ms    16 ms    17 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82]
  5    23 ms    33 ms    22 ms  cpt-net1.ip.adsl.co.za [169.1.5.128]
  6    17 ms    17 ms    17 ms  41.164.52.40
  7    37 ms    36 ms    36 ms  microsoft.ct1.napafrica.net [196.10.140.47]
  8   181 ms   180 ms   181 ms  ae7-0.lon04-96cbe-1a.ntwk.msn.net [191.234.82.143]
  9     *      184 ms     *     ae12-0.lon04-96cbe-1b.ntwk.msn.net [207.46.44.163]
 10   193 ms   193 ms     *     ae11-0.pra-96cbe-1a.ntwk.msn.net [191.234.85.181]
 11   203 ms   203 ms   203 ms  ae2-0.vie-96cbe-1b.ntwk.msn.net [191.234.82.52]
 12   203 ms   203 ms   203 ms  10.104.26.111
 13   203 ms   203 ms   203 ms  10.60.129.153
 14   207 ms   206 ms   206 ms  10.60.136.1
 15   209 ms   203 ms   203 ms  10.60.9.1
 16   208 ms   208 ms   207 ms  132.245.61.210

Trace complete.

LaraC · Oct 27, 2015

AfriGuy said:
Seeing better results from monitoring, our tests and some results pasted here.
Our network team will continue to monitor and update the noticeboard on any changes.

I'll be back tomorrow morning to check up on things.

If you want to submit any urgent results you can do so via our Support team on support@afrihost.com.

Goodnight, I'm off too.

standerr · Oct 27, 2015

Code:

ping 8.8.8.8 -t

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=411ms TTL=57
Reply from 8.8.8.8: bytes=32 time=204ms TTL=57
Reply from 8.8.8.8: bytes=32 time=219ms TTL=57
Reply from 8.8.8.8: bytes=32 time=211ms TTL=57
Reply from 8.8.8.8: bytes=32 time=265ms TTL=57
Reply from 8.8.8.8: bytes=32 time=314ms TTL=57
Reply from 8.8.8.8: bytes=32 time=534ms TTL=57
Reply from 8.8.8.8: bytes=32 time=488ms TTL=57
Reply from 8.8.8.8: bytes=32 time=178ms TTL=57
Reply from 8.8.8.8: bytes=32 time=328ms TTL=57
Reply from 8.8.8.8: bytes=32 time=200ms TTL=57
Reply from 8.8.8.8: bytes=32 time=178ms TTL=57

Ping statistics for 8.8.8.8:
    Packets: Sent = 12, Received = 12, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 178ms, Maximum = 534ms, Average = 294ms

AfriMan · Oct 28, 2015

Morning Everyone

Just waiting for an update from the network team from last night's issue in the South.

Anyone still seeing poor results at the moment?

Zertop · Oct 28, 2015

AfriMan said:
Morning Everyone

Just waiting for an update from the network team from last night's issue in the South.

Anyone still seeing poor results at the moment?

Seems better

savage · Oct 28, 2015

Tracing route to outlook-emeasouth.office365.com [191.234.225.162]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms vl101.wbtg-cn01-cs01.opticnetworks.corp [198.19.255.33]
2 4 ms 4 ms 4 ms 169-0-62-1.ip.afrihost.co.za [169.0.62.1]
3 323 ms 6 ms 6 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 7 ms 7 ms 6 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
5 6 ms 5 ms 6 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 6 ms 6 ms 7 ms 41.164.52.40
7 742 ms 583 ms 562 ms microsoft.ct1.napafrica.net [196.10.140.47]
8 701 ms 665 ms 557 ms ae7-0.lon04-96cbe-1a.ntwk.msn.net [191.234.82.143]
9 597 ms 684 ms 652 ms

C:\Users\Chris Knipe>tracert www.google.com

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

1 <1 ms <1 ms <1 ms vl101.wbtg-cn01-cs01.opticnetworks.corp [198.19.255.33]
2 4 ms 4 ms 4 ms 169-0-62-1.ip.afrihost.co.za [169.0.62.1]
3 * * * Request timed out.
4 7 ms 6 ms 6 ms cpt-in1.ip.adsl.co.za [169.1.5.118]
5 6 ms 5 ms 5 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 6 ms 5 ms 6 ms 41.164.52.40
7 27 ms 28 ms 27 ms 172.18.1.162
8 458 ms 472 ms 554 ms 72.14.194.206
9 * 426 ms 391 ms 72.14.239.129
10 * 428 ms 362 ms jnb01s08-in-f4.1e100.net [216.58.223.36]

Trace complete.

latency still all over the place...

savage · Oct 28, 2015

Tracing route to www.news24.com [41.86.110.200]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms vl101.wbtg-cn01-cs01.opticnetworks.corp [198.19.255.33]
2 4 ms 4 ms 3 ms 169-0-62-1.ip.afrihost.co.za [169.0.62.1]
3 2834 ms 2313 ms 2327 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 7 ms 6 ms 6 ms cpt-in1.ip.adsl.co.za [169.1.5.118]
5 6 ms 5 ms 6 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 6 ms 6 ms 6 ms 41.164.52.40
7 7 ms 6 ms 7 ms 172.18.32.33
8 8 ms 8 ms 8 ms mweb.cinx.net.za [196.223.22.32]
9 1339 ms 532 ms 554 ms te0-0-0-1.cpt-p-1.optinet.net [197.84.7.1]
10 412 ms 469 ms 686 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
11 646 ms 600 ms 430 ms

woohooo

Afrihost New Network Feedback

Afrihost

Afrihost

Member

Expert Member

Honorary Master

Afrihost

Afrihost

Honorary Master

Honorary Master

Afrihost

Expert Member

Afrihost

Member

Honorary Master

Honorary Master

Well-Known Member

Afrihost Representative

Expert Member

Expert Member

Expert Member