New Webafrica Network Migration

scud said:
WA is sending conflicting emails about the move

Is there a way to tell if you have been migrated , like new up range ?
Click to expand...


The indication to confirm the connection has been successfully migrated would be the speed test showing WEBAFRICA-NETWORKS

The IP range for our Vumatel customers will start with 102. etc
 
WebAfrica Helper said:
Awesome! - reported your feedback to the engineers monitoring the migration and connection traffic :)
Click to expand...

Yeah not the place but you can tell the team they ****ed up again. My voice is not working again and error message is "Authentication failure" when making voice calls.
And as my previous comments I am going to log a call and I guess I will get an engineer is looking into the issue and the ticket gets closed instantly.

Will keep you posted........WebAfrica VOIP and support sucks
 
Hellhound105 said:
@WebAfrica Helper - Is the new Public IPs static or will they change? I was happily using the service for 6 months and today I have a new IP?
Click to expand...

The migration will cause a once off IP update to a range that starts with 102. - once the IP has been updated , the new IP assigned will be fixed to your connection going forward on the new network
 
Hellhound105 said:
Yeah not the place but you can tell the team they ****ed up again. My voice is not working again and error message is "Authentication failure" when making voice calls.
And as my previous comments I am going to log a call and I guess I will get an engineer is looking into the issue and the ticket gets closed instantly.

Will keep you posted........WebAfrica VOIP and support sucks
Click to expand...

Please confirm the ticket ref# via DM
 
cAv said:
I am in Northcliff (Johannesburg via Vumatel) I was migrated late yesterday or somewhere overnight. The process seems to have gone through smoothly enough and the speed throughput currently seems to be there and there abouts. The question I have though is that if I use Speedtest it picks up the nearest server as Bloemfontein (?). When I use this server to test I get 1ms response but if I change and test on Johannesburg - Web Africa I get 20ms?
Click to expand...
@WebAfrica Helper - can you comment on this? There is something strange with the routing on the new network...
 
cAv said:
@WebAfrica Helper - can you comment on this? There is something strange with the routing on the new network...
Click to expand...


:unsure::unsure:
We have reached out to the speedtest.net - their connection distribution locators do take some time to update - they will update soon and resolve this issue

Thank you for this feedback though - will make sure they are informed to get this sorted asap - thanks again
 
Hellhound105 said:
Will do, in a few minutes, just awaiting to see if they close the new ticket again.
Click to expand...

The VoIP authentication issue has been reported to be resolved a few days ago, the moment we isolated this issue, it was investigated and restored.

We're on standby for your ticket ref# via DM

Thank you for your time, efforts and updates @Hellhound105 :thumbsup:. We are doing all we can to make sure the migration has a minimal end-user impact (the entire mission was none at all) - your feedback helps us improve. #WeLiveandWeLearn :)
 
WebAfrica Helper said:
:unsure::unsure:
We have reached out to the speedtest.net - their connection distribution locators do take some time to update - they will update soon and resolve this issue

Thank you for this feedback though - will make sure they are informed to get this sorted asap - thanks again
Click to expand...
Thanks but what of the latency aspect? The latency seems to indicate that the traffic is being routed to Cape Town and back?
 
cAv said:
Thanks but what of the latency aspect? The latency seems to indicate that the traffic is being routed to Cape Town and back?
Click to expand...

Escalated this to the engineers monitoring the migration - thank you for this feedback
 
WebAfrica Helper said:
The VoIP authentication issue has been reported to be resolved a few days ago, the moment we isolated this issue, it was investigated and restored.

We're on standby for your ticket ref# via DM

Thank you for your time, efforts and updates @Hellhound105 :thumbsup:. We are doing all we can to make sure the migration has a minimal end-user impact (the entire mission was none at all) - your feedback helps us improve. #WeLiveandWeLearn:)
Click to expand...

I get you, will send it now, but the thing went down this morning - Same as last month. Will send the Ticket ref now.
 
cAv said:
Thanks but what of the latency aspect? The latency seems to indicate that the traffic is being routed to Cape Town and back?
Click to expand...
Can you add a traceroute? Needs to be a TCP traceroute to port 80. I see winmtr can't do this. Have a look at this link to see how to do this on windows: https://support.opendns.com/hc/en-us/articles/227989007-How-to-Running-a-TCP-Traceroute

