Hey all, Getting delays and seeing some pretty funky routes inside Comcast. All traces start from Ashburn, VA (2001:4830:167b::) and go to Chicago, IL (2610:150:4b0f::). Coming from Occaid/SIXXS (over a tunnel) through HE.net and have seen: Ashburn -> San Jose -> New York -> Chicago ----- 3 sixxs-asbnva-gw.customer.occaid.net (2001:4830:e6:7::2) 9.955 ms 10.583 ms 10.17 ms 4 iad0-b0-ge2.hotnic.net (2001:4810:0:100::1) 9.726 ms 11.004 ms 9.956 ms 5 10gigabitethernet2-2.core1.ash1.he.net (2001:504:0:2::6939:1) 10.069 ms 10.674 ms 12.465 ms 6 2001:559::db5 (2001:559::db5) 94.83 ms 95.593 ms 94.768 ms 7 pos-2-2-0-0-cr01.sanjose.ca.ibone.comcast.net (2001:558:0:f58d::1) 96.779 ms 99.591 ms 94.964 ms 8 he-0-7-0-0-cr01.newyork.ny.ibone.comcast.net (2001:558:0:f5ba::2) 89.969 ms 91.143 ms 92.507 ms 9 he-0-11-0-0-cr01.350ecermak.il.ibone.comcast.net (2001:558:0:f5b8::2) 97.411 ms 88.731 ms 87.457 ms 10 he-0-10-0-0-pe04.350ecermak.il.ibone.comcast.net (2001:558:0:f8cc::2) 87.444 ms 88.756 ms 87.505 ms 11 2001:550:2:2::32:2 (2001:550:2:2::32:2) 89.812 ms 88.774 ms 87.558 ms ----- Ashburn -> New York (but with lots of latency..) -> Chicago ----- 3 sixxs-asbnva-gw.customer.occaid.net (2001:4830:e6:7::2) 9.549 ms 10.652 ms 10.107 ms 4 iad0-b0-ge2.hotnic.net (2001:4810:0:100::1) 9.975 ms 11.044 ms 10.009 ms 5 10gigabitethernet2-2.core1.ash1.he.net (2001:504:0:2::6939:1) 17.423 ms 11.05 ms 12.27 ms 6 2001:559::db5 (2001:559::db5) 95.197 ms 95.968 ms 94.793 ms 7 he-2-6-0-0-cr01.ashburn.va.ibone.comcast.net (2001:558:0:f8d2::1) 105.158 ms 101.428 ms 94.993 ms 8 he-0-7-0-0-cr01.newyork.ny.ibone.comcast.net (2001:558:0:f5ba::2) 89.735 ms 90.266 ms 92.577 ms 9 he-0-11-0-0-cr01.350ecermak.il.ibone.comcast.net (2001:558:0:f5b8::2) 89.813 ms 92.963 ms 92.383 ms 10 he-0-10-0-0-pe04.350ecermak.il.ibone.comcast.net (2001:558:0:f8cc::2) 87.401 ms 88.15 ms 87.085 ms 11 2001:550:2:2::32:2 (2001:550:2:2::32:2) 122.387 ms 124.288 ms 122.409 ms ----- Ashburn -> Chicago -> New York -> Chicago ----- 3 sixxs-asbnva-gw.customer.occaid.net (2001:4830:e6:7::2) 9.926 ms 10.183 ms 9.978 ms 4 iad0-b0-ge2.hotnic.net (2001:4810:0:100::1) 9.961 ms 11.37 ms 9.973 ms 5 10gigabitethernet2-2.core1.ash1.he.net (2001:504:0:2::6939:1) 9.95 ms 18.258 ms 9.951 ms 6 2001:559::db5 (2001:559::db5) 94.959 ms 96.413 ms 95.001 ms 7 he-1-10-0-0-cr01.chicago.il.ibone.comcast.net (2001:558:0:f552::1) 92.457 ms 92.964 ms 89.965 ms 8 he-0-7-0-0-cr01.newyork.ny.ibone.comcast.net (2001:558:0:f5ba::2) 89.789 ms 91.291 ms 97.333 ms 9 he-0-11-0-0-cr01.350ecermak.il.ibone.comcast.net (2001:558:0:f5b8::2) 87.518 ms 95.961 ms 87.506 ms 10 he-0-10-0-0-pe04.350ecermak.il.ibone.comcast.net (2001:558:0:f8cc::2) 87.406 ms 86.414 ms 87.425 ms 11 2001:550:2:2::32:2 (2001:550:2:2::32:2) 87.517 ms 86.589 ms 87.506 ms ----- Thoughts? Thanks, Stephen
It's likely a reverse DNS error. If you look at the latency, it's within range of the previous hops. -Steve On Wed, Dec 3, 2014 at 3:12 PM, Stephen Frost <sfrost@snowman.net> wrote:
Hey all,
Getting delays and seeing some pretty funky routes inside Comcast. All traces start from Ashburn, VA (2001:4830:167b::) and go to Chicago, IL (2610:150:4b0f::).
Coming from Occaid/SIXXS (over a tunnel) through HE.net and have seen:
Ashburn -> San Jose -> New York -> Chicago ----- 3 sixxs-asbnva-gw.customer.occaid.net (2001:4830:e6:7::2) 9.955 ms 10.583 ms 10.17 ms 4 iad0-b0-ge2.hotnic.net (2001:4810:0:100::1) 9.726 ms 11.004 ms 9.956 ms 5 10gigabitethernet2-2.core1.ash1.he.net (2001:504:0:2::6939:1) 10.069 ms 10.674 ms 12.465 ms 6 2001:559::db5 (2001:559::db5) 94.83 ms 95.593 ms 94.768 ms 7 pos-2-2-0-0-cr01.sanjose.ca.ibone.comcast.net (2001:558:0:f58d::1) 96.779 ms 99.591 ms 94.964 ms 8 he-0-7-0-0-cr01.newyork.ny.ibone.comcast.net (2001:558:0:f5ba::2) 89.969 ms 91.143 ms 92.507 ms 9 he-0-11-0-0-cr01.350ecermak.il.ibone.comcast.net (2001:558:0:f5b8::2) 97.411 ms 88.731 ms 87.457 ms 10 he-0-10-0-0-pe04.350ecermak.il.ibone.comcast.net (2001:558:0:f8cc::2) 87.444 ms 88.756 ms 87.505 ms 11 2001:550:2:2::32:2 (2001:550:2:2::32:2) 89.812 ms 88.774 ms 87.558 ms -----
Ashburn -> New York (but with lots of latency..) -> Chicago ----- 3 sixxs-asbnva-gw.customer.occaid.net (2001:4830:e6:7::2) 9.549 ms 10.652 ms 10.107 ms 4 iad0-b0-ge2.hotnic.net (2001:4810:0:100::1) 9.975 ms 11.044 ms 10.009 ms 5 10gigabitethernet2-2.core1.ash1.he.net (2001:504:0:2::6939:1) 17.423 ms 11.05 ms 12.27 ms 6 2001:559::db5 (2001:559::db5) 95.197 ms 95.968 ms 94.793 ms 7 he-2-6-0-0-cr01.ashburn.va.ibone.comcast.net (2001:558:0:f8d2::1) 105.158 ms 101.428 ms 94.993 ms 8 he-0-7-0-0-cr01.newyork.ny.ibone.comcast.net (2001:558:0:f5ba::2) 89.735 ms 90.266 ms 92.577 ms 9 he-0-11-0-0-cr01.350ecermak.il.ibone.comcast.net (2001:558:0:f5b8::2) 89.813 ms 92.963 ms 92.383 ms 10 he-0-10-0-0-pe04.350ecermak.il.ibone.comcast.net (2001:558:0:f8cc::2) 87.401 ms 88.15 ms 87.085 ms 11 2001:550:2:2::32:2 (2001:550:2:2::32:2) 122.387 ms 124.288 ms 122.409 ms -----
Ashburn -> Chicago -> New York -> Chicago ----- 3 sixxs-asbnva-gw.customer.occaid.net (2001:4830:e6:7::2) 9.926 ms 10.183 ms 9.978 ms 4 iad0-b0-ge2.hotnic.net (2001:4810:0:100::1) 9.961 ms 11.37 ms 9.973 ms 5 10gigabitethernet2-2.core1.ash1.he.net (2001:504:0:2::6939:1) 9.95 ms 18.258 ms 9.951 ms 6 2001:559::db5 (2001:559::db5) 94.959 ms 96.413 ms 95.001 ms 7 he-1-10-0-0-cr01.chicago.il.ibone.comcast.net (2001:558:0:f552::1) 92.457 ms 92.964 ms 89.965 ms 8 he-0-7-0-0-cr01.newyork.ny.ibone.comcast.net (2001:558:0:f5ba::2) 89.789 ms 91.291 ms 97.333 ms 9 he-0-11-0-0-cr01.350ecermak.il.ibone.comcast.net (2001:558:0:f5b8::2) 87.518 ms 95.961 ms 87.506 ms 10 he-0-10-0-0-pe04.350ecermak.il.ibone.comcast.net (2001:558:0:f8cc::2) 87.406 ms 86.414 ms 87.425 ms 11 2001:550:2:2::32:2 (2001:550:2:2::32:2) 87.517 ms 86.589 ms 87.506 ms -----
Thoughts?
Thanks,
Stephen
* Steve Meuse (smeuse@mara.org) wrote:
It's likely a reverse DNS error. If you look at the latency, it's within range of the previous hops.
Still curious that the systems (IPv6 addresses) are changing too.. It's not like it's the same route but just different rDNS results. It's also quite a bit of latency between he.net and Comcast. Also seeing ~20% packet loss to systems in Comcast and ~15% packet loss end-to-end. Certainly seems like there's something unhappy there, but I'll just keep an eye on it. Thanks! Stephen
I will follow-up offline.... -Steve On Wed, Dec 3, 2014 at 3:40 PM, Stephen Frost <sfrost@snowman.net> wrote:
* Steve Meuse (smeuse@mara.org) wrote:
It's likely a reverse DNS error. If you look at the latency, it's within range of the previous hops.
Still curious that the systems (IPv6 addresses) are changing too.. It's not like it's the same route but just different rDNS results. It's also quite a bit of latency between he.net and Comcast. Also seeing ~20% packet loss to systems in Comcast and ~15% packet loss end-to-end. Certainly seems like there's something unhappy there, but I'll just keep an eye on it.
Thanks!
Stephen
participants (2)
-
Stephen Frost -
Steve Meuse