- Test - lists.nanog.org

godaddy contacts
by DurgaPrasad - DatasoftComnet 20 Dec '18

20 Dec '18

Hi, Is anyone from godaddy in this list? We believe they are announcing our BGP pool. The IP in 17th hop IP pool is ours as a result some of our customers are not able to login to godaddy. C:\Users\DP>tracert sso.godaddy.com Tracing route to sso.godaddy.com [104.238.65.153] over a maximum of 30 hops: 1 2 ms 1 ms 3 ms 192.168.225.1 2 4 ms 2 ms 2 ms 10.24.0.1 3 4 ms 2 ms 3 ms 103.40.48.13 4 4 ms 2 ms 2 ms vbc-10g-ccr.vbctv.in [123.108.200.5] 5 4 ms 2 ms 2 ms vbc-10g-asr.vbctv.in [123.108.200.42] 6 5 ms 2 ms 2 ms 14.142.71.141.static-hydrabad.vsnl.net.in [14.142.71.141] 7 26 ms 32 ms 27 ms 172.25.81.134 8 46 ms 33 ms 35 ms ix-ae-0-4.tcore1.mlv-mumbai.as6453.net [180.87.38.5] 9 150 ms 148 ms 147 ms if-ae-5-2.tcore1.wyn-marseille.as6453.net [180.87.38.126] 10 147 ms 147 ms 146 ms if-ae-8-1600.tcore1.pye-paris.as6453.net [80.231.217.6] 11 147 ms 145 ms 145 ms if-ae-11-2.tcore1.pvu-paris.as6453.net [80.231.153.49] 12 * * 143 ms 80.231.153.66 13 * 318 ms * ae-1-11.bear1.Phoenix1.Level3.net [4.69.210.157] 14 274 ms 337 ms 305 ms THE-GO-DADD.bear1.Phoenix1.Level3.net [4.16.142.186] 15 329 ms 278 ms 340 ms ip-148-72-32-9.ip.secureserver.net [148.72.32.9] 16 269 ms 282 ms 315 ms ip-184-168-0-117.ip.secureserver.net [184.168.0.117] 17 333 ms 289 ms 288 ms 125.62.192.197 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 291 ms 275 ms 273 ms ip-104-238-65-153.ip.secureserver.net [104.238.65.153] Trace complete. Regards Durga Prasad --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

2 1

routeviews.org pending delete
by Siyuan Miao 20 Dec '18

20 Dec '18

All, routeviews.org is pending delete now. Domain Name: ROUTEVIEWS.ORG Registry Domain ID: D48496876-LROR Registrar WHOIS Server: whois.networksolutions.com Registrar URL: http://www.networksolutions.com Updated Date: 2018-12-17T09:33:18Z Creation Date: 2000-12-14T23:05:47Z Registry Expiry Date: 2019-12-14T23:05:47Z Registrar Registration Expiration Date: Registrar: Network Solutions, LLC Registrar IANA ID: 2 Registrar Abuse Contact Email: abuse(a)web.com Registrar Abuse Contact Phone: +1.8003337680 Reseller: Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Domain Status: autoRenewPeriod https://icann.org/epp#autoRenewPeriod Registrant Organization: Network Solutions LLC Registrant State/Province: FL Registrant Country: US Name Server: NS1.PENDINGRENEWALDELETION.COM Name Server: NS2.PENDINGRENEWALDELETION.COM DNSSEC: unsigned URL of the ICANN Whois Inaccuracy Complaint Form https://www.icann.org/wicf/ ) >>> Last update of WHOIS database: 2018-12-17T12:28:37Z <<< routeviews.org. 86400 IN NS ns2.pendingrenewaldeletion.com. routeviews.org. 86400 IN NS ns1.pendingrenewaldeletion.com. I was wondering if there is anyone here can contact them to renew it if this project is still alive. Regards, Siyuan

3 2

Salesmen: ARIN Records are NOT Leads
by Izaac 19 Dec '18

19 Dec '18

Just a reminder. Grrr. -- . ___ ___ . . ___ . \ / |\ |\ \ . _\_ /__ |-\ |-\ \__

9 9

Network Atlas End of Year 2018 Update
by Mehmet Akcin 19 Dec '18

19 Dec '18

