Web Squad ISP

Status
Not open for further replies.
@websquadza any update on the "area" problem in Roodepoort/Little Falls/Radiokop?

My twitch has been buffering non-stop this afternoon, very frustrating.
 
Was just about to ask if there is an issue, vuma trenched randburg, because my twitch is also unwatchable :( Enjoying a gaming podcast at 160p tho :')
 
Noticed I'm getting around 140 ms to São Paulo in Apex Legends,

So that's Singapore, London, Mainland Europe, São Paulo, all we need now is North America, the final frontier :)
 
@websquadza any update on the "area" problem in Roodepoort/Little Falls/Radiokop?

My twitch has been buffering non-stop this afternoon, very frustrating.
Was just about to ask if there is an issue, vuma trenched randburg, because my twitch is also unwatchable :( Enjoying a gaming podcast at 160p tho :')
Apologies for the late reply. Seems twitch specific. We’ve looked at the inbound paths and escalated to the affected transit upstream. They’re investigating and will let us know what they find.
 
Noticed I'm getting around 140 ms to São Paulo in Apex Legends,

So that's Singapore, London, Mainland Europe, São Paulo, all we need now is North America, the final frontier :)
Some SACS bound capacity has been introduced - we’re monitoring this closely for the time being.
 
Apologies for the late reply. Seems twitch specific. We’ve looked at the inbound paths and escalated to the affected transit upstream. They’re investigating and will let us know what they find.

Hi,

Any update on this? Twitch was unwatchable for me over the weekend, ended up using a mobile device and using my backup vodacom mobile data.
 
Hi,

Any update on this? Twitch was unwatchable for me over the weekend, ended up using a mobile device and using my backup vodacom mobile data.
Can I ask you to please update your ticket with an MTR. We’ve been back and forth and it’s been isolated to a specific set of OLTs. Any recent results do help.
 
Can I ask you to please update your ticket with an MTR. We’ve been back and forth and it’s been isolated to a specific set of OLTs. Any recent results do help.
1646675443573.png

Twitch has been fine all day, buffering like mad since around 1900, having to use a VPN to get any stability on it :(
 
Twitch home page is hosted locally on fastly CDN. Content (video feed) is derived from various sources though. Not seeing any issues on transit paths. Will see if we can pick up anything.
You talking about the ttvnw.net domain?

Target Name: video-edge-c87cba.mia05.abs.hls.ttvnw.net
IP: 99.181.101.187
Date/Time: 2022/03/07 20:23:43 - 2022/03/07 20:33:43

Hop Sent PL% Min Max Avg Host Name / [IP]
1 7 100 0 0 0 [-]
2 7 0 6,22 22,09 10,75 as-vuma.jb-is-pld-01.za.ws.net.za [160.119.228.1]
3 6 0 4,93 67,17 17,79 160.119.224.102 [160.119.224.102]
4 7 0 1,84 3,96 2,54 core.cr-xe-01.jb1.za.ws.net.za [160.119.224.89]
5 7 0 2,04 5,16 3,22 core.pe-xe-ip01.jb1.za.ws.net.za [160.119.224.18]
6 7 0 2,80 6,99 4,34 gi0-0-1-0.agr11.jnb01.atlas.cogentco.com [206.249.0.201]
7 7 0 2,79 4,78 3,69 be2355.ccr51.jnb01.atlas.cogentco.com [154.54.43.37]
8 7 0 178,76 188,66 182,38 be2485.ccr21.lon01.atlas.cogentco.com [154.54.88.205]
9 7 0 160,36 173,83 164,31 be2871.ccr42.lon13.atlas.cogentco.com [154.54.58.185]
10 7 0 228,20 249,36 233,12 be2490.ccr42.jfk02.atlas.cogentco.com [154.54.42.85]
11 7 0 227,59 241,67 231,37 be2271.rcr21.ewr01.atlas.cogentco.com [154.54.83.166]
12 7 100 0 0 0 video-edge-c87cba.mia05.abs.hls.ttvnw.net [99.181.101.187]

Seems to be fine again now, but will keep an eye out and do a trace to the video-edge of the affected stream
 
Last edited:
You talking about the ttvnw.net domain?

Target Name: video-edge-c87cba.mia05.abs.hls.ttvnw.net
IP: 99.181.101.187
Date/Time: 2022/03/07 20:23:43 - 2022/03/07 20:33:43

Hop Sent PL% Min Max Avg Host Name / [IP]
1 7 100 0 0 0 [-]
2 7 0 6,22 22,09 10,75 as-vuma.jb-is-pld-01.za.ws.net.za [160.119.228.1]
3 6 0 4,93 67,17 17,79 160.119.224.102 [160.119.224.102]
4 7 0 1,84 3,96 2,54 core.cr-xe-01.jb1.za.ws.net.za [160.119.224.89]
5 7 0 2,04 5,16 3,22 core.pe-xe-ip01.jb1.za.ws.net.za [160.119.224.18]
6 7 0 2,80 6,99 4,34 gi0-0-1-0.agr11.jnb01.atlas.cogentco.com [206.249.0.201]
7 7 0 2,79 4,78 3,69 be2355.ccr51.jnb01.atlas.cogentco.com [154.54.43.37]
8 7 0 178,76 188,66 182,38 be2485.ccr21.lon01.atlas.cogentco.com [154.54.88.205]
9 7 0 160,36 173,83 164,31 be2871.ccr42.lon13.atlas.cogentco.com [154.54.58.185]
10 7 0 228,20 249,36 233,12 be2490.ccr42.jfk02.atlas.cogentco.com [154.54.42.85]
11 7 0 227,59 241,67 231,37 be2271.rcr21.ewr01.atlas.cogentco.com [154.54.83.166]
12 7 100 0 0 0 video-edge-c87cba.mia05.abs.hls.ttvnw.net [99.181.101.187]

Seems to be fine again now, but will keep an eye out and do a trace to the video-edge of the affected stream

Yup. These are the origin servers for streams. Changes based on source and number of viewers. Looks like this stream is from a US server; but our tcp accelerator generally compensates for these higher latencies. I’ve asked the team to check it out.
 
Yup. These are the origin servers for streams. Changes based on source and number of viewers. Looks like this stream is from a US server; but our tcp accelerator generally compensates for these higher latencies. I’ve asked the team to check it out.
Ok, as soon as you said US I realized that the US streamers I watch are totally fine and the EU ones are the buffering culprits, anyway here is trace for an iffy EU stream (been fine now, but it was one that was buffering earlier)

Target Name: live004-ttvnw.akamaized.net
IP: 197.80.130.137
Date/Time: 2022/03/07 20:37:07 - 2022/03/07 20:47:07

Hop Sent PL% Min Max Avg Host Name / [IP]
1 16 44 0,33 2,28 0,64 192.168.1.1 [192.168.1.1]
2 18 0 2,29 14,31 4,55 as-vuma.jb-is-pld-01.za.ws.net.za [160.119.228.1]
3 18 22 2,65 70,02 22,00 160.119.224.102 [160.119.224.102]
4 18 0 1,60 4,70 2,58 core.cr-xe-01.jb1.za.ws.net.za [160.119.224.89]
5 18 0 1,65 10,64 3,58 core.pe-xe-ix01.jb1.za.ws.net.za [160.119.224.17]
6 18 0 2,25 8,13 4,42 optinet.ixp.joburg [196.60.8.120]
7 18 0 3,39 83,06 9,13 197-80-4-96.jhb.mweb.co.za [197.80.4.96]
8 18 0 3,12 79,06 9,50 197-80-5-61.jhb.mweb.co.za [197.80.5.61]
9 18 0 2,90 71,79 8,40 bu-ether2.mca-pe-1.optinet.net [197.80.4.225]
10 18 0 2,84 65,66 8,60 bu-ether3.vic-pe-1.optinet.net [197.80.4.36]
11 18 0 3,91 62,18 13,05 101.te0-0-2-2.vic-pe-13.optinet.net [197.80.7.13]
12 18 0 2,56 132,04 11,16 live004-ttvnw.akamaized.net [197.80.130.137]
 
Ok, as soon as you said US I realized that the US streamers I watch are totally fine and the EU ones are the buffering culprits, anyway here is trace for an iffy EU stream (been fine now, but it was one that was buffering earlier)

Target Name: live004-ttvnw.akamaized.net
IP: 197.80.130.137
Date/Time: 2022/03/07 20:37:07 - 2022/03/07 20:47:07

Hop Sent PL% Min Max Avg Host Name / [IP]
1 16 44 0,33 2,28 0,64 192.168.1.1 [192.168.1.1]
2 18 0 2,29 14,31 4,55 as-vuma.jb-is-pld-01.za.ws.net.za [160.119.228.1]
3 18 22 2,65 70,02 22,00 160.119.224.102 [160.119.224.102]
4 18 0 1,60 4,70 2,58 core.cr-xe-01.jb1.za.ws.net.za [160.119.224.89]
5 18 0 1,65 10,64 3,58 core.pe-xe-ix01.jb1.za.ws.net.za [160.119.224.17]
6 18 0 2,25 8,13 4,42 optinet.ixp.joburg [196.60.8.120]
7 18 0 3,39 83,06 9,13 197-80-4-96.jhb.mweb.co.za [197.80.4.96]
8 18 0 3,12 79,06 9,50 197-80-5-61.jhb.mweb.co.za [197.80.5.61]
9 18 0 2,90 71,79 8,40 bu-ether2.mca-pe-1.optinet.net [197.80.4.225]
10 18 0 2,84 65,66 8,60 bu-ether3.vic-pe-1.optinet.net [197.80.4.36]
11 18 0 3,91 62,18 13,05 101.te0-0-2-2.vic-pe-13.optinet.net [197.80.7.13]
12 18 0 2,56 132,04 11,16 live004-ttvnw.akamaized.net [197.80.130.137]
Surprised to see Akamai’s cache behind Optinet serving this content. Nice to see Twitch investing in local relays, but not sure why they’ve chosen this specific location (rather than Akamai’s own cache behind Akamai’s own peering). These servers are notoriously problematic (think DSTV Now) and prone to congestion.
 
Surprised to see Akamai’s cache behind Optinet serving this content. Nice to see Twitch investing in local relays, but not sure why they’ve chosen this specific location (rather than Akamai’s own cache behind Akamai’s own peering). These servers are notoriously problematic (think DSTV Now) and prone to congestion.
This is really interesting.
 
  • Like
Reactions: Yuu
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X