Vox Telecom Fatpipe

cvanwie said:
3rd hop is Telkom upland vlan to our network. Can't see second hop which is where I bet the latency starts, same as AntiGanda.
Click to expand...
That's what I was thinking as well, which is why I said it's not a Vox issue and wanted to show the same thing happens even when switching ISP.
 
Tonight again at almost on the stroke of midnight when the free period starts, my gaming ping jumps to 205 from 171 and the lag is suddenly intense. It remains rock solid from that point at 203-204.

Is this a result of a large number of customers downloading and a lack of load capacity?
 
Good morning guys, did those Fatpipe + Bolt on have any further trouble yesterday?

(Not talking about Fatpipe Lite + Bolt on)
 
Fixed all the Fatpipe + Bolt on accounts.

I've run a mass fix on the list of customers affected. If you are still "capped" and believe that you shouldn't be, please reconnect to the internet and check again. If you are still capped, please let me know in my inbox.

Regards,
Chris
_____________________________

Chris Van Wie
Solution Architect
Vox Telecom Limited
 
Any update with regards to the terrible latency in the evenings in the western cape?
 
ghostR said:
Any update with regards to the terrible latency in the evenings in the western cape?
Click to expand...

Nothing worth while.

Last night, we showed Telkom:

Code: 
Tracing route to www.mybroadband.co.za [190.93.240.55]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2   283 ms   252 ms   216 ms  dsl-197-245-124-1.voxdsl.co.za [197.245.124.1]
  3   247 ms   225 ms   256 ms  41.193.121.9
  4   251 ms   274 ms   228 ms  41.193.121.10
  5   244 ms   184 ms   229 ms  209.203.1.41
  6   273 ms   276 ms   288 ms  africainx.ct1.napafrica.net [196.10.140.7]
  7   309 ms   256 ms   323 ms  CORE.GP-ID-DCE-3.TO.GP-ID-MEC-2.AINX.P2P.10G.za
[41.84.13.228]
  8    26 ms    25 ms    30 ms  41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africa
inx.net [41.66.181.59]
  9    67 ms    26 ms    26 ms  190.93.240.55

Trace complete.

and while on Axxess:

Code: 
Tracing route to www.mybroadband.co.za [190.93.241.55]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2   251 ms   307 ms   261 ms  105-236-14-193-esr-lo.mtnbusiness.co.za [105.236
.14.193]
  3     *        *     3543 ms  41.181.222.101
  4   402 ms   364 ms     *     41.181.222.102
  5   247 ms   210 ms   257 ms  tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
  6   281 ms   232 ms   238 ms  unc-cpt-1.mtnns.net [196.44.18.8]
  7   260 ms   140 ms   230 ms  196.44.31.106
  8   159 ms   104 ms   146 ms  nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121
]
  9   142 ms   125 ms   112 ms  africainx.cinx.net.za [196.223.22.47]
 10   218 ms   279 ms   285 ms  CORE.GP-ID-DCE-3.TO.GP-ID-MEC-2.AINX.P2P.10G.za
[41.84.13.228]
 11   248 ms     *      340 ms  41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africa
inx.net [41.66.181.59]
 12   100 ms    79 ms    86 ms  190.93.241.55

Trace complete.

And Telkom's reply:

Telkom: Had a look at the line and DSLam and in all honesty see no reason for the increased latency, as per below graph the unit is not congesting. (graph has no threshold identified and goes up to 120M and maxes at 100... doesn't even have a label as to what it's related to)

We are escalating again.

SMH.
 
cvanwie said:
Nothing worth while.

Last night, we showed Telkom:

Code: 
Tracing route to www.mybroadband.co.za [190.93.240.55]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2   283 ms   252 ms   216 ms  dsl-197-245-124-1.voxdsl.co.za [197.245.124.1]
  3   247 ms   225 ms   256 ms  41.193.121.9
  4   251 ms   274 ms   228 ms  41.193.121.10
  5   244 ms   184 ms   229 ms  209.203.1.41
  6   273 ms   276 ms   288 ms  africainx.ct1.napafrica.net [196.10.140.7]
  7   309 ms   256 ms   323 ms  CORE.GP-ID-DCE-3.TO.GP-ID-MEC-2.AINX.P2P.10G.za
[41.84.13.228]
  8    26 ms    25 ms    30 ms  41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africa
inx.net [41.66.181.59]
  9    67 ms    26 ms    26 ms  190.93.240.55

Trace complete.

and while on Axxess:

Code: 
Tracing route to www.mybroadband.co.za [190.93.241.55]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2   251 ms   307 ms   261 ms  105-236-14-193-esr-lo.mtnbusiness.co.za [105.236
.14.193]
  3     *        *     3543 ms  41.181.222.101
  4   402 ms   364 ms     *     41.181.222.102
  5   247 ms   210 ms   257 ms  tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
  6   281 ms   232 ms   238 ms  unc-cpt-1.mtnns.net [196.44.18.8]
  7   260 ms   140 ms   230 ms  196.44.31.106
  8   159 ms   104 ms   146 ms  nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121
]
  9   142 ms   125 ms   112 ms  africainx.cinx.net.za [196.223.22.47]
 10   218 ms   279 ms   285 ms  CORE.GP-ID-DCE-3.TO.GP-ID-MEC-2.AINX.P2P.10G.za
[41.84.13.228]
 11   248 ms     *      340 ms  41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africa
inx.net [41.66.181.59]
 12   100 ms    79 ms    86 ms  190.93.241.55

Trace complete.

And Telkom's reply:

Telkom: Had a look at the line and DSLam and in all honesty see no reason for the increased latency, as per below graph the unit is not congesting. (graph has no threshold identified and goes up to 120M and maxes at 100... doesn't even have a label as to what it's related to)

We are escalating again.

SMH.
Click to expand...

How many people are experiencing the increased latency? just a few or many?
 
ghostR said:
Okay well then it wouldn't be specific to one or a few DSLAM which rules out DSLAM congestion.
Click to expand...

NetOps just escalated offering to send engineers from JHB to CPT to work with Telkom directly since things aren't working over FQ.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X