From cape town it looks like this:
Code: 
~ % mtr speedtest.jhb.webafrica.co.za --tcp --port 80 --report-wide --show-ips
Start: 2019-06-27T10:45:40+0200
HOST: turbot                                                  Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- router.lan (192.168.241.1)                               0.0%    10    0.4   0.9   0.4   1.3   0.3
  2.|-- 102-65-57-1.ftth.web.africa (102.65.57.1)                0.0%    10    2.6   3.4   2.6   4.0   0.4
  3.|-- 197.97.90.130                                            0.0%    10    3.6   4.6   3.1  12.2   2.8
  4.|-- 160.119.142.33                                           0.0%    10    1.7   2.0   1.5   2.3   0.3
  5.|-- 102.67.178.13                                            0.0%    10    2.3   2.1   1.1   2.6   0.4
  6.|-- 100.67.57.8                                              0.0%    10    4.6   8.9   2.4  62.5  18.8
  7.|-- 102.67.178.3                                             0.0%    10    2.1   2.2   1.4   4.4   0.8
  8.|-- 196-10-140-126.ixp.capetown (196.10.140.126)             0.0%    10    2.3   3.0   2.3   3.5   0.3
  9.|-- mi-za-cpt-p7-te0-7-0-0.ip.isnet.net (168.209.2.12)       0.0%    10    3.2   3.2   2.7   3.7   0.3
 10.|-- mi-za-cpt-p7-te-0-0-1-1-141.ip.isnet.net (168.209.0.69)  0.0%    10   18.4  18.3  17.6  18.6   0.3
 11.|-- core1-pkl-tg0-7-0-0.ip.isnet.net (168.209.1.162)         0.0%    10   18.7  21.6  18.6  29.0   3.9
 12.|-- 168.209.100.145                                          0.0%    10   25.7  19.3  17.9  25.7   2.4
 13.|-- speedtest.jhb.webafrica.co.za (197.97.195.120)           0.0%    10   18.3  18.3  17.5  18.5   0.3
 
Tinuva said:
Can you add a traceroute? Needs to be a TCP traceroute to port 80. I see winmtr can't do this. Have a look at this link to see how to do this on windows: https://support.opendns.com/hc/en-us/articles/227989007-How-to-Running-a-TCP-Traceroute

From cape town it looks like this:
Code: 
~ % mtr speedtest.jhb.webafrica.co.za --tcp --port 80 --report-wide --show-ips
Start: 2019-06-27T10:45:40+0200
HOST: turbot                                                  Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- router.lan (192.168.241.1)                               0.0%    10    0.4   0.9   0.4   1.3   0.3
  2.|-- 102-65-57-1.ftth.web.africa (102.65.57.1)                0.0%    10    2.6   3.4   2.6   4.0   0.4
  3.|-- 197.97.90.130                                            0.0%    10    3.6   4.6   3.1  12.2   2.8
  4.|-- 160.119.142.33                                           0.0%    10    1.7   2.0   1.5   2.3   0.3
  5.|-- 102.67.178.13                                            0.0%    10    2.3   2.1   1.1   2.6   0.4
  6.|-- 100.67.57.8                                              0.0%    10    4.6   8.9   2.4  62.5  18.8
  7.|-- 102.67.178.3                                             0.0%    10    2.1   2.2   1.4   4.4   0.8
  8.|-- 196-10-140-126.ixp.capetown (196.10.140.126)             0.0%    10    2.3   3.0   2.3   3.5   0.3
  9.|-- mi-za-cpt-p7-te0-7-0-0.ip.isnet.net (168.209.2.12)       0.0%    10    3.2   3.2   2.7   3.7   0.3
10.|-- mi-za-cpt-p7-te-0-0-1-1-141.ip.isnet.net (168.209.0.69)  0.0%    10   18.4  18.3  17.6  18.6   0.3
11.|-- core1-pkl-tg0-7-0-0.ip.isnet.net (168.209.1.162)         0.0%    10   18.7  21.6  18.6  29.0   3.9
12.|-- 168.209.100.145                                          0.0%    10   25.7  19.3  17.9  25.7   2.4
13.|-- speedtest.jhb.webafrica.co.za (197.97.195.120)           0.0%    10   18.3  18.3  17.5  18.5   0.3
Click to expand...
Here you go.
Code: 
Tracing route to 197.97.195.120 [speedtest.jhb.webafrica.co.za] on port 80
Over a maximum of 30 hops.
1       1 ms    0 ms    0 ms    192.168.51.92
2       1 ms    1 ms    1 ms    102.65.108.1    [102-65-108-1.ftth.web.africa]
3       2 ms    2 ms    2 ms    197.97.90.1
4       66 ms   53 ms   72 ms   102.65.64.33    [102-65-64-33.ftth.web.africa]
5       60 ms   86 ms   65 ms   100.66.109.232
6       72 ms   68 ms   73 ms   102.67.177.7
7       84 ms   76 ms   88 ms   196.60.8.126    [is.ixp.joburg]
8       83 ms   78 ms   87 ms   168.209.1.163   [core2-pkl-t0-7-0-0.ip.isnet.net]
9       62 ms   82 ms   77 ms   168.209.100.145
10      Destination Reached in 76 ms. Connection established to 197.97.195.120
Trace Complete.
 
