VUDU Hogs half my network

[Greg]

Re: VUDU Hogs half my network

Hi htheater,

The network setting (that 3 level radio button setting) affects download speeds but also upload speeds.
If you set it to the lowest level, for instance, you're going to see that the upload is limited to around 100 Kbps (which is what your long post ended up asking for). Try it! Really! - No software update required.

Cheers,

-- Greg

[Nded]

Re: VUDU Hogs half my network

If you set it in the "middle" for instant SD and delayed HD, your upload is limited to 200kb, only instant HD users are hit for 300kb.

[htheater]

Re: VUDU Hogs half my network

Hi htheater,

The network setting (that 3 level radio button setting) affects download speeds but also upload speeds.
If you set it to the lowest level, for instance, you're going to see that the upload is limited to around 100 Kbps (which is what your long post ended up asking for). Try it! Really! - No software update required.

Cheers,

-- Greg

Greg and Ed,

Thank you for the data, and, like I said, it didn't SEEM to affect the UPLOAD speed....I stand corrected, however, as I stated, even when set to the 2Mbps setting, it is over running the network in real life. Really!

Also, you are missing the point.....forcing someone to limit their DOWNLOAD speed so that their UPLOAD speed goes down is, IMHO, the wrong way to address this as it takes away one of the main Vudu marketing points.....INSTANT movie viewing. It is bad enough to limit someone to instant SD only but you are asking for me to limit clients to NO instant viewing at all to accomplish what is needed. So, no, your solution is not what I asked for....I feel that a software update IS needed!

FWIW, I don't think most clients would mind hogging the entire network while they are watching a movie as they probably aren't using the Internet at that time, so, why limit the DOWNLOAD just to keep it from hogging the network when the Vudu is "idle".

[rstone]

Re: VUDU Hogs half my network

If you set it in the "middle" for instant SD and delayed HD, your upload is limited to 200kb, only instant HD users are hit for 300kb.

Lets look at this in the context of a home with multiple boxes, because I think that is more relevant to this discussion. Say AGAIN you have DSL with a 6Mbps, and a 650kbps connection and you have 2 boxes...The problem is that you should be able to enjoy INSTANT HD on BOTH boxes , without having to suffer with bandwidth issues.

So in our scenario with two boxes at "Instant HD" we are now talking 300kbps per box, which gives us 600kbps, or close to our limit of available upstream bandwidth of multibox user. Now sure we could lower to "Instant SD" and reduce that to 400kbps, but why should they? You're asking people to give up the luxury of what the box was intended to do, and that is, if you have the available downstream bandwidth you can play "instant HD." Instead you are saying if your upstream bandwidth is taking over all your upstream bandwidth, then you either A. Lose the ability to get "Instant HD," even so your downstream bandwidth is sufficient to do so or B. Keep it at "Instant HD" and let your network suffer (assuming one is not technically adept to resolve this via a router). The fact is, whether you own 2 or 5 boxes, you shouldn't have to resort to other advance network tactic to solve this problem, when this should be resolved via settings within the VUDU box. That is the point.

[NA9D]

Re: VUDU Hogs half my network

I want to chime in here as well and say I agree with rstone and htheater. I can see in many instance where you would want to do what the Vudu does now and limit both download and upload speeds. But, the automatic detection system in the box should have more settings ranges. The box does a test of the network connection before assigning settings. So it should know what the available d/l and u/l speeds are. Therefore, if my d/l speed is showing something testing out at say 5.5 Mb/sec and my u/l speed is showing at 600 kbps, then it should crank things up both way. If OTOH, the d/l speed is showing at 5.5 and the u/l speed at say 256 or 300, then it should still give me the max d/l speed of 4.0 but limit the u/l to 200 or even 100.

Now, the problem does come in with having two or more boxes on your network and having a speed of say 600 up. No way for the box to autodetect that. So then in addition to the automatic settings, there should be a setting that will allow the user to manually crank the upload down. I know there may be a fear that everyone will crank the u/l down and that will screw up the peering network but perhaps this is something that can be done by customer service if absolutely necessary. It is a problem though.

And I agree with Aaron, that those of us with large upload speeds, should be able to offer a higher upload to the user community and perhaps that would take some of the load off those who are not blessed as such.

