Traceroute / Uploading TV Video to Comcast SLOW

[Michael L]

Hello NLUG,

Do I need a file transfer service?  Insight and suggestions will be much appreciated as always

I upload 22GB to 31GB of video weekly to Comcast and lesser amounts to Cox Media and Charter-

For Comcast I have to upload at this

URL:  https://connect.telvue.com / IP  35.224.46.35

By comparison, uploading to COMCAST TAKES OVER 8 TIMES LONGER ... ON A GOOD DAY!!! 

Here's a little graphic I sent them showing how slow Comcast Telvue is compared to Charter and Cox Media on a 1.9GB test file

(AND I SENT THEM THE TEST FILE SO THEY CAN TRY IT FOR THEMSELVES):

Charter	CoxMedia	Comcast Telvue		IS OVER
2m47s	2m34s	22m21s	<<<<	8 TIMES
				SLOWER

I've been emailing Comcast's contact for 4 to 6 months about how slow this is and the only response I ever get is:  "seems to be working fine"  <<--- i.e., Not our problem; can't help ya.  Finally Comcast management gets out of bed after months of hibernation and tells me:

Sir,

 

We upload to Telvue all the time without issue. We have hundreds of other customers who upload without issue.

We just uploaded just now without issue.

 

Blaming Comcast/Telvue is serving no purpose without doing the necessary troubleshooting steps. Logical troubleshooting starts at the source of the network path. Additionally, comparing speed uploads does not identify a network path issue.

 

Your path to Telvue on the AT&T network will likely contain many different hops. There is very possibly a problem with the path to Telvue somewhere on the network. The logical first step is to start at your upload location and check the path. Since you are an AT&T customer, Comcast can’t help with their network.

That being said we’d like to do what we can to help…

 

TRACERT is a good way to see the path and the speeds along the path. Have you done this?

I replied:  I need exact specific information:  How many hours, minutes and seconds did it take you to upload that test file to Telvue?  Very surprisingly I haven't gotten a response to this yet.

Is there an upload utility that will speed this up?  Do I need to employ a cloud file delivery service or some other service to get my files there in a timely manner?

Here are my Traceroute results:

(base) [jml@localhost ~]$ traceroute https://connect.telvue.com

traceroute to https://connect.telvue.com (35.224.46.35), 30 hops max, 60 byte packets

1 _gateway (10.1.11.254) 0.166 ms 0.094 ms 0.067 ms

2 192.168.1.254 (192.168.1.254) 7.224 ms 7.211 ms 7.265 ms

3 23-127-32-1.lightspeed.nsvltn.sbcglobal.net (23.127.32.1) 8.596 ms 8.626 ms 8.642 ms

4 99.174.25.198 (99.174.25.198) 9.364 ms 9.378 ms 9.450 ms

5 * * *

6 * * *

7 * * *

8 32.130.16.5 (32.130.16.5) 14.861 ms 8.664 ms 12.147 ms

9 gar1.nsvtn.ip.att.net (12.122.96.85) 8.402 ms 8.296 ms 8.328 ms

10 12.255.10.10 (12.255.10.10) 9.662 ms 12.255.10.12 (12.255.10.12) 8.712 ms 12.255.10.20 (12.255.10.20) 8.430 ms

11 * * *

12 108.170.249.67 (108.170.249.67) 9.405 ms 142.251.55.118 (142.251.55.118) 8.372 ms 209.85.246.230 (209.85.246.230) 8.395 ms

13 209.85.246.249 (209.85.246.249) 10.457 ms 72.14.233.145 (72.14.233.145) 11.756 ms 9.923 ms

14 209.85.246.249 (209.85.246.249) 10.771 ms 64.233.175.251 (64.233.175.251) 9.768 ms 142.251.51.243 (142.251.51.243) 16.502 ms

15 209.85.254.85 (209.85.254.85) 17.641 ms 142.251.51.241 (142.251.51.241) 1371.387 ms 216.239.40.141 (216.239.40.141) 16.104 ms

16 216.239.48.192 (216.239.48.192) 32.304 ms 142.251.226.108 (142.251.226.108) 30.806 ms 216.239.58.94 (216.239.58.94) 31.737 ms

17 216.239.50.0 (216.239.50.0) 33.507 ms * *

18 209.85.251.95 (209.85.251.95) 32.135 ms 216.239.41.191 (216.239.41.191) 33.499 ms 142.250.56.49 (142.250.56.49) 33.390 ms

19 142.251.70.239 (142.251.70.239) 30.842 ms * 209.85.242.21 (209.85.242.21) 33.031 ms

20 * * *

21 * * *

22 * * *

23 * * *

24 * * *

25 * * *

26 * * *

27 * * *

28 * * *

29 * * *

30 * * *

(base) [jml@localhost ~]$

[Gibson Prichard]

First, when I connect to connect.telvue.com, it resolves as 8.39.99.30 and NOT 35.224.46.35, as you listed. There seems to be two or more entries in their DNS, but 8.39.99.30 seems to be on a Level3 (CenturyLink) backbone in Philadelphia and 35.224.46.35 resolves for me as "35.46.224.35.bc.googleusercontent.com" on completely different IP space. When I go to https://35.224.46.35, I do get the Telvue website, but the SSL cert is from another entity - "giown1007.siteground.biz," which would seem that this could be a Google-hosted content distribution network. I will note that "telvue.com" resolves for to the 35.224.46.36 address, while "connect.telvue.com" resolves to 8.39.99.30 instead. Can you try uploading to Telvue through https://8.39.99.30 and see if that IP or server is faster for you?

