Contact for Road Runner
Hello, I am looking to get in touch with anyone who is responsible for Routing Registry Objects at Road Runner Cable. Can you please reply back to me off list. (We need to have an older ASN RR Object Created by rr.com to be removed please). Thanks. Faisal Imtiaz Snappy Internet Telecom 7266 SW 48 Street Miami, FL 33155 Tel: 305 663 5518 x 232 Help-desk: (305)663-5518 Option 2 or Email: supp...@snappytelecom.net
re: Contact for Road Runner
Hey Faisal, We use to have peering with Road Runner (Bright House Networks) ~6 years ago. At that time, They created a RR object (RADB) for our AS that specifically said ROAD RUNNER. Which caused all kinds of havoc as some databases would pull that over the AS NAME when listing our network. They even updated the registry a couple of times in the years following our termination of their service. Emails to their RADB email, As well as to their direct support went completely unanswered. The solution for me was asking Merit (RADB's Parent company..whatever they are). To forcibly remove the entry, They did so about two hours after my email to them and were extremely helpful. Nick Olsen Network Operations (855) FLSPEED x106 From: Faisal Imtiaz fai...@snappytelecom.net Sent: Tuesday, May 27, 2014 9:52 AM To: NANOG nanog@nanog.org Subject: Contact for Road Runner Hello, I am looking to get in touch with anyone who is responsible for Routing Registry Objects at Road Runner Cable. Can you please reply back to me off list. (We need to have an older ASN RR Object Created by rr.com to be removed please). Thanks. Faisal Imtiaz Snappy Internet Telecom 7266 SW 48 Street Miami, FL 33155 Tel: 305 663 5518 x 232 Help-desk: (305)663-5518 Option 2 or Email: supp...@snappytelecom.net
Cogent / Internap issue ??
We are having troubles reaching services on the other side of cogent/internap peering. Anyone else seeing issues? Basically 14607 - 6128 - 174 - 14744. Type escape sequence to abort. Tracing the route to 72.5.52.199 VRF info: (vrf in name/id, vrf out name/id) 1 24.157.32.249 [AS 6128] 4 msec 4 msec 4 msec 2 24.38.117.6 [AS 6128] 4 msec 8 msec 4 msec 3 167.206.183.29 [AS 6128] 4 msec 4 msec 8 msec 4 * * * 5 * * * 6 154.54.47.17 [AS 174] 4 msec 154.54.47.29 [AS 174] 8 msec 154.54.44.69 [AS 174] 4 msec 7 66.28.4.202 [AS 174] 28 msec 28 msec 154.54.6.190 [AS 174] 28 msec 8 154.54.6.85 [AS 174] 40 msec 154.54.24.81 [AS 174] 36 msec 154.54.6.117 [AS 174] 40 msec 9 154.54.26.113 [AS 174] 52 msec 154.54.26.121 [AS 174] 52 msec 154.54.26.129 [AS 174] 48 msec 10 154.54.25.70 [AS 174] 64 msec 154.54.25.66 [AS 174] 60 msec 154.54.25.70 [AS 174] 60 msec 11 154.54.2.197 [AS 174] 92 msec 88 msec 84 msec 12 154.54.0.249 [AS 174] 80 msec 154.54.0.253 [AS 174] 80 msec 154.54.0.249 [AS 174] 84 msec 13 154.54.41.142 [AS 174] 152 msec 224 msec 92 msec 14 38.122.90.42 [AS 174] 84 msec 84 msec 38.104.124.82 [AS 174] 80 msec 15 63.251.160.18 [AS 14744] 76 msec 76 msec 72 msec 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * Matthew Huff | 1 Manhattanville Rd Director of Operations | Purchase, NY 10577 OTA Management LLC | Phone: 914-460-4039
crave your indulgence
If you wouldn’t mind a quick tracerooute - Can you confirm reachability to the following: 2001:500:84::b Thanks in advance. /bill Neca eos omnes. Deus suos agnoscet.
Re: crave your indulgence
traceroute to 2001:500:84::b (2001:500:84::b) from 2a04:840:0:2::8baf:41a6, 30 hops max, 24 byte packets 1 2a04:840:0:2::1 (2a04:840:0:2::1) 0.299 ms 0.299 ms 1.03 ms 2 2a00:1c10:3:667::a (2a00:1c10:3:667::a) 1.172 ms 1.42 ms 1.355 ms 3 rtr-23-121-141-2914.thn.v6.custdc.net (2a00:1c10::1::2914:161) 3.375 ms 2.768 ms 3.684 ms 4 ae-4.r23.londen03.uk.bb.gin.ntt.net (2001:728:0:2000::29) 1.866 ms 1.899 ms 1.866 ms 5 ae-3.r22.amstnl02.nl.bb.gin.ntt.net (2001:728:0:2000::16) 9.383 ms 36.228 ms 9.444 ms 6 ae-0.r23.amstnl02.nl.bb.gin.ntt.net (2001:418:0:2000::1c6) 9.367 ms 19.211 ms 9.387 ms 7 ae-7.r21.asbnva02.us.bb.gin.ntt.net (2001:418:0:2000::1b1) 91.736 ms 91.679 ms 91.688 ms 8 ae-0.r20.asbnva02.us.bb.gin.ntt.net (2001:418:0:2000::d) 102.92 ms 91.509 ms 91.442 ms 9 ae-2.r21.lsanca03.us.bb.gin.ntt.net (2001:418:0:2000::1f6) 156.269 ms 156.27 ms 156.435 ms 10 ae-2.r05.lsanca03.us.bb.gin.ntt.net (2001:418:0:2000::14e) 154.111 ms 153.917 ms 153.976 ms 11 * 2001:418:1401:1a::2 (2001:418:1401:1a::2) 150.113 ms * 12 2001:1878::181:177 (2001:1878::181:177) 172.279 ms 168.706 ms 160.806 ms 13 2001:500:84::b (2001:500:84::b) 156.772 ms 156.17 ms 148.251 ms On Tue, 27 May 2014 11:28:00 -0700 manning bill bmann...@isi.edu wrote: If you wouldn’t mind a quick tracerooute - Can you confirm reachability to the following: 2001:500:84::b Thanks in advance. /bill Neca eos omnes. Deus suos agnoscet.
Re: crave your indulgence
This seems like a perfect use for ATLAS: https://atlas.ripe.net/ On 5/27/2014 2:28 PM, manning bill wrote: If you wouldn’t mind a quick tracerooute - Can you confirm reachability to the following: 2001:500:84::b Thanks in advance. /bill Neca eos omnes. Deus suos agnoscet.
RE: Cogent / Internap issue ??
Just to clarify, it's not just a traceroute issue. I can't ping nor connect to port 80/443 to the ip address 72.5.52.199 from our network, although I can do both from an external shell account. It's very possible that it's a routing issue on the other side, and I'm reaching out to them as well. Matthew Huff | 1 Manhattanville Rd Director of Operations | Purchase, NY 10577 OTA Management LLC | Phone: 914-460-4039 -Original Message- From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Matthew Huff Sent: Tuesday, May 27, 2014 2:25 PM To: nanog@nanog.org Subject: Cogent / Internap issue ?? We are having troubles reaching services on the other side of cogent/internap peering. Anyone else seeing issues? Basically 14607 - 6128 - 174 - 14744. Type escape sequence to abort. Tracing the route to 72.5.52.199 VRF info: (vrf in name/id, vrf out name/id) 1 24.157.32.249 [AS 6128] 4 msec 4 msec 4 msec 2 24.38.117.6 [AS 6128] 4 msec 8 msec 4 msec 3 167.206.183.29 [AS 6128] 4 msec 4 msec 8 msec 4 * * * 5 * * * 6 154.54.47.17 [AS 174] 4 msec 154.54.47.29 [AS 174] 8 msec 154.54.44.69 [AS 174] 4 msec 7 66.28.4.202 [AS 174] 28 msec 28 msec 154.54.6.190 [AS 174] 28 msec 8 154.54.6.85 [AS 174] 40 msec 154.54.24.81 [AS 174] 36 msec 154.54.6.117 [AS 174] 40 msec 9 154.54.26.113 [AS 174] 52 msec 154.54.26.121 [AS 174] 52 msec 154.54.26.129 [AS 174] 48 msec 10 154.54.25.70 [AS 174] 64 msec 154.54.25.66 [AS 174] 60 msec 154.54.25.70 [AS 174] 60 msec 11 154.54.2.197 [AS 174] 92 msec 88 msec 84 msec 12 154.54.0.249 [AS 174] 80 msec 154.54.0.253 [AS 174] 80 msec 154.54.0.249 [AS 174] 84 msec 13 154.54.41.142 [AS 174] 152 msec 224 msec 92 msec 14 38.122.90.42 [AS 174] 84 msec 84 msec 38.104.124.82 [AS 174] 80 msec 15 63.251.160.18 [AS 14744] 76 msec 76 msec 72 msec 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * Matthew Huff | 1 Manhattanville Rd Director of Operations | Purchase, NY 10577 OTA Management LLC | Phone: 914-460-4039
Re: crave your indulgence
Looks good from here: Tracing route to 2001:500:84::b over a maximum of 30 hops 11 ms1 ms1 ms 2601:8:1400:880::1 2 *** Request timed out. 310 ms 9 ms 8 ms te-9-3-ur01.shadygrove.va.richmond.comcast.net [2001:558:182:fb::1] 4 9 ms 9 ms 7 ms xe-12-0-1-0-ar02.staplesmllrd.va.richmond.comcast.net [2001:558:180:25::1] 524 ms24 ms26 ms pos-3-10-0-0-cr01.56marietta.ga.ibone.comcast.net [2001:558:0:f6e6::1] 6 *** Request timed out. 723 ms24 ms23 ms 2001:559::1056 823 ms23 ms24 ms ae-6.r03.atlnga05.us.bb.gin.ntt.net [2001:418:0:2000::31] 942 ms76 ms90 ms ae-7.r21.dllstx09.us.bb.gin.ntt.net [2001:418:0:2000::37d] 1043 ms41 ms41 ms ae-0.r20.dllstx09.us.bb.gin.ntt.net [2001:418:0:2000::a9] 1171 ms73 ms90 ms ae-5.r20.lsanca03.us.bb.gin.ntt.net [2001:418:0:2000::295] 1271 ms72 ms74 ms ae-1.r05.lsanca03.us.bb.gin.ntt.net [2001:418:0:2000::116] 1373 ms72 ms74 ms 2001:418:1401:1a::2 1472 ms75 ms72 ms 2001:1878::181:177 1574 ms71 ms71 ms 2001:500:84::b On Tue, 27 May 2014 11:28:00 -0700 manning bill bmann...@isi.edu wrote: If you wouldn’t mind a quick tracerooute - Can you confirm reachability to the following: 2001:500:84::b Thanks in advance. /bill Neca eos omnes. Deus suos agnoscet.
Re: crave your indulgence
On 2014.05.27. 20:28, manning bill wrote: If you wouldn’t mind a quick tracerooute - Can you confirm reachability to the following: 2001:500:84::b Thanks in advance. /bill Neca eos omnes. Deus suos agnoscet. There should be a tool for this kind of thing! :-) https://atlas.ripe.net/atlas/udm.html?msm_id=1666831 or just the data (~1MB): https://atlas.ripe.net/api/v1/measurement/1666831/result/ Cheers, Robert
Re: crave your indulgence
Measurement: 1666834 should be bill's measurement request... 50 icmptraceroutes from around the globez. On Tue, May 27, 2014 at 2:35 PM, Brian Rak b...@gameservers.com wrote: This seems like a perfect use for ATLAS: https://atlas.ripe.net/ On 5/27/2014 2:28 PM, manning bill wrote: If you wouldn’t mind a quick tracerooute - Can you confirm reachability to the following: 2001:500:84::b Thanks in advance. /bill Neca eos omnes. Deus suos agnoscet.
Re: crave your indulgence
traceroute6 to 2001:500:84::b (2001:500:84::b) from 2620::930:0:28e6:7b60:e856:aad7, 64 hops max, 12 byte packets 1 2620:0:930::cafe:beef 82.620 ms 0.772 ms 1.622 ms 2 2620::930:0:2e6b:f5ff:fe03:a80 1.965 ms 3.523 ms 2.613 ms 3 owen-2.tunnel.tserv2.fmt.ipv6.he.net 16.909 ms 18.061 ms 17.007 ms 4 ge5-10.core1.fmt1.he.net 17.122 ms 22.394 ms 15.948 ms 5 10ge3-4.core3.fmt2.he.net 18.848 ms 16.894 ms 19.103 ms 6 10ge12-1.core1.lax1.he.net 26.129 ms 27.115 ms 25.247 ms 7 10ge1-3.core1.lax2.he.net 24.409 ms 24.877 ms 25.065 ms 8 * 2001:504:13::210:43 28.831 ms 28.393 ms 9 2001:1878::181:177 31.308 ms 29.668 ms 25.611 ms 10 2001:500:84::b 24.900 ms 220.098 ms 188.378 ms
Re: crave your indulgence
On Tuesday, May 27, 2014 08:28:00 PM manning bill wrote: If you wouldn’t mind a quick tracerooute - Can you confirm reachability to the following: 2001:500:84::b From Mombasa, Kenya (you're welcome to use http://lg.seacomnet.com/): lg-01-mba.ketraceroute 2001:500:84::b Type escape sequence to abort. Tracing the route to 2001:500:84::B 1 ge-1-0-0-213.mba6-201-access-3.mpls.seacomnet.com (2C0F:FEB0:5:::1) [AS 37100] 0 msec 0 msec 0 msec 2 xe-3-0-0.lon6-201-access-3.mpls.seacomnet.com (2C0F:FEB0:0:20::1) [AS 37100] 452 msec 268 msec 632 msec 3 xe-0-0-0-0.pp6-01-lhr.uk.seacomnet.com (2C0F:FEB0:0:23::6) [AS 37100] 132 msec 132 msec 128 msec 4 40ge1-3.core1.lon2.he.net (2001:7F8:4::1B1B:1) [AS 5459] 220 msec 216 msec 192 msec 5 100ge1-1.core1.nyc4.he.net (2001:470:0:2CF::2) [AS 6939] 224 msec 232 msec 228 msec 6 10ge10-3.core1.lax1.he.net (2001:470:0:10E::1) [AS 6939] 292 msec 268 msec 272 msec 7 10ge1-3.core1.lax2.he.net (2001:470:0:72::2) [AS 6939] 260 msec 268 msec 272 msec 8 * usclos-nettos.gigabitethernet4-11.core1.lax2.he.net (2001:470:1:3E8::2) 256 msec * 9 2001:1878::181:177 [AS 226] 288 msec 284 msec 296 msec 10 2001:500:84::B [AS 226] 292 msec 264 msec 276 msec lg-01-mba.ke Cheers, Mark. signature.asc Description: This is a digitally signed message part.
Re: crave your indulgence
At 14:47 27/05/2014 -0400, Christopher Morrow wrote: Measurement: 1666834 should be bill's measurement request... 50 icmptraceroutes from around the globez. Or ring-ping and ring-trace: https://ring.nlnog.net/toolbox/ -Hank On Tue, May 27, 2014 at 2:35 PM, Brian Rak b...@gameservers.com wrote: This seems like a perfect use for ATLAS: https://atlas.ripe.net/ On 5/27/2014 2:28 PM, manning bill wrote: If you wouldn't mind a quick tracerooute - Can you confirm reachability to the following: 2001:500:84::b Thanks in advance. /bill Neca eos omnes. Deus suos agnoscet.
RIPE Atlas data parsing
Folks, Yes, RIPE Atlas is great. It generates output as JSON. Is there dummy tool for summarizing this JSON data and possibly visualizing it? I could write my own, but i imagine someone has already done this somewhere. No? CB
Re: RIPE Atlas data parsing
On 2014.05.27. 21:28, Ca By wrote: Folks, Yes, RIPE Atlas is great. It generates output as JSON. Is there dummy tool for summarizing this JSON data and possibly visualizing it? I could write my own, but i imagine someone has already done this somewhere. No? CB These may help: https://github.com/RIPE-NCC/ripe.atlas.sagan
Re: RIPE Atlas data parsing
On Tue, May 27, 2014 at 12:28:30PM -0700, Ca By cb.li...@gmail.com wrote a message of 9 lines which said: Is there dummy tool for summarizing this JSON data and possibly visualizing it? On Atlas Web site, there is the Seismograph (an interactive tool). I don't use it myself. There are many sample programs on: https://github.com/RIPE-Atlas-Community/ripe-atlas-community-contrib See for instance reachability+retrieve.py There is now a new library to help parsing, called Sagan: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-latest-results-api-and-parsing-library (I used it only a little) You may also look at the tutorial: https://ripe67.ripe.net/presentations/153-ripe-atlas-udm-api-1.pdf
Re: crave your indulgence
# ADDRESS LOSS SENTLAST AVGBEST WORST STD-DEV STATUS 1 2001:504:13::1a0%6 8.4ms12.2 8.4 19.9 5.3 2 2001:470:1:3e8::2 0%6 9.2ms 9.2 9.1 9.4 0.1 3 2001:1878::181:177 0%6 8.8ms 9 8.8 10 0.4 4 2001:500:84::b 0%6 9ms 8.7 8.6 9 0.1 On Tue, May 27, 2014 at 11:59 AM, Hank Nussbacher h...@efes.iucc.ac.ilwrote: At 14:47 27/05/2014 -0400, Christopher Morrow wrote: Measurement: 1666834 should be bill's measurement request... 50 icmptraceroutes from around the globez. Or ring-ping and ring-trace: https://ring.nlnog.net/toolbox/ -Hank On Tue, May 27, 2014 at 2:35 PM, Brian Rak b...@gameservers.com wrote: This seems like a perfect use for ATLAS: https://atlas.ripe.net/ On 5/27/2014 2:28 PM, manning bill wrote: If you wouldn't mind a quick tracerooute - Can you confirm reachability to the following: 2001:500:84::b Thanks in advance. /bill Neca eos omnes. Deus suos agnoscet.
Re: RIPE Atlas data parsing
I'm using Graphite (http://graphite.readthedocs.org) - I plan on blogging how I'm doing it at some point, but it's not all that difficult. Dan On 27 May 2014 20:41, Stephane Bortzmeyer bortzme...@nic.fr wrote: On Tue, May 27, 2014 at 12:28:30PM -0700, Ca By cb.li...@gmail.com wrote a message of 9 lines which said: Is there dummy tool for summarizing this JSON data and possibly visualizing it? On Atlas Web site, there is the Seismograph (an interactive tool). I don't use it myself. There are many sample programs on: https://github.com/RIPE-Atlas-Community/ripe-atlas-community-contrib See for instance reachability+retrieve.py There is now a new library to help parsing, called Sagan: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-latest-results-api-and-parsing-library (I used it only a little) You may also look at the tutorial: https://ripe67.ripe.net/presentations/153-ripe-atlas-udm-api-1.pdf
Re: Cogent / Internap issue ??
On 5/27/2014 11:24 AM, Matthew Huff wrote: We are having troubles reaching services on the other side of cogent/internap peering. Anyone else seeing issues? We haven't seen Cogent-related issues at SEF today and that IP address is currently pingable through the Cogent looking glass. From your trace, Internap's equipment is reachable and responding (the two last hops are Internap-controlled), so the actual endpoint network (beyond Internap) seems to be either explicitly filtering your source or sending traffic back to it over a different and broken path. The Internap NOC is responsive when it comes to investigating routing problems, so they're a good place to turn for such concerns. If you're having problems reaching them or would like some external help in exploring the problem from inside and outside that PNAP, shoot me an email off-list. -John
Re: rz.verisign-grs.com root zone ftp access
On 5/20/14, 11:53 PM, John Levine wrote: In article 537c1f17.6070...@digital-z.com you write: On 5/20/14, 4:21 PM, Brandon Applegate wrote: Is anyone using this and having failed login for a few days now ? I�ve been mirroring the root zone(s) for years and I just started getting failures in my logs. I emailed an address I found on the Verisign website but so far dead air. If anyone knows of a more pointed email POC that would actually have clue about this that would be awesome. I have been experiencing this problem as well but have not had a chance to look into it. It stopped working some time between May 15th and May 16th. If you find out anything, please let me know! When I had problems like this a while ago, I found their support people to be quite responsive. Try writing them at tldz...@verisign-grs.com or call the support number on the web site 703-925-6999. If you're not using your password to download the .COM or .NET zones, it is my impression that they will eventually turn off your password because they think you're not using it. R's, John Just wanted to follow-up on this issue. I was actively using it every day to fetch the .COM and .NET TLD zone files. Sent multiple emails to tldz...@verisign-grs.com with no response. Finally reached out to them via chat and was informed that I needed to execute a new zone file access agreement because they needed updated information for me. New agreement has been submitted so we will see what they say this time. If anyone else is still having problems then you probably need to do the same. --Blaine
Re: rz.verisign-grs.com root zone ftp access
Hi Doug, IIRC you can ftp to rs.internic.net (the IANA) and download zones to your hearts content. At least until transition, I'd think this one is authoritative. I don't exactly remember where you can pull it from, but I believe they offer it in XML too. [ Paging Joe Abley ] Best, -M On Wed, May 21, 2014 at 1:50 AM, Doug Barton do...@dougbarton.us wrote: The last time I asked them, F-root had a we allow it because it's the right thing to do but we don't like it policy. Given that ICANN operates an infrastructure purposely built for doing zone transfers, and given that they offer more zones than are on the roots, that's the way I recommend people go. YMMV. Doug On 05/20/2014 10:42 PM, Mehmet Akcin wrote: F-root also allows you to axfr root-zone ( dig @f.root-servers.net . axfr ) On May 20, 2014, at 10:32 PM, Doug Barton do...@dougbarton.us wrote: Signed PGP part On 05/20/2014 02:21 PM, Brandon Applegate wrote: | Is anyone using this and having failed login for a few days now ? I?ve been mirroring the root zone(s) for years and I just started getting failures in my logs. I emailed an address I found on the Verisign website but so far dead air. If anyone knows of a more pointed email POC that would actually have clue about this that would be awesome. You can slave the root and more directly from ICANN: http://www.dns.icann.org/services/axfr/
Re: rz.verisign-grs.com root zone ftp access
Pretty annoying (esp. to my databases) that com.zone.gz alone is 2.3 GB ... . On Tue, May 27, 2014 at 6:21 PM, Blaine Fleming gro...@digital-z.com wrote: On 5/20/14, 11:53 PM, John Levine wrote: In article 537c1f17.6070...@digital-z.com you write: On 5/20/14, 4:21 PM, Brandon Applegate wrote: Is anyone using this and having failed login for a few days now ? I�ve been mirroring the root zone(s) for years and I just started getting failures in my logs. I emailed an address I found on the Verisign website but so far dead air. If anyone knows of a more pointed email POC that would actually have clue about this that would be awesome. I have been experiencing this problem as well but have not had a chance to look into it. It stopped working some time between May 15th and May 16th. If you find out anything, please let me know! When I had problems like this a while ago, I found their support people to be quite responsive. Try writing them at tldz...@verisign-grs.com or call the support number on the web site 703-925-6999. If you're not using your password to download the .COM or .NET zones, it is my impression that they will eventually turn off your password because they think you're not using it. R's, John Just wanted to follow-up on this issue. I was actively using it every day to fetch the .COM and .NET TLD zone files. Sent multiple emails to tldz...@verisign-grs.com with no response. Finally reached out to them via chat and was informed that I needed to execute a new zone file access agreement because they needed updated information for me. New agreement has been submitted so we will see what they say this time. If anyone else is still having problems then you probably need to do the same. --Blaine -- jamie rishaw // .com.arpa@j - reverse it. ish. ...let's consider this world like a family and care about each other... -Malala Yousafzai
Re: [dns-wg] crave your indulgence
If you wouldn't mind a quick tracerooute - Can you confirm reachability to the following: 2001:500:84::b Thanks in advance. traceroute6 to 2001:500:84::b (2001:500:84::b) from 2a04:b900::1:0:0:15, 64 hops max, 12 byte packets 1 office.bijgepunt.nlnetlabs.nl 0.333 ms 0.314 ms 0.308 ms 2 2a02:d28:5580:e:1000::245 0.589 ms 0.611 ms 0.507 ms 3 eth1-1.core1.ams1.nl.as5580.net 0.554 ms 0.549 ms 0.536 ms 4 eth1-8.r1.ams2.nl.as5580.net 0.694 ms 13.099 ms 4.514 ms 5 30gigabitethernet1-3.core1.ams1.he.net 8.437 ms 1.450 ms 1.651 ms 6 100ge9-1.core1.lon2.he.net 17.578 ms 7.245 ms 17.896 ms 7 100ge1-1.core1.nyc4.he.net 86.636 ms 82.937 ms 103.756 ms 8 10ge10-3.core1.lax1.he.net 159.165 ms 164.547 ms 153.020 ms 9 10ge1-3.core1.lax2.he.net 158.396 ms 153.472 ms 152.610 ms 10 2001:504:13::210:43 153.222 ms 154.124 ms 153.499 ms 11 2001:1878::181:177 153.629 ms 153.891 ms 153.103 ms 12 2001:500:84::b 153.426 ms 153.167 ms 152.977 ms