Bottom line: I don't think people with high download speeds but poor uploads should be punished by not being able to get instant access to the movies.

[Greg]

Re: VUDU Hogs half my network

Yup, you guys have good points. I'm sure we'll be making incremental enhancements with time.

Cheers,

-- Greg

[htheater]

Re: VUDU Hogs half my network

Yup, you guys have good points. I'm sure we'll be making incremental enhancements with time.

Cheers,

-- Greg

Greg,

That is all we can ask for.....a responsive company....and, Vudu has proven to be just that in the past!

Thanks for listening!

[interacsol]

Re: VUDU Hogs half my network

I bought a Vudu a couple weeks ago and I am generally impressed -- great piece of hardware (much higher quality than I was expecting), excellent quality movies with good selection, elegant user interface.

One wrinkle, however, related to this thread: when I got Vudu, I upgraded my CableOne internet service from 2Mbps to 5Mbps. I now have no problem with download speed, even when using the internet for work while my family is watching a movie.

My problem is that CableOne tests for upload VOLUME, regardless of speed. If you upload more than 250MB between noon and midnight, you are automatically throttled down to the 2Mbps service, which nets to 1.2 to 1.7Mbps, until midnight. When I check my speed in the morning, I'm at 5Mbps. At night, before I even power up the home theater, I'm throttled to under 2Mbps. When I call the cable company, they say "Wow, you are uploading a lot every day).

I'm happy to let Vudu stream away in the P2P context but I need a way to control how much it uploads so that I can watch instant HD in the evening (the reason I bought the box) without getting throttled back, which is what is happening now (so I'm online rather than watching a movie). I need to be able to set a limit on AMOUNT per day or SPEED, independently of download speed.

Until Vudu provides a solution, I have two options: Upgrade (again) to 8Mbps service for an additional $33/mo. (at which point I will be unable to recommend Vudu to my friends) or unplug my Vudu box most of the time, thereby reducing the benefit of the clever P2P technology.

Comments or suggestions from anyone?

Gordon

[SatireWolf]

Re: VUDU Hogs half my network

I am seeing the EXACT same thing at my home (6mb > 3mb), office (8mb > 4mb), two of my employee's homes (both 8mb > 4mb) and every customer I have installed this at. BTW, these speeds are actual paid for speeds, not speeds that you see using powerboost, etc.

These are ALL installs that have the latest OS, are always plugged in and have all of the cover art, etc. Some have been installed for over 6 months and all at least a month, so it is not a "catching up" issue which DOES happen and IS totally understandable and acceptable!

And, yes, I have read the other threads on this and have eliminated the issue via router settings at the sites that allow this, but I should not have to do this at that level and, does Vudu expect me to replace everyone's router when I sell a unit?

This IS an issue and the firmware needs an update to allow you to limit OUTGOING (upload) usage independent of INCOMING (download) usage.



I see this recommended in other threads too. This is not an acceptable fix. One of Vudu's main selling points is "INSTANT" movie viewing. Setting it back WILL cut back on your network usage, but it will also mean that you can't watch movies right then and there.....you have to plan ahead of time....this ruins much of the Vudu allure which is a shame since it is such a great piece of hardware, software AND service all in one box! Rare in the CE world!

I'm not sure how many connections that Vudu makes on average, but some 'lesser' routers (ie most of the default DSL modems and routers) have slow processors and low memory can't handle high state tables from torrents and slow down regardless of bandwidth utilization. A lot of times if the router/firewall runs out of steam (ie processor utilization is maxed), regardless of extra bandwidth being available, your total throughput will drop substantially until the number of connections through the router/firewall is reduced.

I use ALIX and Soekris 5501 boards running pfSense at all of my customers sites and they handle 50-100 employees hammer multiple T1's just fine. If you're having performance issues, you could always try going to a more 'open' router platform and put some more horsepower behind the service.

As for Vudu being responsible for this, if you're having performance problems with your firewall with Vudu, any other torrent app will cause the same problems even if it is bandwidth limited. A lot of game update apps, and several video distribution services use torrent technology and cause the same issues.

It's more an issue of ISP's providing wimpy torrent adverse routers / firewalls as they don't give a flipping dime away that they don't have to. Plus they'd rather not have their customers running torrents.