cAv said:
Here you go.
Code: 
Tracing route to 197.97.195.120 [speedtest.jhb.webafrica.co.za] on port 80
Over a maximum of 30 hops.
1       1 ms    0 ms    0 ms    192.168.51.92
2       1 ms    1 ms    1 ms    102.65.108.1    [102-65-108-1.ftth.web.africa]
3       2 ms    2 ms    2 ms    197.97.90.1
4       66 ms   53 ms   72 ms   102.65.64.33    [102-65-64-33.ftth.web.africa]
5       60 ms   86 ms   65 ms   100.66.109.232
6       72 ms   68 ms   73 ms   102.67.177.7
7       84 ms   76 ms   88 ms   196.60.8.126    [is.ixp.joburg]
8       83 ms   78 ms   87 ms   168.209.1.163   [core2-pkl-t0-7-0-0.ip.isnet.net]
9       62 ms   82 ms   77 ms   168.209.100.145
10      Destination Reached in 76 ms. Connection established to 197.97.195.120
Trace Complete.
Click to expand...


Thank you @cAv and @Tinuva
 
cAv said:
Here you go.
Code: 
Tracing route to 197.97.195.120 [speedtest.jhb.webafrica.co.za] on port 80
Over a maximum of 30 hops.
1       1 ms    0 ms    0 ms    192.168.51.92
2       1 ms    1 ms    1 ms    102.65.108.1    [102-65-108-1.ftth.web.africa]
3       2 ms    2 ms    2 ms    197.97.90.1
4       66 ms   53 ms   72 ms   102.65.64.33    [102-65-64-33.ftth.web.africa]
5       60 ms   86 ms   65 ms   100.66.109.232
6       72 ms   68 ms   73 ms   102.67.177.7
7       84 ms   76 ms   88 ms   196.60.8.126    [is.ixp.joburg]
8       83 ms   78 ms   87 ms   168.209.1.163   [core2-pkl-t0-7-0-0.ip.isnet.net]
9       62 ms   82 ms   77 ms   168.209.100.145
10      Destination Reached in 76 ms. Connection established to 197.97.195.120
Trace Complete.
Click to expand...
Yup there is something wrong there. You will now have to wait for WAHelper to get it escalated.
 
cAv said:
Here you go.
Code: 
Tracing route to 197.97.195.120 [speedtest.jhb.webafrica.co.za] on port 80
Over a maximum of 30 hops.
1       1 ms    0 ms    0 ms    192.168.51.92
2       1 ms    1 ms    1 ms    102.65.108.1    [102-65-108-1.ftth.web.africa]
3       2 ms    2 ms    2 ms    197.97.90.1
4       66 ms   53 ms   72 ms   102.65.64.33    [102-65-64-33.ftth.web.africa]
5       60 ms   86 ms   65 ms   100.66.109.232
6       72 ms   68 ms   73 ms   102.67.177.7
7       84 ms   76 ms   88 ms   196.60.8.126    [is.ixp.joburg]
8       83 ms   78 ms   87 ms   168.209.1.163   [core2-pkl-t0-7-0-0.ip.isnet.net]
9       62 ms   82 ms   77 ms   168.209.100.145
10      Destination Reached in 76 ms. Connection established to 197.97.195.120
Trace Complete.
Click to expand...

Please confirm your customer code via DM - already reported your the above test results to the network teams
 
I find download from Apple slow I’m from Port Elizabeth


ba72d4c51b92f467eaf0a96d3f27e0a0.jpg


e0e5a9f87554555bae03ed26b00a78bd.jpg
 
Last edited:
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X