Roy 10,832 / 0 Report Post Posted March 18, 2019 6 minutes ago, Liloz01 said: @Roy First - A college computer Second - My laptop running off of my mobile hotspot (I've played games like this before, don't judge) The first trace route being a college computer makes sense. I think your college may be blocking that IP since it doesn't even leave the internal network, lol. The high latency on the second trace route now makes sense since you're using a mobile hot spot haha. Thanks! Share this post Link to post Share on other sites More sharing options...
Ben 2,378 / 31,856 Report Post Posted March 18, 2019 · Hidden Hidden Bring me Atlanta location or I'll riot! (╯°□°）╯︵ ┻━┻ Joking asides, I'm really excited about this. I see Atlanta location, I hype up because I like nearby servers. Hence why I have a OpenVZ VPS in Atlanta. Share this post Link to post
Fafy 391 / 8,511 Report Post Posted March 18, 2019 Edited March 18, 2019 by Fafy · Hidden Hidden Location: Argentina, Buenos Aires (Province), La Plata (City) C:\Users\usuario>tracert 92.119.148.5 Traza a 92.119.148.5 sobre caminos de 30 saltos como máximo. 1 <1 ms <1 ms <1 ms 192.168.1.1 [192.168.1.1] 2 3 ms 2 ms 2 ms 10.100.100.1 [10.100.100.1] 3 3 ms 3 ms 2 ms 143.208.36.241 4 5 ms 4 ms 4 ms static1.100.12.190.cps.com.ar [190.12.100.1] 5 4 ms 4 ms 4 ms static.40.192.104.190.cps.com.ar [190.104.192.40 ] 6 5 ms 4 ms 4 ms 195.22.220.113 7 34 ms 33 ms 31 ms et11-1-0.sanpaolo8.spa.seabone.net [195.22.219.1 45] 8 141 ms 141 ms 142 ms ntt-verio.sanpaolo8.spa.seabone.net [149.3.181.6 5] 9 141 ms 140 ms 141 ms ae-8.r24.nycmny01.us.bb.gin.ntt.net [129.250.2.1 2] 10 141 ms 141 ms 140 ms ae-1.r07.nycmny01.us.bb.gin.ntt.net [129.250.3.1 81] 11 141 ms 141 ms 140 ms ae-0.a02.nycmny01.us.bb.gin.ntt.net [129.250.6.5 1] 12 150 ms 141 ms 173 ms ae-1.choopa.nycmny01.us.bb.gin.ntt.net [128.241. 2.250] 13 141 ms 142 ms 141 ms vl42-br2.pnj1.choopa.net [108.61.2.89] 14 * * * Tiempo de espera agotado para esta solicitud. 15 * * * Tiempo de espera agotado para esta solicitud. 16 * * * Tiempo de espera agotado para esta solicitud. 17 * * * Tiempo de espera agotado para esta solicitud. 18 * * * Tiempo de espera agotado para esta solicitud. 19 * * * Tiempo de espera agotado para esta solicitud. 20 * * * Tiempo de espera agotado para esta solicitud. 21 * * * Tiempo de espera agotado para esta solicitud. 22 * * * Tiempo de espera agotado para esta solicitud. 23 * * * Tiempo de espera agotado para esta solicitud. 24 * * * Tiempo de espera agotado para esta solicitud. 25 * * * Tiempo de espera agotado para esta solicitud. 26 * * * Tiempo de espera agotado para esta solicitud. 27 * * * Tiempo de espera agotado para esta solicitud. 28 * * * Tiempo de espera agotado para esta solicitud. 29 * * * Tiempo de espera agotado para esta solicitud. 30 * * * Tiempo de espera agotado para esta solicitud. Traza completa. Edited March 18, 2019 by Fafy Share this post Link to post
juky 131 / 4,515 Report Post Posted March 18, 2019 · Hidden Hidden Antwerp, Belgium juky@DESKTOP-9M2VO72 ~ $ tracert 92.119.148.5 Tracing route to 92.119.148.5 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.168.1.1 2 9 ms 13 ms 7 ms d54c09001.access.telenet.be [84.192.144.1] 3 10 ms 11 ms 8 ms dd5e0cc99.access.telenet.be [213.224.204.153] 4 9 ms 10 ms 9 ms dd5e0fa7b.access.telenet.be [213.224.250.123] 5 10 ms 8 ms 11 ms brx-b2-link.telia.net [80.239.132.217] 6 15 ms 17 ms 17 ms prs-bb3-link.telia.net [62.115.112.142] 7 16 ms 17 ms 17 ms prs-b7-link.telia.net [62.115.113.183] 8 * * * Request timed out. 9 * * * Request timed out. 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 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 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Trace complete. Share this post Link to post
Roy 10,832 / 0 Report Post Posted March 18, 2019 1 hour ago, Fafy said: Location: Argentina, Buenos Aires (Province), La Plata (City) C:\Users\usuario>tracert 92.119.148.5 Traza a 92.119.148.5 sobre caminos de 30 saltos como máximo. 1 <1 ms <1 ms <1 ms 192.168.1.1 [192.168.1.1] 2 3 ms 2 ms 2 ms 10.100.100.1 [10.100.100.1] 3 3 ms 3 ms 2 ms 143.208.36.241 4 5 ms 4 ms 4 ms static1.100.12.190.cps.com.ar [190.12.100.1] 5 4 ms 4 ms 4 ms static.40.192.104.190.cps.com.ar [190.104.192.40 ] 6 5 ms 4 ms 4 ms 195.22.220.113 7 34 ms 33 ms 31 ms et11-1-0.sanpaolo8.spa.seabone.net [195.22.219.1 45] 8 141 ms 141 ms 142 ms ntt-verio.sanpaolo8.spa.seabone.net [149.3.181.6 5] 9 141 ms 140 ms 141 ms ae-8.r24.nycmny01.us.bb.gin.ntt.net [129.250.2.1 2] 10 141 ms 141 ms 140 ms ae-1.r07.nycmny01.us.bb.gin.ntt.net [129.250.3.1 81] 11 141 ms 141 ms 140 ms ae-0.a02.nycmny01.us.bb.gin.ntt.net [129.250.6.5 1] 12 150 ms 141 ms 173 ms ae-1.choopa.nycmny01.us.bb.gin.ntt.net [128.241. 2.250] 13 141 ms 142 ms 141 ms vl42-br2.pnj1.choopa.net [108.61.2.89] 14 * * * Tiempo de espera agotado para esta solicitud. 15 * * * Tiempo de espera agotado para esta solicitud. 16 * * * Tiempo de espera agotado para esta solicitud. 17 * * * Tiempo de espera agotado para esta solicitud. 18 * * * Tiempo de espera agotado para esta solicitud. 19 * * * Tiempo de espera agotado para esta solicitud. 20 * * * Tiempo de espera agotado para esta solicitud. 21 * * * Tiempo de espera agotado para esta solicitud. 22 * * * Tiempo de espera agotado para esta solicitud. 23 * * * Tiempo de espera agotado para esta solicitud. 24 * * * Tiempo de espera agotado para esta solicitud. 25 * * * Tiempo de espera agotado para esta solicitud. 26 * * * Tiempo de espera agotado para esta solicitud. 27 * * * Tiempo de espera agotado para esta solicitud. 28 * * * Tiempo de espera agotado para esta solicitud. 29 * * * Tiempo de espera agotado para esta solicitud. 30 * * * Tiempo de espera agotado para esta solicitud. Traza completa. Interesting. I plan to at some point get PoPs in South America. But for some reason you're being routed to the NYC PoP instead of something like Miami (preferred based on your location) or Dallas. If you can, would you be able to PM me your public IPv4 address? I'd like to investigate this further. I may ask to do trace routes to specific PoPs themselves if that's okay. Thank you. Share this post Link to post Share on other sites More sharing options...
Vauff 965 / 16,971 Report Post Posted March 18, 2019 · Hidden Hidden Location - Southern Ontario, Canada Trace Route - Tracing route to 92.119.148.5 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.168.1.1 2 13 ms 12 ms 7 ms 10.75.192.1 3 13 ms 13 ms 21 ms 185-2-226-24.rev.cgocable.net [24.226.2.185] 4 18 ms 13 ms 15 ms 10.0.18.73 5 15 ms 32 ms 17 ms toro-b1-link.telia.net [62.115.54.234] 6 24 ms 29 ms 24 ms chi-b21-link.telia.net [62.115.118.230] 7 27 ms 29 ms 28 ms vultr-ic-318445-chi-b21.c.telia.net [62.115.148.197] 8 * * * Request timed out. 9 * * * Request timed out. 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 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 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Trace complete. Share this post Link to post
SwegBuster 879 / 15,758 Report Post Posted March 19, 2019 · Hidden Hidden Location: Hillsboro, Oregon Tracert: Microsoft Windows [Version 10.0.17134.648] (c) 2018 Microsoft Corporation. All rights reserved. C:\Users\zws11>tracert 92.119.148.5 Tracing route to 92.119.148.5 over a maximum of 30 hops 1 1 ms <1 ms <1 ms 10.0.0.1 2 8 ms 9 ms 7 ms 96.120.60.125 3 9 ms 9 ms 7 ms ae-111-rur01.beaverton.or.bverton.comcast.net [162.151.214.209] 4 10 ms 9 ms 12 ms ae-2-rur02.beaverton.or.bverton.comcast.net [68.85.243.154] 5 9 ms 9 ms 30 ms ae-51-ar01.troutdale.or.bverton.comcast.net [68.87.216.105] 6 17 ms 17 ms 16 ms be-33490-cr01.seattle.wa.ibone.comcast.net [68.86.92.217] 7 30 ms 30 ms 31 ms be-10825-cr01.9greatoaks.ca.ibone.comcast.net [68.86.85.198] 8 39 ms 36 ms 37 ms be-11525-cr02.losangeles.ca.ibone.comcast.net [68.86.84.149] 9 36 ms 36 ms 43 ms be-11599-pe01.losangeles.ca.ibone.comcast.net [68.86.84.194] 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 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 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Trace complete. C:\Users\zws11> Share this post Link to post
Bae 2,489 / 41,520 Report Post Posted March 19, 2019 · Hidden Hidden Location: Stafford, TX Traceroute: C:\Users\deput>tracert 92.119.148.5 Tracing route to 92.119.148.5 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.168.1.1 2 11 ms 10 ms 10 ms 96.120.17.233 3 19 ms 18 ms 14 ms 69.139.211.85 4 11 ms 11 ms 11 ms ae-2-rur02.alief.tx.houston.comcast.net [68.85.247.178] 5 19 ms 16 ms 13 ms ae-17-ar01.bearcreek.tx.houston.comcast.net [68.85.245.33] 6 21 ms 18 ms 14 ms be-33662-cr02.dallas.tx.ibone.comcast.net [68.86.92.61] 7 40 ms 42 ms 40 ms be-12224-cr02.miami.fl.ibone.comcast.net [68.86.86.141] 8 41 ms 45 ms 44 ms be-12274-pe01.nota.fl.ibone.comcast.net [68.86.82.154] 9 41 ms 41 ms 44 ms 96-87-8-30-static.hfc.comcastbusiness.net [96.87.8.30] 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 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 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Trace complete. credits to @Clavers Share this post Link to post Achievements
Roy 10,832 / 0 Report Post Posted March 19, 2019 @SwegBuster @Bae Hm. Both of you should be routed to a different PoP. Swegbuster should be routed to the PoP in Seattle, WA and Bae should be routed to the PoP in Dallas. I will investigate this later on and see what BGP/BIRD filters I can change. Thanks. Share this post Link to post Share on other sites More sharing options...
SwegBuster 879 / 15,758 Report Post Posted March 19, 2019 · Hidden Hidden 6 hours ago, Roy said: @SwegBuster @Bae Hm. Both of you should be routed to a different PoP. Swegbuster should be routed to the PoP in Seattle, WA and Bae should be routed to the PoP in Dallas. I will investigate this later on and see what BGP/BIRD filters I can change. Thanks. I do actually get routed to Seattle before going to LA. The others are closer to my state so. Thanks. Share this post Link to post
Guest Report Post Posted March 19, 2019 · Hidden Hidden Location - Sterling, VA Trace Route - Tracing route to 92.119.148.5 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.168.1.1 2 9 ms 11 ms 7 ms 92.119.148.5 Trace complete. Share this post Link to post
Roy 10,832 / 0 Report Post Posted March 19, 2019 28 minutes ago, SwegBuster said: I do actually get routed to Seattle before going to LA. The others are closer to my state so. Thanks. Yes, but it routes you from a hop in Seattle all the way to the PoP we have in Los Angeles (this would just add latency since you're being routed to Seattle and back to Los Angeles) instead of just going to the PoP we have in Seattle. This is most likely due to the route to Los Angeles having less hops than the route to the Seattle PoP (Anycast picks the closest PoP based off of the amount of hops it takes to get to each PoP I believe). This leads to a routing issue. I may PM you asking if you can perform a trace route to our Seattle PoP server so I can see what route you're taking to there and then make optimizations where necessary. I will admit though, if our physical server is in Dallas, you're better off being routed to the Los Angeles PoP. However, the Seattle PoP is still technically closer. Therefore, there is still optimizing we have to perform with the routing. I've noticed our Seattle and Dallas PoPs having the least amount of traffic and these are the two PoPs we have the most routing issues with. Once I get more experience with BIRD/BGP configuration, myself or @Dreae (he is definitely more experienced with this) should be able to correct this. I am trying to find out how advanced/specific the BIRD configuration can go. It'd be really cool if we could optimize certain routes based off of the destination IP. For example, the IPs that get forwarded to the physical server in Dallas, it'd be better to prefer you to the Los Angeles PoP but if a physical server is in Chicago, you'd be better off getting routed to the Seattle PoP. I'm not sure if this is even possible, though. Thanks! Share this post Link to post Share on other sites More sharing options...
Roy 10,832 / 0 Report Post Posted March 19, 2019 8 minutes ago, RainGamma said: Location - Sterling, VA Trace Route - Tracing route to 92.119.148.5 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.168.1.1 2 9 ms 11 ms 7 ms 92.119.148.5 Trace complete. That is the best trace route I've seen lmao. I honestly don't even know how you got a reply from the IP itself, lol. Thanks. Share this post Link to post Share on other sites More sharing options...
Guest Report Post Posted March 19, 2019 · Hidden Hidden 1 minute ago, Roy said: That is the best trace route I've seen lmao. Thanks. I have one gig ethernet. Share this post Link to post
Roy 10,832 / 0 Report Post Posted March 19, 2019 5 minutes ago, RainGamma said: I have one gig ethernet. I hate to break it to ya, but we don't even have a PoP in Virginia and I'm not sure how you're even getting a reply from the Anycast IP itself. I think your ISP is doing something fucky, lol. I'm just not sure what. Still though, 9ms is pretty good You're probably getting routed to the NYC PoP. Thanks. Share this post Link to post Share on other sites More sharing options...
Guest Report Post Posted March 19, 2019 · Hidden Hidden Just now, Roy said: I hate to break it to ya, but we don't even have a PoP in Virginia and I'm not sure how you're even getting a reply from the Anycast IP itself. I think your ISP is doing something weird, lol. I'm just not sure what. Still though, 9ms is pretty good You're probably getting routed to the NYC PoP. Thanks. oh ok! Share this post Link to post
King_Wailord 965 / 15,577 Report Post Posted March 19, 2019 · Hidden Hidden Location: Zionsville, Indiana Traceroute: Tracing route to 92.119.148.5 over a maximum of 30 hops 1 3 ms 2 ms 4 ms testwifi.here [192.168.86.1] 2 3 ms 2 ms 4 ms 192.168.0.1 3 9 ms 6 ms 8 ms cytninhed11-dy1001-secondary4.network.tds.net [96.60.208.1] 4 9 ms 10 ms 10 ms cytnindst52-tg0-7-0-0.network.tds.net [64.50.231.113] 5 31 ms 30 ms 32 ms h64-50-224-143.mdsnwi.tisp.static.tds.net [64.50.224.143] 6 35 ms 30 ms 31 ms nyiix.gi3-6.cr1.nyc1.choopa.net [198.32.160.157] 7 29 ms 30 ms 34 ms vl42-br2.pnj1.choopa.net [108.61.2.89] 8 * * * Request timed out. 9 * * * Request timed out. 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 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 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Trace complete. Share this post Link to post Achievements
Roy 10,832 / 0 Report Post Posted March 19, 2019 1 hour ago, King_Wailord said: Location: Zionsville, Indiana Traceroute: Tracing route to 92.119.148.5 over a maximum of 30 hops 1 3 ms 2 ms 4 ms testwifi.here [192.168.86.1] 2 3 ms 2 ms 4 ms 192.168.0.1 3 9 ms 6 ms 8 ms cytninhed11-dy1001-secondary4.network.tds.net [96.60.208.1] 4 9 ms 10 ms 10 ms cytnindst52-tg0-7-0-0.network.tds.net [64.50.231.113] 5 31 ms 30 ms 32 ms h64-50-224-143.mdsnwi.tisp.static.tds.net [64.50.224.143] 6 35 ms 30 ms 31 ms nyiix.gi3-6.cr1.nyc1.choopa.net [198.32.160.157] 7 29 ms 30 ms 34 ms vl42-br2.pnj1.choopa.net [108.61.2.89] 8 * * * Request timed out. 9 * * * Request timed out. 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 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 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Trace complete. You'd probably be better off being routed to the Chicago PoP. I can look into this later. Thanks. Share this post Link to post Share on other sites More sharing options...
Roy 10,832 / 0 Report Post Posted March 21, 2019 Just a heads up, every PoP server besides Dallas is offline at the moment (the BIRD daemon isn't running). We are trying to fix the route from our physical machine to the Dallas PoP and experiencing issues. Once we fix this, we'll put all the rest of the PoPs back up. This means every trace route performed will route to the Dallas PoP regardless of location, etc. Thank you. Share this post Link to post Share on other sites More sharing options...
Remuchu 103 / 2,638 Report Post Posted March 21, 2019 · Hidden Hidden 8 hours ago, Roy said: Just a heads up, every PoP server besides Dallas is offline at the moment (the BIRD daemon isn't running). We are trying to fix the route from our physical machine to the Dallas PoP and experiencing issues. Once we fix this, we'll put all the rest of the PoPs back up. This means every trace route performed will route to the Dallas PoP regardless of location, etc. Thank you. If it helps i can run tr again, just let me know! -Location Louisiana Share this post Link to post