The other possibility is that some ISP's are employing QoS at the ISP side of a customers connection and throttling the entire connection the second they see torrent traffic until the torrents are stopped. This is a bit Draconian but I have seen this behavior on Cox and Comcast services before.

So it's possible that if replacing the router does not resolve your issue, the ISP is giving you a hammering from passing torrent traffic.

I would be curious to packet analyze what is coming out of the vudu to see if most packet shapers categorize it as normal or torrent traffic via their default torrent queue setups.

[deparson]

Re: VUDU Hogs half my network

I wonder if any of the open source router software supports upload bandwidth limits by time of day. e.g. limit uploads during the day to a lower kbps and then open it up at night when you are likely to use the box??

I bought a Vudu a couple weeks ago and I am generally impressed -- great piece of hardware (much higher quality than I was expecting), excellent quality movies with good selection, elegant user interface.

One wrinkle, however, related to this thread: when I got Vudu, I upgraded my CableOne internet service from 2Mbps to 5Mbps. I now have no problem with download speed, even when using the internet for work while my family is watching a movie.

My problem is that CableOne tests for upload VOLUME, regardless of speed. If you upload more than 250MB between noon and midnight, you are automatically throttled down to the 2Mbps service, which nets to 1.2 to 1.7Mbps, until midnight. When I check my speed in the morning, I'm at 5Mbps. At night, before I even power up the home theater, I'm throttled to under 2Mbps. When I call the cable company, they say "Wow, you are uploading a lot every day).

I'm happy to let Vudu stream away in the P2P context but I need a way to control how much it uploads so that I can watch instant HD in the evening (the reason I bought the box) without getting throttled back, which is what is happening now (so I'm online rather than watching a movie). I need to be able to set a limit on AMOUNT per day or SPEED, independently of download speed.

Until Vudu provides a solution, I have two options: Upgrade (again) to 8Mbps service for an additional $33/mo. (at which point I will be unable to recommend Vudu to my friends) or unplug my Vudu box most of the time, thereby reducing the benefit of the clever P2P technology.

Comments or suggestions from anyone?

Gordon

[aaronwt]

Re: VUDU Hogs half my network

I wonder if any of the open source router software supports upload bandwidth limits by time of day. e.g. limit uploads during the day to a lower kbps and then open it up at night when you are likely to use the box??

Can't that already be done with some routers? I thought some of the Dlink routers had that capabilty.

[RonV]

Re: VUDU Hogs half my network

I wonder if any of the open source router software supports upload bandwidth limits by time of day. e.g. limit uploads during the day to a lower kbps and then open it up at night when you are likely to use the box??

I've seen firmware like Tomato do access restrictions by time of day but not QOS. But if you are good with the "tc" command and know how to use cron you could write your own schedule.

[NA9D]

Re: VUDU Hogs half my network

Heh, heh. If you are good with the IPTables command you can do all sorts of fun stuff too. But does anyone really know how the IPTables command fully works?

Does anybody know what time it is? Does anybody really care? About time...

[AndyMan]

Re: VUDU Hogs half my network

Here is the outgoing log from my router after my vudu was connected to the network for maybe 20 seconds. I had to unplug my vudu to send this thread! I hope this is helpful in answering the question: What is my vudu du-ing to my network after being connected for 6 days. Updates? peer-to-peer communicaiton with ?????

192.168.1.101204.11.220.6113210 192.168.1.101204.11.220.6113202 192.168.1.101204.11.220.6113203 192.168.1.101204.11.220.6213205 192.168.1.101204.11.220.6113201 192.168.1.10168.50.252.998100 192.168.1.101208.78.67.588101 192.168.1.10170.152.250.1348101 192.168.1.10169.120.56.6341364 192.168.1.10124.186.165.188101 192.168.1.101173.17.254.2008101 192.168.1.10170.121.0.1688101 192.168.1.10172.177.234.208101 192.168.1.10172.197.225.2078101 192.168.1.10167.61.117.248101 192.168.1.10176.217.0.758101 192.168.1.10198.247.28.888101 192.168.1.10170.89.127.508101 192.168.1.10168.4.83.8847232 192.168.1.10124.130.36.738101 192.168.1.101204.11.220.94laserjet