Secondly, and to your question as to whether you would be helped by a file upload service, I don't know that you would, since a file upload service (HighTail or WeTransfer or others) is is just a repository in the cloud to store files, which doesn't ultimately deliver your content to your destination of connect.telvue.com. Perhaps you could try to upload through a friend's Comcast connection as an alternative to your AT&T one to see if there really is an interconnect or throttling issue, but I don't think a file transfer service is your answer. It seems to me that https://connect.telvue.com / IP  35.224.46.35 is on a low-bandwidth or oversubscribed circuit or server farm. I don't see an interconnection issue to either site.

Good luck.

Gibson Prichard
Nashville, TN
gib...@prichard.tv

[Michael L]

AS ALWAYS, THANK YOU ALL FOR THE EXCELLENT INFO.

I did upload a lot from our 10Mbps Comcast Business connection in the past, generally slow and historically Comcast has been a disastrous connection.

I should say that about July 2020 when I first uploaded to Telvue on my newly installed AT&T Fiber connection, I could upload extremely quickly, comparable to both Charter and Cox Media, not so in the last 6+ months.  And if I try this at night I get slightly (but noticeably) less slow results.  Particularly frustrating, the last few days it took over twice as long to upload to Telvue.  AND normally the upload is not set and forget ... it interrupts and I (the customer) have to reload and continue the upload, which at least picks up where it left off.  This happens more when I try to upload multiple files at once; if I could just set 10 or 12 files to uploading and come back later to a completed job, then I wouldn't care as much that it's slow.

--
--
You received this message because you are subscribed to the Google Groups "NLUG" group.
To post to this group, send email to nlug...@googlegroups.com
To unsubscribe from this group, send email to nlug-talk+...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/nlug-talk?hl=en

---
You received this message because you are subscribed to the Google Groups "NLUG" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nlug-talk+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/nlug-talk/CA%2BJ3mBC8sN1DOukS7ogSBXUvAS8Faqh364%3Dx2ZU1vFXWcFzivw%40mail.gmail.com.

[Paul Boniol]

What command/program are you using to send the files? It may be possible to set a parameter to automatically rerty.

To view this discussion on the web visit https://groups.google.com/d/msgid/nlug-talk/CALdmzXabxzguvSszc5BZpMPm-yFKM0Ca0fJy12G6kK%2BKP4X54w%40mail.gmail.com.

[Michael L]

I tried uploading to https://8.39.99.30 ; it's about the same.

It's a drag and drop web interface.  When it interrupts, I have to reload the web page and drag/drop again for it to continue.  I would very much like to do it via command line and auto retry which I suppose should work since we have the IP address (I had to get it from nslookup).

I tried the command line ftp, but that will probably not work without ftp access being set up on their end, which I will ask for.

To view this discussion on the web visit https://groups.google.com/d/msgid/nlug-talk/CAL9PgS08uaYAYQkcwDqYz3tmE7fW6WwFBZyjmWzq8eHAYAwnBQ%40mail.gmail.com.

[Paul Boniol]

I did a quick search of their documentation. It appears they support uploads via web interface, Samba, and ftp / sftp. I'd recommend sftp even if the content will be public. The ftp protocols are very likely the most fault tolerant option. Also command line access gives you options for automation if desired.

Paul

To view this discussion on the web visit https://groups.google.com/d/msgid/nlug-talk/CALdmzXZpS%2Br45_OeiXW8ohan1H0vLcBACxNw0ZA6iZCsfwyWrg%40mail.gmail.com.

[Kent Perrier]

IIRC, sftp/ftp doesn't do resume. rsync will but I doubt you will get support for that.

To view this discussion on the web visit https://groups.google.com/d/msgid/nlug-talk/CAL9PgS26X2yEsCqSOF6Ex22DUhSA8MHDdhFp4cSDuPrdYw42YA%40mail.gmail.com.

[Tilghman Lesher]

It will, as long as both client and server support the related (raw) commands:

https://unix.stackexchange.com/questions/91602/is-there-any-ftp-command-to-resume-upload

> To view this discussion on the web visit https://groups.google.com/d/msgid/nlug-talk/CA%2B6_KC-1Xtku9UPCdQekON9EXRuTUTit0sRYXHXTNaqQQbx6HA%40mail.gmail.com.



--
Tilghman

[Kent Perrier]

Ah, thanks. It's been a long time since I have had to worry about that. :)

To view this discussion on the web visit https://groups.google.com/d/msgid/nlug-talk/CAHPkZcWdUVCMtjfycRqN77E0xTMYAX0EBBxkWXQxyon5WQpdBg%40mail.gmail.com.

[Michael L]

Well, well, well, (I won't paste the pagefuls of instructions in this email, but)

https://telvue.com/telvue-knowledge-base/  

https://telvue.com/knowledgebase/json-rest-api-version-2-playlists/   <<<---- Ansible Playlist?

My hurdle:  This may be my first ever implementation of API and / or use of Ansible playlist if this is Ansible .. shall see

Thanks Paul for mentioning Telvue documentation and everyone for your expert input.  I suspect I'll have future questions, will see how far I get ...

To view this discussion on the web visit https://groups.google.com/d/msgid/nlug-talk/CA%2B6_KC8rFA4zu%2B-rePGmYbwsjHtKKgB3%2BaPsRBEUC%2BAh0-a6Kw%40mail.gmail.com.