Date: Tue, 27 Jan 2015 20:46:39 +0100 (CET)
From: acongi@free.fr
To: Aleksey PETROV <ap@vod-tv.ru>
Message-ID: <1304247883.135579352.1422387999793.JavaMail.root@zimbra58-e10.priv.proxad.net>
In-Reply-To: <CAGt4UJ-Mi+dJMb+AbfCgWfEdwHcHd5K2FsF+DqM+aOJM5jjH6g@mail.gmail.com>
Subject: =?utf-8?Q?Re=C2=A0:_Issues_with_the_client_#_20?=
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Dear Aleksey,

I asked  to Limelight more info about the problem and I'll keep you inform =
when I'll have a feed-back.

Best,=20
Adolphe

----- Mail d'origine -----
De: Aleksey PETROV <ap@vod-tv.ru>
=C3=80: Adolphe Congi <acongi@free.fr>
Envoy=C3=A9: Tue, 27 Jan 2015 13:05:58 +0100 (CET)
Objet: Issues with the client # 20

Dear Adolphe,

Hope this mail finds you well.

The client # 20 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

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]
 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]


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.
Please, send this traceroute to Limelight and ask them to do something
about it. Thank you very much, Adolphe!

Best,
Aleksey