- NANOG - lists.nanog.org

Hosteurope / GoDaddy contact
by Umut Alemdar 07 Jun '24

07 Jun '24

Hi, We are dealing with unannounced SOA record changes from Hosteurope to our domain. Is there anyone from Hosteurope / GoDaddy who we could reach out to quickly resolve this matter? Thanks, Umut

1 0

Get ready for N91: Learn more about Monday's Keynote + More
by Nanog News 06 Jun '24

06 Jun '24

*Get Ready for N91: Q + A with Keynote Corey Quinn* *“Snarky” Chief Cloud Economist Discusses Upcoming Talk + Why Humor is the Key to a Good Keynote* Chief Cloud Economist at The Duckbill Group, Corey Quinn, will kick off the NANOG 91 programming on Monday! Attendees may be familiar with Corey from his sarcastic, thoughtful, and humorous commentary on helping companies improve their Amazon Web Services (AWS). *READ NOW * <https://nanog.org/stories/articles/get-ready-for-nanog-91-qa-w-keynote-core…> *Still Time to Register for NANOG 91!* *Can't Make it to Kansas City? Join us Virtually! * NANOG 91 will kick off Monday! Can't make it in-person? Join us virtually + stream live presentations while engaging in real-time speaker Q+A plus live chat with other attendees. *REGISTER NOW * <https://nanog.org/events/nanog-91/> *Take Advantage of NANOG 91 Socials! * *Have you Synced the NANOG 91 Socials to your Calendar?* Get to know your peers in the industry + foster important relationships in a relaxed, casual environment. * <https://nanog.org/events/nanog-91/socials/>* *GET SOCIAL <https://nanog.org/events/nanog-91/socials/>* *Kansas City — Things to Do + See While Attending NANOG 91 * When not absorbing the latest trends in technology or networking with tech leaders — why not explore this jazzy city, where the roots (and fountains) run deep? We've done the work. Check out NANOG's hit list, and then curate your own. <https://nanog.org/stories/articles/things-to-do-see-in-kansas-city/> *VIEW NOW <https://nanog.org/stories/articles/things-to-do-see-in-kansas-city/>*

1 0

Any Zayo clue on the list?
by Mike Lyon 06 Jun '24

06 Jun '24

Have a zayo packet loss issue and your NOC doesn't see anything wrong... Host Loss% Snt Last Avg Best Wrst StDev 1. ae15.cs4.sjc4.us.zip.zayo.com 94.3% 142 28.7 28.9 28.0 30.6 0.8 2. ae8.cs2.sea1.us.zip.zayo.com 27.5% 142 30.8 30.5 27.5 41.6 3.9 Any help would be appreciated. Please ping me off list. Thank You, Mike -- Mike Lyon mike.lyon(a)gmail.com http://www.linkedin.com/in/mlyon

2 1

West Coast Peering / Packet Loss issues between AS7018 (AT&T) and AS6461
by Alex Buie 05 Jun '24

05 Jun '24

Since roughly 6:30AM local time on Tuesday we have been seeing significantly increased packet loss (20-40%) and latency increase of ~30-40ms from customers on the west coast hosted out of AS7018 (AT&T/sbcglobal) towards our addresses announced through Zayo (AS6461). Has anyone else noticed or seen this? We're working through our channels with the carrier but the latency profile is such that it seems likely it may be affecting others as well and I wanted to ask the group. Any incidents that anyone is aware of which may be related? Thanks, *Alex Buie*Senior Cloud Operations Engineer 450 Century Pkwy # 100 Allen, TX 75013 <https://maps.google.com/?q=450+Century+Pkwy+STE+100+%7C+Allen,+TX+%7C+75013…> D: 469-884-0225 | www.cytracom.com

2 1

Re: West Coast Peering / Packet Loss issues between AS7018 (AT&T) and AS6461
by howard stearn 05 Jun '24

05 Jun '24

To those interested , This is an ongoing issue for my users . AT&T and Zayo have not responded to my requests . AS7018 12.122.114.5 AS6461 64.125.12.117 >From June 4 , 2024 , Packet loss continues and has been going on between AT&T and Zayo/ABOVENET all day . According to DNS packet loss appears to be on a lag in SJC7 . ( Evocative San Jose Data Center ? ) According to all traceroutes the IPs on each side of the packet loss are AT&T 12.122.114.5 and ZAYO 64.125.12.117 . When the traceroute confirms the IPs above are in the path ; packet loss to or from any endpoint is greater than 15% . So far I tried reaching out to technical support with both providers via public and standard channels . I’m asking for help passing this information along to AT&T or Zayo hoping the community can provide some assistance to deliver this message because their technical support can not . Please forward this information along if you really do know the right person to ask don’t just spam them with messages . Don’t assume someone else will look at this and forward it to the correct person .

1 0