[AndyMan]

Re: VUDU Hogs half my network

Here are the routes of the IP addresses my vudu is going to over the 20 secs I had it connected to the internet. This thing is going to coast to coast sending something...what is it sending?

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

F:\>c:

C:\>tracert 204.11.220.94

Tracing route to n94.vudu.com [204.11.220.94]
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms 192.168.1.1
2 16 ms 15 ms 14 ms 65.14.252.13
3 17 ms 16 ms 16 ms 68.152.179.181
4 22 ms 22 ms 22 ms adsl-156-253-153.bct.bellsouth.net [66.156.253.1
53]
5 21 ms 21 ms 21 ms 65.83.236.133
6 21 ms 21 ms 20 ms pxr00apx-ge-1-3-0.bellsouth.net [65.83.236.160]

7 21 ms 20 ms 21 ms 65.83.238.142
8 33 ms 33 ms 32 ms cr2.ormfl.ip.att.net [12.122.143.214]
9 33 ms 33 ms 31 ms cr1.attga.ip.att.net [12.122.5.142]
10 32 ms 32 ms 33 ms ggr2.attga.ip.att.net [12.122.141.97]
11 33 ms 42 ms 33 ms 192.205.33.38
12 32 ms 33 ms 32 ms ge-11-0-2.mpr3.atl6.us.above.net [64.125.25.9]
13 51 ms 51 ms 53 ms ge-2-1-0.mpr4.iah1.us.above.net [64.125.31.50]
14 81 ms 79 ms 79 ms so-1-1-0.mpr4.lax9.us.above.net [64.125.25.18]
15 82 ms 90 ms 89 ms so-0-0-0.mpr3.lax9.us.above.net [64.125.26.145]

16 92 ms 89 ms 89 ms so-0-1-0.mpr1.sjc2.us.above.net [64.125.26.26]
17 89 ms 88 ms 88 ms xe-1-1-0.er1.sjc2.us.above.net [64.125.26.198]
18 89 ms 90 ms 89 ms 64.124.200.82
19 89 ms 89 ms 88 ms vl300.cr2.mlp1.peakwebhosting.com [67.221.32.18]

20 91 ms 93 ms 91 ms gi3-11.cr2.sfo1.peakwebhosting.com [204.11.216.2
10]
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 ^C
C:\>tracert 74.125.45.100

Tracing route to yx-in-f100.google.com [74.125.45.100]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 16 ms 18 ms 15 ms 65.14.252.13
3 18 ms 16 ms 18 ms 68.152.179.181
4 50 ms 48 ms 36 ms adsl-156-253-150.bct.bellsouth.net [66.156.253.1
50]
5 36 ms 34 ms 34 ms pxr00chi-so-0-0-0.bellsouth.net [65.83.236.64]
6 34 ms 35 ms 33 ms pxr00asm-2-0-0.bellsouth.net [65.83.236.2]
7 34 ms 33 ms 33 ms 65.83.237.221
8 35 ms 34 ms 35 ms 72.14.233.56
9 34 ms 34 ms 36 ms 209.85.254.243
10 34 ms 40 ms 35 ms 209.85.253.133
11 35 ms 34 ms 35 ms yx-in-f100.google.com [74.125.45.100]

Trace complete.

C:\>tracert 24.130.36.73

