- « Previous
-
- 1
- 2
- Next »
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@JTANDVT wrote:
traceroute to verizon.com (192.16.31.23), 64 hops max, 72 byte packets
1 wireless_broadband_router (192.168.1.1) 1.453 ms 0.862 ms 0.857 ms
2 l100.cmdnnj-vfttp-22.verizon-gni.net (96.248.89.1) 7.246 ms 9.367 ms 7.153 ms
3 t0-4-0-1.cmdnnj-lcr-21.verizon-gni.net (100.41.128.180) 9.773 ms 11.788 ms 9.445 ms
4 * * *
5 * * *
6 0.ae17.gw12.iad8.alter.net (140.222.234.33) 21.992 ms 22.157 ms 19.878 ms
7 edgecast.com.customer.alter.net (204.148.11.54) 16.889 ms 22.113 ms 19.974 ms
8 edgecastcdn.net (72.21.83.153) 19.993 ms 20.149 ms 20.149 ms
9 192.16.31.23 (192.16.31.23) 17.112 ms 22.786 ms 19.875 ms
Every single one of these hops up to #8 is Verizon owned. I don't see anything wrong with this traceroute either. What you want though is a reverse trace to you from your download target. Paths to the source and from the source can be different.
In fact, I just lol'd hard because Verizon apparently bought edgecast.
Verizon, #1 at being bad. Dear Verizon execs, please learn to internet. You WILL be replaced.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That is funny because central Jersey is Verizon's backyard.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@JTANDVT wrote:traceroute to verizon.com (192.16.31.23), 64 hops max, 72 byte packets
1 wireless_broadband_router (192.168.1.1) 1.453 ms 0.862 ms 0.857 ms
2 l100.cmdnnj-vfttp-22.verizon-gni.net (96.248.89.1) 7.246 ms 9.367 ms 7.153 ms
3 t0-4-0-1.cmdnnj-lcr-21.verizon-gni.net (100.41.128.180) 9.773 ms 11.788 ms 9.445 ms
4 * * *
5 * * *
6 0.ae17.gw12.iad8.alter.net (140.222.234.33) 21.992 ms 22.157 ms 19.878 ms
7 edgecast.com.customer.alter.net (204.148.11.54) 16.889 ms 22.113 ms 19.974 ms
8 edgecastcdn.net (72.21.83.153) 19.993 ms 20.149 ms 20.149 ms
9 192.16.31.23 (192.16.31.23) 17.112 ms 22.786 ms 19.875 ms
So where is the issue?
Not all devices will respond to a traceroute command.
So if your issue is steps 4&5, probably not an issue.
And you got to your final destination w/ no dropped packets.
- « Previous
-
- 1
- 2
- Next »