Looking for contact at Microsoft optical networking
by Scott Campbell 05 Jun '24

05 Jun '24

We are looking for a contact within the optical group at Microsoft networking to discuss a fiber outage event in the Chicago area during third party physical maintenance that resulted in accidental information disclosure between our organizations on or around 22 March, 2024. Our intent is to better understand exactly what happened and what can be done to mitigate potential fallout in the event that this happens again. Many thanks, Scott Campbell ESnet Security Tech Lead

1 0

600,000 routers bricked
by Dave Taht 04 Jun '24

04 Jun '24

https://www.linkedin.com/pulse/600000-families-using-one-internet-provider-… -- https://www.youtube.com/watch?v=BVFWSyMp3xg&t=1098s Waves Podcast Dave Täht CSO, LibreQos

10 11

Free(opensource) Ticketing solutions
by Pascal Masha 03 Jun '24

03 Jun '24

Hello, Which free and good ticketing systems do you folks(for those who do) use? Regards, Paschal Masha

15 15

Anyone from AS137409 lurking?
by Bryan Holloway 03 Jun '24

03 Jun '24

Looking for a peering contact for Global Secure Layer aka GSL Networks. Trying to resolve a long-standing peering issue, and e-mails to published contacts have gone unanswered. Thanks! - bryan

1 0

comcast v4 in pnw
by Randy Bush 02 Jun '24

02 Jun '24

a bunch of us comcast soho folk, and monitoring gear, are seeing v4 breakage in orygon and maybe washington but only for seattle destinations. v6 works. johnb, is comcast going v6-only? :) ryuu.rg.net:/Users/randy> ping r0.iad PING r0.iad.rg.net (198.180.150.120): 56 data bytes 64 bytes from 198.180.150.120: icmp_seq=0 ttl=54 time=83.186 ms 64 bytes from 198.180.150.120: icmp_seq=1 ttl=54 time=81.450 ms ^C --- r0.iad.rg.net ping statistics --- 2 packets transmitted, 2 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 81.450/82.318/83.186/0.868 ms ryuu.rg.net:/Users/randy> ping r0.sea PING r0.sea.rg.net (147.28.0.4): 56 data bytes Request timeout for icmp_seq 0 ^C --- r0.sea.rg.net ping statistics --- 2 packets transmitted, 0 packets received, 100.0% packet loss ryuu.rg.net:/Users/randy> ping6 r0.sea PING6(56=40+8+8 bytes) 2601:1c0:5600:9f4d:b500:3942:c8bd:ff16 --> 2001:418:1::4 16 bytes from 2001:418:1::4, icmp_seq=0 hlim=55 time=21.339 ms 16 bytes from 2001:418:1::4, icmp_seq=1 hlim=55 time=17.544 ms ^C --- r0.sea.rg.net ping6 statistics --- my guess is that it is up in seattle. but portland folk always blame seattle :) ryuu.rg.net:/Users/randy> traceroute r1.sea traceroute to r1.sea.rg.net (147.28.0.5), 64 hops max, 40 byte packets 1 192.168.0.1 (192.168.0.1) 5.382 ms 2.555 ms 1.978 ms 2 100.93.174.2 (100.93.174.2) 14.301 ms 100.93.174.3 (100.93.174.3) 16.307 ms 100.93.174.2 (100.93.174.2) 15.785 ms 3 po-332-364-rur202.beaverton.or.bverton.comcast.net (96.108.64.189) 19.839 ms po-332-363-rur201.beaverton.or.bverton.comcast.net (96.108.64.181) 11.312 ms po-332-364-rur202.beaverton.or.bverton.comcast.net (96.108.64.189) 17.453 ms 4 po-2-rur202.beaverton.or.bverton.comcast.net (24.124.129.106) 14.082 ms po-200-xar02.beaverton.or.bverton.comcast.net (96.216.60.165) 13.606 ms po-2-rur202.beaverton.or.bverton.comcast.net (24.124.129.106) 17.979 ms 5 ae-69-ar01.troutdale.or.bverton.comcast.net (68.85.243.197) 20.961 ms po-200-xar02.beaverton.or.bverton.comcast.net (96.216.60.165) 15.522 ms * 6 ae-69-ar01.troutdale.or.bverton.comcast.net (68.85.243.197) 12.324 ms * * 7 be-2312-pe12.seattle.wa.ibone.comcast.net (96.110.34.138) 20.785 ms be-36211-cs01.seattle.wa.ibone.comcast.net (68.86.93.49) 18.071 ms be-2212-pe12.seattle.wa.ibone.comcast.net (96.110.34.134) 15.331 ms 8 be-2212-pe12.seattle.wa.ibone.comcast.net (96.110.34.134) 26.953 ms * be-2412-pe12.seattle.wa.ibone.comcast.net (96.110.34.142) 19.355 ms 9 * * * 10 * * * ^C randy

2 2