Status
Not open for further replies.
Hi Bryn,

I have a Octotel/CISP 100/100 solution, and when uploading 7gig video file to OneDrive I get 7 MB/s.
I've tested it with App and also Browser. What I see, it doesn't go and stay at 7 MB/s it jump a-lot in the beginning.

On the pic you can see the server I'm connected to (removed all the other connections / focus on this one only).

So that Prefix, 13.107.6.0/24, is being advertised out of NAP CPT and NAP JHB. So the traffic should hop off in CPT straight to microsoft.

BGP routing table entry for 13.107.6.0/24, version 653143709
Paths: (17 available, best #10, table default)
Multipath: iBGP
Additional-path-install
Path advertised to update-groups:
16
Refresh Epoch 1
8075 8068

So Bryn just needs to confirm what IP his onedrive is going to to make sure it's going via NAP.
 
Does indeed go through Cape Town:

Code:
$ mtr 13.107.6.151 --report-wide --show-ips
Start: Thu Jan  4 20:45:38 2018
HOST: outlawstar                                         Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- router.heaven.za.net (192.168.241.1)                0.0%    10    0.2   0.3   0.2   0.4   0.0
  2.|-- 155.93.251.1                                        0.0%    10    1.2   3.2   1.1  21.3   6.3
  3.|-- 154.0.1.125                                         0.0%    10    0.9   1.1   0.9   1.4   0.0
  4.|-- 154.0.1.13                                          0.0%    10    1.2   1.5   1.2   3.1   0.5
  5.|-- microsoft.ixp.capetown (196.10.140.47)              0.0%    10    1.4   1.6   1.4   2.0   0.0
  6.|-- be-10-0.ibr01.lon30.ntwk.msn.net (104.44.5.102)     0.0%    10  164.3 147.5 144.4 164.3   5.9
  7.|-- ae62-0.lon04-96cbe-1b.ntwk.msn.net (104.44.9.245)   0.0%    10  180.7 148.0 142.9 180.7  12.0
  8.|-- ae3-0.lon21-96cbe-1a.ntwk.msn.net (198.206.164.68)  0.0%    10  144.5 151.7 143.6 206.9  19.6
  9.|-- ???                                                100.0    10    0.0   0.0   0.0   0.0   0.0
 10.|-- ???                                                100.0    10    0.0   0.0   0.0   0.0   0.0
 11.|-- ???                                                100.0    10    0.0   0.0   0.0   0.0   0.0
 12.|-- ???                                                100.0    10    0.0   0.0   0.0   0.0   0.0
 13.|-- 13.107.6.151                                        0.0%    10  144.3 144.4 143.9 146.6   0.7
 
Well Twitch streaming has pretty much gone to the dogs the past two nights....

Normally i use Milan as my ingest server and have minimal dropped frames due to network/internet. But the past two nights have been horrible having over 20% drops

https://i.imgur.com/hwfHu2m.png
https://i.imgur.com/NgCcNN2.png

Generally i get 10,000+ kbps to Milan, Italy (As it's the only server that uses a different route once it hits EU)
Also Mexico is normally very close too 10,000+ kbps
As well as Lima, Peru which also readyly goes to 10,000+ kbps

Really expected CoolIdeas to at least figure out the EU issue by now seen as they have said they peer directly with twitch in London, Which would make one assume that the london ingest server would be perfect yet i have never seen the connection go above 3500 kbps which is just far too low for HD streaming.

Vumatel Trenched - Durbanville
100mbps up / 100mbps down
 
Well Twitch streaming has pretty much gone to the dogs the past two nights....

Normally i use Milan as my ingest server and have minimal dropped frames due to network/internet. But the past two nights have been horrible having over 20% drops

https://i.imgur.com/hwfHu2m.png
https://i.imgur.com/NgCcNN2.png

Generally i get 10,000+ kbps to Milan, Italy (As it's the only server that uses a different route once it hits EU)
Also Mexico is normally very close too 10,000+ kbps
As well as Lima, Peru which also readyly goes to 10,000+ kbps

Really expected CoolIdeas to at least figure out the EU issue by now seen as they have said they peer directly with twitch in London, Which would make one assume that the london ingest server would be perfect yet i have never seen the connection go above 3500 kbps which is just far too low for HD streaming.

Vumatel Trenched - Durbanville
100mbps up / 100mbps down
Twitch performance seems to come and go without any changes from our side, we do peer with them in London which means that we get traffic there and back again. From there onward it's on their network. I'd give it a day or two and see if it resolves itself.
 
On 28/12 I reported to cool ideas that the cable connecting my house and the Vumatel pole is very loose Ticket ID: #COOL-20171228-65667 I got a SMS from Vuatel with reference no 35934 . Until now I got 3 phone calls from Vumatel asking me if a technician was here but no technician . Phone Vumatel they told me to wait after 10 minutes I hanged up .What should I do now ?
Will escalate your ref to Vumatels installs again.
 
giphy.gif


Damnit man, don't be telling me that. Nothing has worked at getting the speeds to not be a steaming turd.

Uploading from desktop gets like 4Mbps. Chrome is by far the fastest at 16Mbps.

I've been going back and forth with the built-in OneDrive support, and it's going nowehere. Just rubbish about disabling antivirus, clearing caches, trying other browsers etc. Nothing has done anything. Although interestingly, Edge is the slowest browser to upload with.

Edit: Scratch that - now I can only upload at 4Mbps to OneDrive from anywhere.
Yeah as mentioned we peer with MS in both JHB and CPT, once the traffic reaches the peering point we have no further visibility of the traffic. These services are designed for trickle ingress over a period of time and partial data retrieval on the fly. Not as a live drive so to speak.
 
Last edited:
Twitch performance seems to come and go without any changes from our side, we do peer with them in London which means that we get traffic there and back again. From there onward it's on their network. I'd give it a day or two and see if it resolves itself.

I do tend to agree, however, i feel like if it had to do with their network more people would be complaining about the issues globally, Not just restricted to South Africa. If that makes sense?

I assume the last hop before the twitch network in London is 154.0.3.106? because it constantly reports Destination net unreachable?
Which is weird because the Milan Servers does manage to trace all the way through, even past this IP.

Which is also weird, as it is all being routed through London should that be the case?

Milan

Code:
tracert Live-mil.Twitch.TV

Tracing route to live-mil.twitch.tv [178.255.155.139]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  172.18.7.225
  2     1 ms     1 ms     1 ms  155.93.251.1
  3    <1 ms    <1 ms    <1 ms  154.0.1.125
  4     1 ms     1 ms     1 ms  154.0.1.13
  5   141 ms   141 ms   141 ms  154.0.3.106
  6   142 ms   142 ms   142 ms  v1000.core1.lon3.he.net [216.66.80.169]
  7   142 ms   174 ms   143 ms  100ge14-1.core1.lon2.he.net [184.105.64.237]
  8   150 ms   205 ms   164 ms  100ge5-1.core1.par2.he.net [184.105.223.254]
  9   151 ms   150 ms   149 ms  seabone-net-as6762.10gigabitethernet8-19.core1.par2.he.net [216.66.83.126]
 10   178 ms   172 ms   174 ms  ae8.milano30.mil.seabone.net [195.22.192.191]
 11   172 ms   182 ms   169 ms  149.3.181.130
 12   176 ms   173 ms   169 ms  178.255.155.139

Trace complete.

London

Code:
 tracert Live-lhr.Twitch.TV

Tracing route to Live-lhr.Twitch.TV [52.223.194.212]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  172.18.7.225
  2     1 ms     1 ms     1 ms  155.93.251.1
  3     1 ms    <1 ms    <1 ms  154.0.1.125
  4     2 ms     1 ms     1 ms  154.0.1.13
  5   142 ms   141 ms   141 ms  154.0.3.106
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9  lhr01-br01.justin.tv [195.66.225.174]  reports: Destination net unreachable.

Trace complete.


Any thoughts on this?
 
I do tend to agree, however, i feel like if it had to do with their network more people would be complaining about the issues globally, Not just restricted to South Africa. If that makes sense?

I assume the last hop before the twitch network in London is 154.0.3.106? because it constantly reports Destination net unreachable?
Which is weird because the Milan Servers does manage to trace all the way through, even past this IP.

Which is also weird, as it is all being routed through London should that be the case?

Milan

Code:
tracert Live-mil.Twitch.TV

Tracing route to live-mil.twitch.tv [178.255.155.139]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  172.18.7.225
  2     1 ms     1 ms     1 ms  155.93.251.1
  3    <1 ms    <1 ms    <1 ms  154.0.1.125
  4     1 ms     1 ms     1 ms  154.0.1.13
  5   141 ms   141 ms   141 ms  154.0.3.106
  6   142 ms   142 ms   142 ms  v1000.core1.lon3.he.net [216.66.80.169]
  7   142 ms   174 ms   143 ms  100ge14-1.core1.lon2.he.net [184.105.64.237]
  8   150 ms   205 ms   164 ms  100ge5-1.core1.par2.he.net [184.105.223.254]
  9   151 ms   150 ms   149 ms  seabone-net-as6762.10gigabitethernet8-19.core1.par2.he.net [216.66.83.126]
 10   178 ms   172 ms   174 ms  ae8.milano30.mil.seabone.net [195.22.192.191]
 11   172 ms   182 ms   169 ms  149.3.181.130
 12   176 ms   173 ms   169 ms  178.255.155.139

Trace complete.

London

Code:
 tracert Live-lhr.Twitch.TV

Tracing route to Live-lhr.Twitch.TV [52.223.194.212]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  172.18.7.225
  2     1 ms     1 ms     1 ms  155.93.251.1
  3     1 ms    <1 ms    <1 ms  154.0.1.125
  4     2 ms     1 ms     1 ms  154.0.1.13
  5   142 ms   141 ms   141 ms  154.0.3.106
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9  lhr01-br01.justin.tv [195.66.225.174]  reports: Destination net unreachable.

Trace complete.


Any thoughts on this?
So the next hop after that point is on Twitches network, if that Twitch router doesn't allow ICMP it will report unreachable. Certain routers filter this out for security reasons. Globally there are lots of complaints, our only choice is to try drop the peer to Twitch and see if this improves anything which we have done before and didn't make any difference.
 
Let me check where those IPs originate from as they aren't using the peer.
 
I do tend to agree, however, i feel like if it had to do with their network more people would be complaining about the issues globally, Not just restricted to South Africa. If that makes sense?

I assume the last hop before the twitch network in London is 154.0.3.106? because it constantly reports Destination net unreachable?
Which is weird because the Milan Servers does manage to trace all the way through, even past this IP.

Which is also weird, as it is all being routed through London should that be the case?

Milan

Code:
tracert Live-mil.Twitch.TV

Tracing route to live-mil.twitch.tv [178.255.155.139]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  172.18.7.225
  2     1 ms     1 ms     1 ms  155.93.251.1
  3    <1 ms    <1 ms    <1 ms  154.0.1.125
  4     1 ms     1 ms     1 ms  154.0.1.13
  5   141 ms   141 ms   141 ms  154.0.3.106
  6   142 ms   142 ms   142 ms  v1000.core1.lon3.he.net [216.66.80.169]
  7   142 ms   174 ms   143 ms  100ge14-1.core1.lon2.he.net [184.105.64.237]
  8   150 ms   205 ms   164 ms  100ge5-1.core1.par2.he.net [184.105.223.254]
  9   151 ms   150 ms   149 ms  seabone-net-as6762.10gigabitethernet8-19.core1.par2.he.net [216.66.83.126]
 10   178 ms   172 ms   174 ms  ae8.milano30.mil.seabone.net [195.22.192.191]
 11   172 ms   182 ms   169 ms  149.3.181.130
 12   176 ms   173 ms   169 ms  178.255.155.139

Trace complete.

London

Code:
 tracert Live-lhr.Twitch.TV

Tracing route to Live-lhr.Twitch.TV [52.223.194.212]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  172.18.7.225
  2     1 ms     1 ms     1 ms  155.93.251.1
  3     1 ms    <1 ms    <1 ms  154.0.1.125
  4     2 ms     1 ms     1 ms  154.0.1.13
  5   142 ms   141 ms   141 ms  154.0.3.106
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9  lhr01-br01.justin.tv [195.66.225.174]  reports: Destination net unreachable.

Trace complete.


Any thoughts on this?

From that, Milan server goes over HurricanElectric, so not through the London peering. Different transit provider could help but not definite.

As for the London server, here is how the trace look: (reverse dns reveal its a reverse proxy, so there could be more traces in their network that we are not aware of)
Code:
$ mtr -T --port 80 --report-wide --show-ips 52.223.194.212 
Start: Thu Jan  4 21:39:20 2018
HOST: outlawstar                                                Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- router.heaven.za.net (192.168.241.1)                       0.0%    10    0.3   0.3   0.3   0.4   0.0
  2.|-- 155.93.251.1                                               0.0%    10    1.1   1.7   1.1   5.5   1.2
  3.|-- 154.0.1.125                                                0.0%    10    1.1   1.2   1.0   1.3   0.0
  4.|-- 154.0.1.13                                                 0.0%    10    1.5   1.4   1.2   1.9   0.0
  5.|-- 154.0.3.106                                                0.0%    10  141.8 142.0 141.8 142.6   0.0
  6.|-- lhr01-br01.justin.tv (195.66.225.174)                      0.0%    10  143.0 143.1 142.5 144.4   0.3
  7.|-- 10.26.52.138                                               0.0%    10  142.5 142.8 142.3 144.3   0.5
  8.|-- ingest-proxy-edge-c684cc.lhr03.justin.tv (52.223.194.212)  0.0%    10  250.5 245.6 200.5 250.6  15.8
Also revealing that latency jump inside their own network...
 
So the next hop after that point is on Twitches network, if that Twitch router doesn't allow ICMP it will report unreachable. Certain routers filter this out for security reasons. Globally there are lots of complaints, our only choice is to try drop the peer to Twitch and see if this improves anything which we have done before and didn't make any difference.

Yeah, i figured that's what was going on, at least in EU, Most servers outside the EU i can trace to no problem. But like i said, thought that was the issue indeed.

Good luck! Really hope we can come back with an idea of what to do!
 
Yeah, i figured that's what was going on, at least in EU, Most servers outside the EU i can trace to no problem. But like i said, thought that was the issue indeed.

Good luck! Really hope we can come back with an idea of what to do!

Yes so 178.255.155.139 is announced as, 178.255.155.0/24 which is announced by AS42473 which is why it wouldnt route via the twitch peer. Chances are they use an edge server on their network for that area.
 
Yes so 178.255.155.139 is announced as, 178.255.155.0/24 which is announced by AS42473 which is why it wouldnt route via the twitch peer. Chances are they use an edge server on their network for that area.

Ahhhhh, why didn't i think to have a look at that... haha, hmmm, so would seem to be the twitch network as the main culprit.
 
Ahhhhh, why didn't i think to have a look at that... haha, hmmm, so would seem to be the twitch network as the main culprit.
Too many factors to state but we have lots of capacity available at any given time to London so more than likely a 3rd party thing.
 
Ahhhhh, why didn't i think to have a look at that... haha, hmmm, so would seem to be the twitch network as the main culprit.

3Ls20Ut.png


Would assume your results are much better then what i can get. really anxious for Octotel to sort this out barely been using my Fibre this month vs last month
 
3Ls20Ut.png


Would assume your results are much better then what i can get. really anxious for Octotel to sort this out barely been using my Fibre this month vs last month

Ouch! Just try the lastest version of twitch test tho, might be the issue, although i doubt it.
 
Yeah as mentioned we peer with MS in both JHB and CPT, once the traffic reaches the peering point we have no further visibility of the traffic. These services are designed for trickle ingress over a period of time and partial data retrieval on the fly. Not as a live drive so to speak.

Trace route to OneDrive seems pretty dodge though?

Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                          setup.ubnt.com -    0 |   62 |   62 |    0 |    0 |    7 |    1 |
|                             192.168.2.1 -    0 |   62 |   62 |    0 |    0 |    5 |    1 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                            192.168.10.5 -    0 |   62 |   62 |   19 |   20 |   27 |   22 |
|                            192.168.11.6 -   93 |   13 |    1 |   15 |   15 |   15 |   15 |
|                  microsoft.ixp.capetown -   93 |   13 |    1 |   38 |   38 |   38 |   38 |
|        be-10-0.ibr01.lon30.ntwk.msn.net -   93 |   13 |    1 |  393 |  393 |  393 |  393 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
 
Trace route to OneDrive seems pretty dodge though?

Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                          setup.ubnt.com -    0 |   62 |   62 |    0 |    0 |    7 |    1 |
|                             192.168.2.1 -    0 |   62 |   62 |    0 |    0 |    5 |    1 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                            192.168.10.5 -    0 |   62 |   62 |   19 |   20 |   27 |   22 |
|                            192.168.11.6 -   93 |   13 |    1 |   15 |   15 |   15 |   15 |
|                  microsoft.ixp.capetown -   93 |   13 |    1 |   38 |   38 |   38 |   38 |
|        be-10-0.ibr01.lon30.ntwk.msn.net -   93 |   13 |    1 |  393 |  393 |  393 |  393 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Are you still using the USG? What host are you tracing to?
 
3Ls20Ut.png


Would assume your results are much better then what i can get. really anxious for Octotel to sort this out barely been using my Fibre this month vs last month
Which router are you using?
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X