NANOG Friends, The final month of 2018 is going to be a busy one for Network Atlas, and while I still have a few spare hours, I wanted to share some exciting updates and address a few questions. First, I would like to thank all the people who believe in Network Atlas and have helped it get to where it is today. Network Atlas is at its heart a community concept, and it is energizing to see so many of you excited about its potential and interested in making it better. To that end, the Network Atlas team will be spending the next month working feverishly to improve the product and get it ready for 2019. I am very excited to announce the following list of features that should come online early next year: 1. Cable system operation status allows users to see which segments are up/down/partial and their last outage, along with textual details of previous outages with potential for links 2. Cable system information - length, activation date, and estimated end-of-life 3. Fast page load time of <5 secs for users within the US 4. 3D data center locations 5. “Buy capacity” - a form that generates an email to a specified cable owner 6. Report-an-issue on routes for users to send feedback 7. Ability for users to receive email notifications about cable status changes ,Option to show subsea cables only , Option to show active cables only, Option to show future cables only 8. A Time Machine function that will show cables that will be active in the future 9. Ability to add custom fields in select or all cables to show information such as latency3-tiered Network Atlas Cable 10. Management UI: Users can:Add/Delete/Replace I can’t wait to share this next phase of Network Atlas with you all. Once it’s complete, it will truly be “one map to rule them all.” Next up, let me address the elephant in the room. As many of you know, Network Atlas’ Kickstarter for $100K for 2019 funding came up short of meeting its goal(we cancelled it before the time because many of you reached out wanting to support directly not via Kickstart). However, it was an excellent learning experience, as it provided a chance to interact with potential donors and hear their questions. One of those questions was if Network Atlas could show its 3-year plan for the project. In the interest of transparency, I would like to share with you Network Atlas’ proposed 3-year operating budget as of today. You can see this as details in our blog - https://www.networkatlas.org/blog/eoy2018 Month of December, we will freeze adding new fiber routes to Network Atlas, this will allow us to focus on working the 10 feature we have explained above. If you want to upload fiber routes you own and authorized, feel free to go to https://kmzs.networkatlas.org <https://kmzs.networkatlas.org> and upload them and please include your email address in the file name (or create a colder with readme in it) so we can reach back with questions. Our self-service portal will solve this issue in January :) Now this is not the end. It is not even the beginning of the end. But it is, perhaps, the end of the beginning. Have a wonderful December, and a happy new year! Mehmet

3 5

Re: Stupid Question maybe?
by Scott Weeks 19 Dec '18

19 Dec '18

--- nanog(a)nanog.org wrote: From: Grant Taylor via NANOG <nanog(a)nanog.org> You can safely say that 72.234.7.0/24 is a Class C /sized/ network. -------------------------------------- But most don't say that. They just say it's a Class C, which it most assuredly is not. I heckle them until they can give the correct answer: leading bits are 110 or it's not a Class C subnet. scott

4 4

RE: rfd
by Scott Weeks 18 Dec '18

18 Dec '18

--- SNaslund(a)medline.com wrote: From: "Naslund, Steve" <SNaslund(a)medline.com> Mainly because propagating a flapping route across the entire Internet is damaging... ------------------------------------------------ https://www.researchgate.net/publication/220850232_Route_Flap_Damping_Made_… scott

2 1

Re: Stupid Question maybe?
by Scott Weeks 18 Dec '18

18 Dec '18

--- beecher(a)beecher.cc wrote: From: Tom Beecher <beecher(a)beecher.cc> It's good to have at least a passing understanding of the old terminology simply because documentation for newer stuff likes to reference it... -------------------------------------- Plus it's fun (and informative about a netgeek's skill) when they call, say, 72.234.7.0/24 a Class C and you can say no it's not. Then you see if they can say why. If they can't, well...ummm... I really mess with them after that. It helps pass the work day. >;-) https://en.wikipedia.org/wiki/Classful_network#Classful_addressing_definiti… scott ps. Be sure to send Wikipedia a small Christmas gift. It's invaluable.

2 1

Twitter (AS13414) Peering Contact
by Ryan Gard 17 Dec '18

17 Dec '18

Afternoon, If there's anybody on the list from Twitter AS13414, if they could contact me off list? Further, if you have contact info outside of the standard peering email, that would be fantastic. We've made a few attempts over the last year give or take to reach out, and unfortunately we've seen nothing but silence in response. Thanks! -- Ryan Gard

2 1

Hostwinds LLC. (AS54290) Contact
by Cummings, Chris 17 Dec '18

17 Dec '18

Good Morning, If anyone from Hostwinds LLC, AS54290 is on the list, can you please contact me at ccummings(a)coeur.com<mailto:ccummings@coeur.com>? Also, if anyone would like to send me contact info if you have it, it would be greatly appreciated. Thanks! Chris Cummings

1 0

How to choose a transit provider?
by Mehmet Akcin 15 Dec '18

15 Dec '18

Hello there, I have started writing a blog which I hope it would help buy transit services from providers by doing various due diligences(technical) i wanted to reach out and ask nanog community’s thoughts on this. What are some of your checklist items ? Price? Their directly peered networks? If they are tier 2,3 who they use as tier 1-2? Are the onnet? I am sure list goes on and on on... Thanks a lot for your help. I plan to write the blog this month and publish. Mehmet -- Mehmet +1-424-298-1903

9 13