Return-Path: Delivered-To: acongi@2etv-group.com Received: (qmail 19889 invoked by uid 503); 27 Jan 2015 23:04:18 -0000 Received: from unknown (HELO ?192.168.2.36?) (82.98.32.222) by ns303373.ovh.net with SMTP; 27 Jan 2015 23:04:18 -0000 From: "acongi@2etv-group.com" Content-Type: multipart/alternative; boundary=Apple-Mail-3--437262786 Date: Tue, 27 Jan 2015 23:50:52 +0100 Subject: To: support@llnw.com Message-Id: Mime-Version: 1.0 (Apple Message framework v1085) X-Mailer: Apple Mail (2.1085) --Apple-Mail-3--437262786 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 Bonjour, Pourriez-vous donner des r=E9ponses au probl=E8me que nous rapporte dans = l'email plus bas notre agent en Russie =E0 propos du signal HLS de = FrenchLover TV? Merci, Cdlt, Adolphe CONGI 2ETV GROUP 0686135974 >=20 > A client had reported issues with HLS delivery. They say it was ok at = the beginning, but started jittering on Dec the 24th. Bitrate drops from = time to time, picture freezes. They had tried to connect via various = backbone internet providers - it didn`t help. They had made a traceroute = to the Limelight`s server. It had shown, that it all seems to be ok on = the way from them to Ligmelight. Just 8 hops, and delays are reasonable. = The result of the traceroute shows that the problem is most likely on = the Limelight`s side. Here is the traceroute, it was made last week: >=20 > C: \ Users \ TV> tracert eetvgroup.vo.llnwd.net >=20 > Tracing route to eetvgroup.vo.llnwd.net [87.248.217.254] > maximum number of hops 30: >=20 > 1 <1 ms <1 ms <1 ms PPPoE-188.0.0.254-IP.RastrNET.RU [188.0.0.254] > 2 <1 ms <1 ms <1 ms 10.10.1.101 > 3 <1 ms <1 ms <1 ms kyk01.transtelecom.net [188.43.4.22] > 4 * * * timed request. > 5 ms 86 ms 83 90 ms netnod-ix-ge-b-sth-1500.llnw.com = [194.68.128.167] > 6105 ms 104 ms 104 ms tge6-4.fr3.frf.llnw.net [69.28.172.121] > 7108 ms 103 ms 103 ms ve5.fr4.frf.llnw.net [69.28.172.106] > 8 99 ms 99 ms 101 ms cdn-87-248-217-254.frf.llnw.net = [87.248.217.254] >=20 > Trace complete. >=20 > C: \ Users \ TV> ping eetvgroup.vo.llnwd.net -l -t 1000 >=20 > Pinging eetvgroup.vo.llnwd.net [87.248.217.254] 1000 bytes of data: > Response from 87.248.217.254: bytes =3D 1000 time =3D 97ms TTL =3D 59 > Response from 87.248.217.254: bytes =3D 1000 time =3D 138ms TTL =3D 59 > Response from 87.248.217.254: bytes =3D 1000 time =3D 122ms TTL =3D 59 > Response from 87.248.217.254: bytes =3D 1000 time =3D 97ms TTL =3D 59 > Response from 87.248.217.254: bytes =3D 1000 time =3D 97ms TTL =3D 59 > ~~~ > Statistics Ping to 87.248.217.254: > Package: Sent =3D 2459, received =3D 2459, lost =3D 0 > (0% loss) > Approximate round-trip time in milliseconds: > Minimum =3D 97msek, maximum =3D 221 ms, 109 ms average =3D > Control-C >=20 > Since it was ok at the beginning, they think that may be the traffic = had increased recently and Limelight`s server simply doesn`t have = enought resources to serve this traffic. May be it has to be retuned. --Apple-Mail-3--437262786 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1

A client had reported issues with HLS = delivery. They say it was ok at the beginning, but started jittering on = Dec the 24th. Bitrate drops from time to time, picture freezes. They had = tried to connect via various backbone internet providers - it didn`t = help. They had made a traceroute to the Limelight`s server. It had = shown, that it all seems to be ok on the way from them to Ligmelight. = Just 8 hops, and delays are reasonable. The result of the traceroute = shows that the problem is most likely on the Limelight`s side. Here is = the traceroute, it was made last week:

C: \ Users \ TV> tracert eetvgroup.vo.llnwd.net
<= div dir=3D"ltr">

Tracing route to eetvgroup.vo.llnwd.net [87.248.217.254]
maximum number of hops 30:

1 <1 ms <1 ms <1 = ms PPPoE-188.0.0.254-IP.RastrNET.RU [188.0.0.254]<= /div>
2 <1 ms <1 ms <1 ms = 10.10.1.101
3 <1 ms <1 ms <1 = ms kyk01.transtelecom.net [188.43.4.22]
4 * * * timed = request.
5 ms 86 ms 83 90 ms netnod-ix-ge-b-sth-1500.llnw.com [194.68.128.16= 7]
6105 ms 104 ms 104 ms tge6-4.fr3.frf.llnw.net [69.28.172.121]
7108 ms 103 ms 103 ms ve5.fr4.frf.llnw.net [69.28.172.106]
8 99 ms 99 ms 101 ms cdn-87-248-217-254.frf.llnw.net [87.248.217.254= ]

Trace = complete.

C: \ Users \ TV> = ping eetvgroup.vo.llnwd.net -l -t = 1000

Pinging eetvgroup.vo.llnwd.net [87.248.217.254] 1000 = bytes of data:
Response from 87.248.217.254: = bytes =3D 1000 time =3D 97ms TTL =3D 59
Response from 87.248.217.254: = bytes =3D 1000 time =3D 138ms TTL =3D = 59
Response from 87.248.217.254: = bytes =3D 1000 time =3D 122ms TTL =3D = 59
Response from 87.248.217.254: = bytes =3D 1000 time =3D 97ms TTL =3D 59
Response from 87.248.217.254: = bytes =3D 1000 time =3D 97ms TTL =3D 59
~~~
Statistics Ping to 87.248.217.254:
= Package: Sent =3D 2459, received =3D 2459, lost =3D = 0
(0% = loss)
Approximate round-trip time in = milliseconds:
Minimum =3D 97msek, = maximum =3D 221 ms, 109 ms average =3D
Control-C

Since it was ok at the = beginning, they think that may be the traffic had increased recently and = Limelight`s server simply doesn`t have enought resources to serve this = traffic. May be it has to be = retuned.

= --Apple-Mail-3--437262786--