Tracing route to rh-la-36-73.rhythm.com [24.130.36.73]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 16 ms 15 ms 14 ms 65.14.252.13
3 17 ms 16 ms 17 ms 68.152.179.181
4 23 ms 23 ms 22 ms adsl-156-253-153.bct.bellsouth.net [66.156.253.1
53]
5 22 ms 21 ms 21 ms 65.83.236.133
6 21 ms 22 ms 21 ms pxr00apx-so-0-0-0.bellsouth.net [65.83.236.60]
7 20 ms 21 ms 20 ms 65.83.238.190
8 32 ms 33 ms 35 ms cr1.ormfl.ip.att.net [12.123.34.18]
9 33 ms 32 ms 32 ms cr2.attga.ip.att.net [12.122.31.29]
10 31 ms 31 ms 31 ms ggr2.attga.ip.att.net [12.122.140.93]
11 31 ms 31 ms 32 ms 192.205.34.22
12 52 ms 53 ms 52 ms cr2-pos-0-8-2-3.NewYork.savvis.net [204.70.196.1
25]
13 52 ms 52 ms 54 ms er2-tengig-3-1.NewYork.savvis.net [204.70.198.18
]
14 54 ms 53 ms 54 ms 208.173.138.14
15 55 ms 54 ms 54 ms pos-1-9-0-0-cr01.newyork.ny.ibone.comcast.net [6
8.86.86.41]
16 71 ms 71 ms 72 ms pos-1-15-0-0-cr01.chicago.il.ibone.comcast.net [
68.86.85.102]
17 96 ms 97 ms 96 ms pos-1-15-0-0-cr01.denver.co.ibone.comcast.net [6
8.86.85.114]
18 126 ms 126 ms 126 ms pos-0-15-0-0-cr01.sanjose.ca.ibone.comcast.net [
68.86.85.126]
19 126 ms 127 ms 126 ms pos-0-14-0-0-ar01.sfsutro.ca.sfba.comcast.net [6
8.86.90.158]
20 128 ms 126 ms 127 ms te-9-3-ur02.oakland.ca.sfba.comcast.net [68.86.1
43.69]
21 128 ms 127 ms 128 ms GE-2-2-ur01.oakland.ca.sfba.comcast.net [68.87.1
99.101]
22 * 128 ms 128 ms ge-3-0-0-ten01.oakland.ca.sfba.comcast.net [68.8
5.217.70]
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * ^C
C:\>tracert 68.4.83.88

Tracing route to ip68-4-83-88.oc.oc.cox.net [68.4.83.88]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 16 ms 14 ms 15 ms 65.14.252.13
3 16 ms 16 ms 17 ms 65.14.255.161
4 21 ms 22 ms 21 ms adsl-156-253-153.bct.bellsouth.net [66.156.253.153]
5 21 ms 20 ms 21 ms 65.83.236.133
6 20 ms 20 ms 21 ms pxr00apx-so-0-0-0.bellsouth.net [65.83.236.60]
7 20 ms 21 ms 20 ms 65.83.238.182
8 32 ms 32 ms 32 ms 12.122.143.134
9 34 ms 32 ms 32 ms cr1.attga.ip.att.net [12.122.5.142]
10 32 ms 31 ms 32 ms ggr4.attga.ip.att.net [12.122.141.81]
11 418 ms 691 ms 815 ms 192.205.35.90
12 79 ms 81 ms 107 ms 67.17.195.30
13 80 ms 80 ms 80 ms 68.1.2.107
14 81 ms 82 ms 81 ms ip68-4-13-46.oc.oc.cox.net [68.4.13.46]
15 83 ms 82 ms 83 ms ip68-4-13-14.oc.oc.cox.net [68.4.13.14]
16 82 ms 81 ms 84 ms 68.4.15.78
17 * * * Request timed out.
18 * * ^C
C:\>tracert 98.247.28.88

Tracing route to c-98-247-28-88.hsd1.wa.comcast.net [98.247.28.88]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 15 ms 15 ms 14 ms 65.14.252.13
3 15 ms 16 ms 16 ms 65.14.255.161
4 21 ms 28 ms 20 ms adsl-156-253-153.bct.bellsouth.net [66.156.253.153]
5 23 ms 22 ms 20 ms 65.83.236.135
6 22 ms 21 ms 20 ms 65.83.236.116
7 21 ms 20 ms 21 ms 65.83.238.190
8 32 ms 32 ms 32 ms cr1.ormfl.ip.att.net [12.122.143.86]
9 33 ms 32 ms 32 ms cr2.attga.ip.att.net [12.122.31.29]
10 31 ms 32 ms 31 ms ggr2.attga.ip.att.net [12.122.140.93]
11 30 ms 31 ms 31 ms 192.205.34.22
12 52 ms 52 ms 52 ms cr2-pos-0-8-2-3.NewYork.savvis.net [204.70.196.125]
13 54 ms 52 ms 53 ms er2-tengig-3-1.NewYork.savvis.net [204.70.198.18]
14 53 ms 53 ms 52 ms 208.173.138.14
15 54 ms 53 ms 53 ms pos-1-9-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.86.41]
16 71 ms 73 ms 72 ms pos-1-11-0-0-cr01.chicago.il.ibone.comcast.net [68.86.85.38]
17 99 ms 98 ms 98 ms pos-1-14-0-0-cr01.denver.co.ibone.comcast.net [68.86.85.118]
18 124 ms 126 ms 125 ms pos-0-6-0-0-cr01.seattle.wa.ibone.comcast.net [68.86.85.230]
19 127 ms 126 ms 125 ms pos-0-14-0-0-ar01.seattle.wa.seattle.comcast.net [68.86.90.210]
20 127 ms 126 ms 127 ms po-50-ur02.bellevue.wa.seattle.comcast.net [68.85.240.66]
21 127 ms 127 ms 127 ms 68.86.113.62
22 * * * Request timed out.
23 * ^C
C:\>tracert 76.217.0.75

