Return-Path: <customer.support@llnw.com>
Delivered-To: acongi@2etv-group.com
Received: (qmail 18956 invoked by uid 503); 28 Jan 2015 10:36:28 -0000
Received: from unknown (HELO mailroute1.phx2.llnw.com) (69.164.57.40)
  by ns303373.ovh.net with SMTP; 28 Jan 2015 10:36:28 -0000
Received: from app31024.iad3.service-now.com (unknown [199.91.139.160])
	by mailroute1.phx2.llnw.com (Postfix) with ESMTPS id CE6989F67E3;
	Wed, 28 Jan 2015 03:22:50 -0700 (MST)
Date: Wed, 28 Jan 2015 02:22:47 -0800 (PST)
From: Limelight Support <customer.support@llnw.com>
Reply-To: customer.support@llnw.com
To: dsackett@llnw.com, acongi@2etv-group.com
Message-ID: <20726402.60566.1422440567136.JavaMail.p16521@app31024.iad3.service-now.com>
Subject: CINC0054840 - eetvgroup - http - issues with HLS playback in Dec
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_60564_19001119.1422440567136"
X-ServiceNow-SysEmail-Version: 2
X-ServiceNow-Source: Notification-0b0150266f2f8100d8862762be3ee4c2
Precedence: bulk

------=_Part_60564_19001119.1422440567136
Content-Type: multipart/alternative; 
	boundary="----=_Part_60565_14283877.1422440567136"

------=_Part_60565_14283877.1422440567136
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=UTF-8

2015-01-28 03:22:16 MST - Paul Bradbury (Additional comments)
Hello Adolphe,
=C2=A0
This is Paul with Limelight Networks. I have reviewed the information provi=
ded in regards to the single end user issue that occurred on Dec 24th and w=
anted to provide some analysis:
=C2=A0
Unfortunately, the information provide in the trace route may not be entire=
ly accurate, as there could have been changes on the customer side as far a=
s dns or routes being taken so we will be able to use that information exce=
pt to provide us with a possible location for where the customer may have b=
een resolving to that day. The trace route times to that location are accep=
table and within the bounds that we would expect normally delivery.
=C2=A0
In regards to the comment, "they think that may be the traffic had increase=
d recently and Limelight`s server simply doesn`t have enought resources to =
serve this traffic. May be it has to be retuned." The configuration is util=
izing all available resources on our network for http content delivery and =
as such was not a utilization issue. We had no major events that day in reg=
ards to http delivery that could have effected this customer. If there had =
been a utilization issue, you would have received reports of issue from mor=
e than a single user.
=C2=A0
Based on the information provided, we can find no fault on the Limelight si=
de and believe that the customer experienced an issue not related to Limeli=
ght.
=C2=A0
Please let me know if you have any further questions.
=C2=A0
Regards,
=C2=A0
=C2=A0
=C2=A0
This comment was added to CINC0054840.
=C2=A0
Thank you,
=C2=A0
Operations Customer Support=20
(866) 544-4830=20
(602) 850-5200=20
support@llnw.com
=C2=A0
Please do not delete the following Incident ID ref:
LLNW:CINC0054840

Ref:MSG0665241
------=_Part_60565_14283877.1422440567136
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset=UTF-8

<html><head></head><body><div>2015-01-28 03:22:16 MST - Paul Bradbury (Addi=
tional comments)</div><div>Hello Adolphe,</div><div>&nbsp;</div><div>This i=
s Paul with Limelight Networks. I have reviewed the information provided in=
 regards to the single end user issue that occurred on Dec 24th and wanted =
to provide some analysis:</div><div>&nbsp;</div><div>Unfortunately, the inf=
ormation provide in the trace route may not be entirely accurate, as there =
could have been changes on the customer side as far as dns or routes being =
taken so we will be able to use that information except to provide us with =
a possible location for where the customer may have been resolving to that =
day. The trace route times to that location are acceptable and within the b=
ounds that we would expect normally delivery.</div><div>&nbsp;</div><div>In=
 regards to the comment, &quot;they think that may be the traffic had incre=
ased recently and Limelight`s server simply doesn`t have enought resources =
to serve this traffic. May be it has to be retuned.&quot;  The configuratio=
n is utilizing all available resources on our network for http content deli=
very and as such was not a utilization issue. We had no major events that d=
ay in regards to http delivery that could have effected this customer. If t=
here had been a utilization issue, you would have received reports of issue=
 from more than a single user.</div><div>&nbsp;</div><div>Based on the info=
rmation provided, we can find no fault on the Limelight side and believe th=
at the customer experienced an issue not related to Limelight.</div><div>&n=
bsp;</div><div>Please let me know if you have any further questions.</div><=
div>&nbsp;</div><div>Regards,</div><div>&nbsp;</div><div>&nbsp;</div><div>&=
nbsp;</div><div>This comment was added to CINC0054840.</div><div>&nbsp;</di=
v><div>Thank you,</div><div>&nbsp;</div><div>Operations Customer Support </=
div><div>(866) 544-4830 </div><div>(602) 850-5200 </div><div>support@llnw.c=
om</div><div>&nbsp;</div><div>Please do not delete the following Incident I=
D ref:</div><div>LLNW:CINC0054840</div><div>&nbsp;</div><div style=3D"displ=
ay:inline">Ref:MSG0665241</div></body></html>
------=_Part_60565_14283877.1422440567136--

------=_Part_60564_19001119.1422440567136--
