YouTube upload problems

[#1]

I've been having trouble uploading to YouTube for several days now, where a video that may take 20-40 minutes to upload is now getting estimated uploads of 300+ minutes.
In doing a tracert to YouTube I get:

Quote

Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\>tracert youtube.com Tracing route to youtube.com [212.56.71.241] over a maximum of 30 hops:   1    90 ms    99 ms    99 ms  dsldevice.lan [192.168.1.254]   2    27 ms    14 ms    13 ms  lo0-central10.pcl-ag01.plus.net [195.166.128.182 ]   3    14 ms    14 ms    13 ms  link-a-central10.pcl-gw01.plus.net [212.159.2.16 0]   4    14 ms    14 ms    14 ms  192.core.access.plus.net [212.159.0.192]   5    14 ms    14 ms    13 ms  212.56.71.241 Trace complete.

So why is my connection being directed to Plusnet and not YouTube?

[#2]

This is what I get.

Quote

Tracing route to youtube.com [173.194.34.132] over a maximum of 30 hops:   1    <1 ms    <1 ms    <1 ms  192.168.1.254   2    19 ms    17 ms    18 ms  lo0-central10.pcl-ag06.plus.net [195.166.128.187 ]   3    16 ms    15 ms    15 ms  link1-central10.pcl-gw01.plus.net [84.93.249.160 ]   4    15 ms    15 ms    16 ms  212.core.access.plus.net [212.159.0.212]   5    15 ms    16 ms    15 ms  ae1.ptw-cr01.plus.net [195.166.129.0]   6    16 ms    15 ms    15 ms  ae2.ptw-cr02.plus.net [195.166.129.5]   7    16 ms    15 ms    16 ms  72.14.223.32   8    16 ms    16 ms    15 ms  209.85.252.188   9    16 ms    15 ms    16 ms  209.85.253.115 10    16 ms    16 ms    16 ms  lhr14s21-in-f4.1e100.net [173.194.34.132] Trace complete. >

[#3]

Hi Razer,
That's odd. The IP you're tracing to there is a box in our network. Which DNS server is that being returned from, as we need to know why that IP is being returned as youtube?

[#4]

Hi Matt,
I have my router configured to use OpenDNS.

[#5]

Razer,
A quick google search shows loads of people that use OpenDNS having youtube issues do I think Matt is right on track in asking for your DNS settings. Have you tried google's DNS?
Its 8.8.8.8 or just use the PN DNS but I don't know that one yet as I do not have the BB activated yet.

[#6]

Razer:  Red herring.  You'll be hitting the caches in our network for Youtube content with the tracert.  Have you done a speed test recently to see if your upload speed is down? 

[#7]

Could you explain that in more detail please Kelly, I get similar to Strat
Tracing route to youtube.com [173.194.41.96]
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  dsldevice.lan [192.168.1.254]
  2    35 ms    34 ms    34 ms  lo0-central10.ptw-ag02.plus.net [195.166.128.196]
  3    35 ms    34 ms    34 ms  link-b-central10.ptw-gw02.plus.net [212.159.2.150]
  4    34 ms    34 ms    34 ms  te2-3.ptw-gw02.plus.net [212.159.1.58]
  5    34 ms    34 ms    34 ms  72.14.223.32
  6    35 ms    36 ms    34 ms  209.85.252.186
  7    35 ms    34 ms    35 ms  72.14.238.53
  8    34 ms    34 ms    34 ms  lhr08s02-in-f0.1e100.net [173.194.41.96]
Trace complete.

[#8]

The tracert is back to normal. Was late last night and still this morning, and shows much as Strat's example above.

Quote

Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\>tracert youtube.com Tracing route to youtube.com [173.194.34.161] over a maximum of 30 hops:  1    78 ms    99 ms    99 ms  dsldevice.lan [192.168.1.254]  2    84 ms    60 ms    19 ms  lo0-central10.pcl-ag04.plus.net [195.166.128.185 ]  3    15 ms    15 ms    14 ms  link2-central10.pcl-gw02.plus.net [84.93.249.98]  4    15 ms    14 ms    14 ms  206.core.access.plus.net [212.159.0.206]  5    15 ms    15 ms    14 ms  ae1.ptw-cr02.plus.net [195.166.129.2]  6    15 ms    14 ms    15 ms  72.14.223.32  7    18 ms    17 ms    15 ms  209.85.252.188  8    15 ms    15 ms    15 ms  209.85.253.175  9    15 ms    15 ms    15 ms  lhr14s22-in-f1.1e100.net [173.194.34.161] Trace complete.

As for speed. My upload speed has been checking as within normal parameters. It's the first thing I checked and changing gateway several times hasn't made a difference.

Quote from: RickK

A quick google search shows loads of people that use OpenDNS having youtube issues do I think Matt is right on track in asking for your DNS settings.

Thanks for that info. I think that OpenDNS must have sorted that particular issue.

[#9]

I'm 100% sure how they work, but https://peering.google.com/about/ggc.html.
Hitting that IP for a Google look up and sometimes not is entirely normal though!

[#10]

Surely that is only for calling content from youtube. What about uploading? I can't imagine that my uploads to 'YouTube' would actually be going to a PN cache.

[#11]

Can someone help me understand what's going on here? I've tried again to upload, and decided to take a look at TCP connections so that I could trace the upload servers in an effort to find out where the problem lies. I find two connections, both https. The first is constant, the second repeatedly renewed, as it were. Both traces timeout at the 12th hop and I am left none the wiser because there's no information on that hop.

Quote

C:\>tracert fa-in-f95.1e100.net Tracing route to fa-in-f95.1e100.net [173.194.70.95] over a maximum of 30 hops:   1    21 ms    99 ms    99 ms  dsldevice.lan [192.168.1.254]   2    16 ms    16 ms    16 ms  lo0-central10.pcl-ag07.plus.net [195.166.128.188 ]   3    15 ms    15 ms    15 ms  link5-central10.pcl-gw01.plus.net [84.93.249.200 ]   4    15 ms    15 ms    15 ms  xe-2-2-0.pcl-cr01.plus.net [212.159.1.12]   5    16 ms    15 ms    16 ms  ae1.ptw-cr01.plus.net [195.166.129.0]   6    15 ms    15 ms    15 ms  72.14.222.97   7    15 ms    15 ms    16 ms  209.85.240.61   8    16 ms    16 ms    16 ms  209.85.253.94   9    21 ms    21 ms    21 ms  209.85.243.33 10    29 ms    27 ms    28 ms  209.85.241.229 11    28 ms    28 ms    28 ms  209.85.254.112 12     *        *        *     Request timed out. 13    28 ms    28 ms    28 ms  fa-in-f95.1e100.net [173.194.70.95] Trace complete. ---------------- firefox.exe:3520 TCP mine.lan:1219 de-in-f116.1e100.net:https ESTABLISHED C:\>tracert de-in-f116.1e100.net Tracing route to de-in-f116.1e100.net [74.125.24.116] over a maximum of 30 hops:   1    38 ms    95 ms    99 ms  dsldevice.lan [192.168.1.254]   2    16 ms    16 ms    16 ms  lo0-central10.pcl-ag07.plus.net [195.166.128.188 ]   3    15 ms    15 ms    15 ms  link4-central10.pcl-gw02.plus.net [84.93.249.198 ]   4    15 ms    15 ms    15 ms  xe-2-2-0.pcl-cr02.plus.net [212.159.1.14]   5    15 ms    15 ms    15 ms  ae2.pcl-cr01.plus.net [195.166.129.6]   6    16 ms    15 ms    16 ms  ae1.ptw-cr01.plus.net [195.166.129.0]   7    15 ms    68 ms    15 ms  72.14.222.97   8    15 ms    20 ms    15 ms  209.85.240.63   9    16 ms    15 ms    16 ms  209.85.253.92 10    25 ms    24 ms    25 ms  209.85.251.190 11    42 ms    41 ms    43 ms  72.14.235.139 12     *        *        *     Request timed out. 13    25 ms    24 ms    24 ms  de-in-f116.1e100.net [74.125.24.116] Trace complete.

[#12]

I had uploaded one earlier with no issues.  Currently using PN and opendns dns servers, PN is the primary.  As for the trace looks like its a normal blackhole hop before the destination

[#13]

Those request time outs are just because that host isn't set up to respond to pings.  It's a red herring.
Still seeing poor uploads Razer?  Are you seeing fine speeds with other upstream activities?

[#14]

Thanks for the replies, gents.

Quote from: Gus

As for the trace looks like its a normal blackhole hop before the destination

I don't know what that means.

Quote from: Kelly

Those request time outs are just because that host isn't set up to respond to pings.  It's a red herring.

Ah, ok. Thanks for that.

Quote

Still seeing poor uploads Razer?  Are you seeing fine speeds with other upstream activities?

Yes, still terrible. Last good upload was over a week ago. I am trying every day and it's still the same. I only do one other upload activity, occasionally; dropbox. Last couple of uploads to that lately went fine, but I have always found the upload with that sluggish.

[#15]

Blackhole is same as Kellys reply, it is there but won't respond.  e.g. if I use DMZ my firewall does not respond to port scans.