Tracing route to 76-217-0-75.lightspeed.irvnca.sbcglobal.net [76.217.0.75]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms 192.168.1.1
2 15 ms 15 ms 14 ms 65.14.252.13
3 15 ms 15 ms 16 ms 65.14.255.161
4 21 ms 21 ms 21 ms adsl-156-253-153.bct.bellsouth.net [66.156.253.153]
5 21 ms 20 ms 21 ms axr00mco-so-2-0-0.bellsouth.net [65.83.238.43]
6 20 ms 19 ms 25 ms pxr00apx-so-0-0-0.bellsouth.net [65.83.236.60]
7 22 ms 21 ms 24 ms 65.83.238.138
8 81 ms 81 ms 80 ms cr1.ormfl.ip.att.net [12.122.143.86]
9 81 ms 80 ms 82 ms cr1.hs1tx.ip.att.net [12.122.31.241]
10 80 ms 80 ms 81 ms cr2.hs1tx.ip.att.net [12.122.5.190]
11 80 ms 80 ms 79 ms cr1.dlstx.ip.att.net [12.122.28.157]
12 80 ms 80 ms 80 ms cr2.dlstx.ip.att.net [12.122.1.210]
13 80 ms 80 ms 80 ms cr2.la2ca.ip.att.net [12.122.28.178]
14 81 ms 80 ms 79 ms gar6.la2ca.ip.att.net [12.122.129.5]
15 80 ms 79 ms 79 ms 12.122.79.110
16 82 ms 82 ms 81 ms agr2-p0-12-2-0.irvnca.sbcglobal.net [151.164.243.177]
17 81 ms 81 ms 81 ms bb4-10g12-0.irvnca.sbcglobal.net [151.164.243.34]
18 81 ms 81 ms 81 ms bb2.p13-1.irvnca.sbcglobal.net [69.220.8.21]
19 * * ^C
C:\>tracert 67.61.117.24

Tracing route to 67-61-117-24.cpe.cableone.net [67.61.117.24]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms 192.168.1.1
2 15 ms 15 ms 15 ms 65.14.252.13
3 15 ms 15 ms 16 ms 65.14.255.161
4 21 ms 21 ms 21 ms adsl-156-253-153.bct.bellsouth.net [66.156.253.153]
5 21 ms 21 ms 21 ms 65.83.236.133
6 20 ms 20 ms 20 ms axr00asm-0-3-0.bellsouth.net [65.83.236.12]
7 20 ms 20 ms 20 ms 65.83.238.142
8 47 ms 48 ms 48 ms cr1.ormfl.ip.att.net [12.123.34.18]
9 49 ms 48 ms 47 ms cr1.hs1tx.ip.att.net [12.122.31.241]
10 48 ms 47 ms 47 ms cr2.hs1tx.ip.att.net [12.122.5.190]
11 47 ms 48 ms 47 ms cr1.dlstx.ip.att.net [12.122.28.157]
12 47 ms 47 ms 47 ms 12.122.139.25
13 53 ms 47 ms 47 ms 192.205.33.206
14 101 ms 102 ms 100 ms scor-01-rif1.sndg.twtelecom.net [66.192.251.146]
15 101 ms 101 ms 101 ms 67-60-156-74.cpe.cableone.net [67.60.156.74]
16 * * * Request timed out.
17 * *