Smokeping favour from someone?

Forums › Vetta and Quic › Smokeping favour from someone?

timwelch

93 posts

Master Geek
+1 received by user: 14

#312225 28-Mar-2024 07:48

Any chance I can get someone with a Smokeping instance to add a host and monitor it for 10 days or so?

I've been listening to a streaming radio station in the UK for the last couple of years without issue but in the last month it's become unusable. The packet loss to this one specific host seems to be my issue but it would be great to have it confirmed.

My Smokeping target entry is...

++ TMM
menu = The Music Machine
title = TMM Radio | msmn3.co
host = msmn3.co

The actual steam is https://msmn3.co/proxy/x1mp31/stream

I contacted them directly but they are unaware of any issues their end but other hosts they own / run appear to work fine such as https://msmn8.co/proxy/cx128mp3/stream

Any assistance greatly appreciated.

Cheers, Tim

Smokeping

This is a filtered page: currently showing replies marked as answers. Click here to see full discussion.

saf

221 posts

Master Geek
+1 received by user: 533

ID Verified

Trusted

Vetta Group

Subscriber

#3211777 28-Mar-2024 08:46

Out of interest, I ran an MTR for a 100 pings...

HOST:                                      Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- [redacted]                          0.0%   100    0.5   0.4   0.2   0.7   0.1
  2.|-- [redacted]                          0.0%   100    1.1   1.0   0.7   1.5   0.2
  3.|-- ae1-chc4.vetta.net                  0.0%   100    4.1   4.3   3.8   4.9   0.3
  4.|-- pe1-chc4.vetta.net                  0.0%   100    4.8   4.5   3.9   9.0   0.7
  5.|-- 100.126.0.16                        0.0%   100   19.5  19.0  18.2  20.4   0.3
  6.|-- ???                                100.0   100    0.0   0.0   0.0   0.0   0.0
  7.|-- ???                                100.0   100    0.0   0.0   0.0   0.0   0.0
  8.|-- unknown.telstraglobal.net           0.0%   100   43.1  43.3  42.6  50.5   0.8
  9.|-- i-90.sydp-core03.telstraglobal.net  0.0%   100   45.4  44.5  43.0  47.2   0.7
 10.|-- i-90.sydp-core03.telstraglobal.net  0.0%   100  162.3 161.7 160.3 165.6   1.0
 11.|-- 202.84.138.90                       0.0%   100  162.1 161.8 160.2 163.4   0.7
 12.|-- 202.84.157.37                       0.0%   100  162.4 177.4 160.6 253.7  27.3
 13.|-- ae1-206.rt.iad.hkg.cn.retn.net      6.0%   100  295.8 184.2 163.0 297.2  46.9
 14.|-- ae1-7.RT.TC2.LON.UK.retn.net        7.0%   100  430.5 327.0 298.2 450.4  44.5
 15.|-- GW-SharpStream.retn.net             2.0%   100  439.1 340.1 311.3 464.9  52.5
 16.|-- 91.193.244.24.sharp-stream.com      3.0%   100  450.0 344.9 318.2 453.2  50.7
 17.|-- 91.193.246.163.sharp-stream.com     7.0%   100  441.9 331.8 311.2 446.0  47.4

Seems to be loss gets introduced into the path around hop #13 once traffic enters the retn.net network.
Unfortunately this isn't a direct upstream of Quic/Vetta so hands are somewhat tied to a degree, depending on how the route is presented to us. It may be possible we to traffic engineer around it depending on what BGP communities we could get our hands on, and what alternative paths are available, but will need to discuss with our network guys.

My views are as unique as a unicorn riding a unicycle. They do not reflect the opinions of my employer, my cat, or the sentient coffee machine in the break room.

saf

221 posts

Master Geek
+1 received by user: 533

ID Verified

Trusted

Vetta Group

Subscriber

#3212167 29-Mar-2024 20:14

I have had a bit of a look for you, and my poke around does hint to add weight to what @Lias has mentioned above.

There are a significant number of submarine cables cut currently between Asia and Europe. With this happening, carriers and providers are being forced to use paths with less capacity, or temporary measures in order to keep packets flowing, which causes congestion on the remaining paths that are working - but hey, moving most packets is better than no packets!

Fixing these cables is proving especially challenging, moreso than normal due to the instability in the region, needing military escorts and defense etc.

Doing some digging, it does look like RETN and/or their provider are striking this problem, which matches both in terms of the traffic path, and explains differences in time of day based on when the working path they're using is congested.

We have already completed some traffic engineering changes a month or so ago in order to route around points of significant congestion due to all the above with the elements we have control over, however we can't fix every path to everywhere, as we can't control the whole path to the remote destination.

My views are as unique as a unicorn riding a unicycle. They do not reflect the opinions of my employer, my cat, or the sentient coffee machine in the break room.