January 2025 - NANOG - lists.nanog.org

400G link L2 flakiness over DWDM
by Oliver Garraux 13 Jan '25

13 Jan '25

We have a number of new 400G provider waves with odd flakiness that we can't seem to sort out. These links appear good - light levels are fine, links will be up with working LLDP. But if we admin down / up the link on the IP side, many of them won't come back up on their own. Our provider sees "loss of alignment" alarms on the optical equipment, and we can eventually get the links back up if they bounce them a few times on the DWDM side. We're using Juniper PTX's, with Juniper 400G FR4 and 400G LR4 optics. Same issue on different circuits/devices/paths with this provider, but no issues with other transport providers using the same optics on our end. Believe our provider is using Ciena optical equipment. Has anyone seen issues like this before? Our provider has been looking into this for months without much progress. One tantalizing clue was another customer using Cisco Nexus had better results after they enabled "link transmit reset-skip" (https://quickview.cloudapps.cisco.com/quickview/bug/CSCvi45168) Not clear exactly what that option does, and there doesn't seem to be an obviously equivalent config knob in Junos. Thanks, Oliver

5 8

Level3 4.2.2.1 and 4.2.2.2 not responding to pings, DNS queries work
by Mel Beckman 13 Jan '25

13 Jan '25

I noticed that Level3 open DNS 4.2.2.1 and 4.2.2.2 stopped responding to ping today. They are responding to DNS queries however. Does anyone know if this filtering is going to be permanent? -mel beckman

6 7

Re: Level3 4.2.2.1 and 4.2.2.2 not responding to pings, DNS queries work
by nanog＠fleish.org 13 Jan '25

13 Jan '25

I’m seeing some of the resolver IPs being filtering from various locations while responding from others, no doubt due to their use of anycast. I rarely ping test 4.2.2.2 anymore, having switched to 8.8.8.8 some time ago which I have a window up running 24x7 as a quick way to detect if my laptop is having connectivity issues from wherever it currently resides. It’s usually reliable, but I understand such traffic is the first to get filtered/dropped when needed so it’s just an initial indicator for me from which further testing can be performed when needed. I will also mention it’s possible to detect which NS server/pool/location you are reaching on Level3’s network via the below dig query. This has been an invaluable tool over the years as IME they tend to break DNS sub-delegation at least once or twice a year and the more data you can provide to them about where the breakage is the faster you can get them to engage the DNS team to actually fix it vs. arguing with you that it’s not broken because it "works for them” (facepalm). And at least once I found they broke resolution on their authoritative name servers (ns1.l3.net <http://ns1.l3.net/> or ns2.l3.net <http://ns2.l3.net/>) and again they first told me it wasn’t a problem because DNS again the broken one(s) would timeout and then get the answer from another, working server (double-facepalm). dig +short @4.2.2.2 hostname.bind CH TXT I’ve also been provided this query to derive the same for Cloudflare’s NS servers: dig CHAOS TXT id.server @1.1.1.1 +nsid And the following for Cleanbrowsing NS servers (these power content filtering on Unifi networks): nslookup -type=txt iptest.whois.dnscontest.cleanbrowsing.org <http://iptest.whois.dnscontest.cleanbrowsing.org/> Below are the results I got for Level3 from various locations (pardon the wall of text). It looks like they’re making some changes to serve DNS queries off their NTP servers From Level3 WDC1/McLean: PING 4.2.2.1 (4.2.2.1) 56(84) bytes of data. --- 4.2.2.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.987/0.987/0.987/0.000 ms "pubntp1.wdc12" PING 4.2.2.2 (4.2.2.2) 56(84) bytes of data. --- 4.2.2.2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.926/0.926/0.926/0.000 ms "cns4.sjo1" PING 4.2.2.3 (4.2.2.3) 56(84) bytes of data. --- 4.2.2.3 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.799/0.799/0.799/0.000 ms "pubntp1.wdc12" PING 4.2.2.4 (4.2.2.4) 56(84) bytes of data. --- 4.2.2.4 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.855/0.855/0.855/0.000 ms "pubntp2.wdc12" PING 4.2.2.5 (4.2.2.5) 56(84) bytes of data. --- 4.2.2.5 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.897/0.897/0.897/0.000 ms "cns4.sjo1" PING 4.2.2.6 (4.2.2.6) 56(84) bytes of data. --- 4.2.2.6 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.973/0.973/0.973/0.000 ms "pubntp1.wdc12” From Level3 SFO1/Sunnyvale: PING 4.2.2.1 (4.2.2.1) 56(84) bytes of data. --- 4.2.2.1 ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 999ms "cns3.sjo1" PING 4.2.2.2 (4.2.2.2) 56(84) bytes of data. --- 4.2.2.2 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms "cns2.sjo1" PING 4.2.2.3 (4.2.2.3) 56(84) bytes of data. --- 4.2.2.3 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms "cns1.sjo1" PING 4.2.2.4 (4.2.2.4) 56(84) bytes of data. --- 4.2.2.4 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms "cns2.sjo1" PING 4.2.2.5 (4.2.2.5) 56(84) bytes of data. --- 4.2.2.5 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.275/0.275/0.275/0.000 ms "cns3.sjo1" PING 4.2.2.6 (4.2.2.6) 56(84) bytes of data. --- 4.2.2.6 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms "cns3.sjo1” From Comcast Atlanta: PING 4.2.2.1 (4.2.2.1) 56(84) bytes of data. --- 4.2.2.1 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms "cns2.atl2" PING 4.2.2.2 (4.2.2.2) 56(84) bytes of data. --- 4.2.2.2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 13.442/13.442/13.442/0.000 ms "cns4.atl2" PING 4.2.2.3 (4.2.2.3) 56(84) bytes of data. --- 4.2.2.3 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 13.431/13.431/13.431/0.000 ms "cns2.atl2" PING 4.2.2.4 (4.2.2.4) 56(84) bytes of data. --- 4.2.2.4 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 13.632/13.632/13.632/0.000 ms "cns2.atl2" PING 4.2.2.5 (4.2.2.5) 56(84) bytes of data. --- 4.2.2.5 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 12.656/12.656/12.656/0.000 ms "cns3.atl2" PING 4.2.2.6 (4.2.2.6) 56(84) bytes of data. --- 4.2.2.6 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 12.041/12.041/12.041/0.000 ms "cns4.atl2” From AT&T Atlanta: PING 4.2.2.1 (4.2.2.1) 56(84) bytes of data. --- 4.2.2.1 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms "cns2.atl2" PING 4.2.2.2 (4.2.2.2) 56(84) bytes of data. --- 4.2.2.2 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms "pubntp1.atl2" PING 4.2.2.3 (4.2.2.3) 56(84) bytes of data. --- 4.2.2.3 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms "cns3.atl2" PING 4.2.2.4 (4.2.2.4) 56(84) bytes of data. --- 4.2.2.4 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 15.430/15.430/15.430/0.000 ms "pubntp1.atl2" PING 4.2.2.5 (4.2.2.5) 56(84) bytes of data. --- 4.2.2.5 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms "cns3.atl2" PING 4.2.2.6 (4.2.2.6) 56(84) bytes of data. --- 4.2.2.6 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 16.103/16.103/16.103/0.000 ms "cns4.atl2” From AT&T SF Bay Area Peninsula: PING 4.2.2.1 (4.2.2.1) 56(84) bytes of data. --- 4.2.2.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 7.880/7.880/7.880/0.000 ms "cns3.sjo1" PING 4.2.2.2 (4.2.2.2) 56(84) bytes of data. --- 4.2.2.2 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms "cns2.sjo1" PING 4.2.2.3 (4.2.2.3) 56(84) bytes of data. --- 4.2.2.3 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 6.888/6.888/6.888/0.000 ms "cns3.sjo1" PING 4.2.2.4 (4.2.2.4) 56(84) bytes of data. --- 4.2.2.4 ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1000ms "cns4.sjo1" PING 4.2.2.5 (4.2.2.5) 56(84) bytes of data. --- 4.2.2.5 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 7.173/7.173/7.173/0.000 ms "cns1.sjo1" PING 4.2.2.6 (4.2.2.6) 56(84) bytes of data. --- 4.2.2.6 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms "cns2.sjo1” From DRFortress Honolulu: PING 4.2.2.1 (4.2.2.1) 56(84) bytes of data. --- 4.2.2.1 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms "cns3.sjo1" PING 4.2.2.2 (4.2.2.2) 56(84) bytes of data. --- 4.2.2.2 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms "cns3.sjo1" PING 4.2.2.3 (4.2.2.3) 56(84) bytes of data. --- 4.2.2.3 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 54.233/54.233/54.233/0.000 ms "cns3.sjo1" PING 4.2.2.4 (4.2.2.4) 56(84) bytes of data. --- 4.2.2.4 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms "cns3.sjo1" PING 4.2.2.5 (4.2.2.5) 56(84) bytes of data. --- 4.2.2.5 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 54.195/54.195/54.195/0.000 ms "cns3.sjo1" PING 4.2.2.6 (4.2.2.6) 56(84) bytes of data. --- 4.2.2.6 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms "cns4.sjo1” From Hawaiian Telecom Honolulu (oddly from here I get no response to the hostname.bind dig queries): PING 4.2.2.1 (4.2.2.1) 56(84) bytes of data. --- 4.2.2.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 54.727/54.727/54.727/0.000 ms PING 4.2.2.2 (4.2.2.2) 56(84) bytes of data. --- 4.2.2.2 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms PING 4.2.2.3 (4.2.2.3) 56(84) bytes of data. --- 4.2.2.3 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms PING 4.2.2.4 (4.2.2.4) 56(84) bytes of data. --- 4.2.2.4 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms PING 4.2.2.5 (4.2.2.5) 56(84) bytes of data. --- 4.2.2.5 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 56.765/56.765/56.765/0.000 ms PING 4.2.2.6 (4.2.2.6) 56(84) bytes of data. --- 4.2.2.6 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms From Unitas Seacacus: PING 4.2.2.1 (4.2.2.1) 56(84) bytes of data. --- 4.2.2.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 2.062/2.062/2.062/0.000 ms "cns2.nyc6" PING 4.2.2.2 (4.2.2.2) 56(84) bytes of data. --- 4.2.2.2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 2.012/2.012/2.012/0.000 ms "cns2.nyc6" PING 4.2.2.3 (4.2.2.3) 56(84) bytes of data. --- 4.2.2.3 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.651/1.651/1.651/0.000 ms "cns3.nyc6" PING 4.2.2.4 (4.2.2.4) 56(84) bytes of data. --- 4.2.2.4 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 2.055/2.055/2.055/0.000 ms "cns2.nyc6" PING 4.2.2.5 (4.2.2.5) 56(84) bytes of data. --- 4.2.2.5 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 2.102/2.102/2.102/0.000 ms "cns3.nyc6" PING 4.2.2.6 (4.2.2.6) 56(84) bytes of data. --- 4.2.2.6 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.626/1.626/1.626/0.000 ms "cns3.nyc6” From Verizon FIOS New York (oddly from here I get no response to the hostname.bind dig queries): PING 4.2.2.1 (4.2.2.1) 56(84) bytes of data. --- 4.2.2.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 4.355/4.355/4.355/0.000 ms PING 4.2.2.2 (4.2.2.2) 56(84) bytes of data. --- 4.2.2.2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 3.764/3.764/3.764/0.000 ms PING 4.2.2.3 (4.2.2.3) 56(84) bytes of data. --- 4.2.2.3 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 4.053/4.053/4.053/0.000 ms PING 4.2.2.4 (4.2.2.4) 56(84) bytes of data. --- 4.2.2.4 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 3.394/3.394/3.394/0.000 ms PING 4.2.2.5 (4.2.2.5) 56(84) bytes of data. --- 4.2.2.5 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 3.442/3.442/3.442/0.000 ms PING 4.2.2.6 (4.2.2.6) 56(84) bytes of data. --- 4.2.2.6 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 4.944/4.944/4.944/0.000 ms From Allied Telecom in Washington DC: PING 4.2.2.1 (4.2.2.1) 56(84) bytes of data. --- 4.2.2.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.683/1.683/1.683/0.000 ms "pubntp1.wdc12" PING 4.2.2.2 (4.2.2.2) 56(84) bytes of data. --- 4.2.2.2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.592/1.592/1.592/0.000 ms "pubntp2.wdc12" PING 4.2.2.3 (4.2.2.3) 56(84) bytes of data. --- 4.2.2.3 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.776/1.776/1.776/0.000 ms "cns1.wdc12" PING 4.2.2.4 (4.2.2.4) 56(84) bytes of data. --- 4.2.2.4 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.810/1.810/1.810/0.000 ms "pubntp2.wdc12" PING 4.2.2.5 (4.2.2.5) 56(84) bytes of data. --- 4.2.2.5 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.729/1.729/1.729/0.000 ms "cns1.wdc12" PING 4.2.2.6 (4.2.2.6) 56(84) bytes of data. --- 4.2.2.6 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.432/1.432/1.432/0.000 ms "cns4.sjo1” -T > On Jan 13, 2025, at 07:00, nanog-request(a)nanog.org wrote: > > Message: 6 > Date: Mon, 13 Jan 2025 04:24:50 +0000 > From: Mel Beckman <mel(a)beckman.org <mailto:mel@beckman.org>> > To: Daniel Sterling <sterling.daniel(a)gmail.com <mailto:sterling.daniel@gmail.com>> > Cc: Jerry Cloe <jerry(a)jtcloe.net <mailto:jerry@jtcloe.net>>, "nanog(a)nanog.org <mailto:nanog@nanog.org>" <nanog(a)nanog.org <mailto:nanog@nanog.org>> > Subject: Re: Level3 4.2.2.1 and 4.2.2.2 not responding to pings, DNS > queries work > Message-ID: <1E72A509-881F-453A-B5D4-7AF8FDB44C4E(a)beckman.org <mailto:1E72A509-881F-453A-B5D4-7AF8FDB44C4E@beckman.org>> > Content-Type: text/plain; charset="utf-8" > > Dan, > > Thanks! I had never read that before. But that makes sense. > > -mel > > On Jan 12, 2025, at 8:22?PM, Daniel Sterling <sterling.daniel(a)gmail.com <mailto:sterling.daniel@gmail.com>> wrote: > > ? > Seems like these IPs not responding to ping is not unusual, as per https://www.reddit.com/r/sysadmin/comments/11syv2e/google_dns_8888_dropping… > > "Google has stated multiple times before as has Level3/CenturyLink/Lumen that 4.2.2.1 and 8.8.8.8 should not be used for ping checks and they will drop packets when under load or if they notice too much activity from a single IP" > > -- Dan > > On Sun, Jan 12, 2025 at 11:03?PM Mel Beckman <mel(a)beckman.org <mailto:mel@beckman.org><mailto:mel@beckman.org>> wrote: > Still not pinging from Frontier, Lumen, AT&T, or Verizon networks > > > -mel > > On Jan 12, 2025, at 4:13?PM, Jerry Cloe <jerry(a)jtcloe.net <mailto:jerry@jtcloe.net><mailto:jerry@jtcloe.net>> wrote: > > ? > O:\>ping 4.2.2.1 > > Pinging 4.2.2.1 with 32 bytes of data: > Reply from 4.2.2.1<http://4.2.2.1 <http://4.2.2.1/>>: bytes=32 time=36ms TTL=56 > Reply from 4.2.2.1<http://4.2.2.1 <http://4.2.2.1/>>: bytes=32 time=44ms TTL=56 > Reply from 4.2.2.1<http://4.2.2.1 <http://4.2.2.1/>>: bytes=32 time=36ms TTL=56 > Reply from 4.2.2.1<http://4.2.2.1 <http://4.2.2.1/>>: bytes=32 time=38ms TTL=56 > > Ping statistics for 4.2.2.1<http://4.2.2.1 <http://4.2.2.1/>>: > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > Approximate round trip times in milli-seconds: > Minimum = 36ms, Maximum = 44ms, Average = 38ms > > Same for 4.2.2.2 > > > > -----Original message----- > From: Mel Beckman <mel(a)beckman.org <mailto:mel@beckman.org><mailto:mel@beckman.org>> > Sent: Sun 01-12-2025 06:07 pm > Subject: Level3 4.2.2.1 and 4.2.2.2 not responding to pings, DNS queries work > To: nanog(a)nanog.org <mailto:nanog@nanog.org><mailto:nanog@nanog.org>; > I noticed that Level3 open DNS 4.2.2.1 and 4.2.2.2 stopped responding to ping today. They are responding to DNS queries however. > > Does anyone know if this filtering is going to be permanent? > > -mel beckman >

4 4

Apply Today for the ARIN 55 Fellowship Program
by John Sweeting 13 Jan '25

13 Jan '25

Hello NANOG, Please see the announcement below referencing ARIN's Fellowship Program. Thanks, John S. ________________________________ From: ARIN-announce <arin-announce-bounces(a)arin.net<mailto:arin-announce-bounces@arin.net>> on behalf of ARIN <info(a)arin.net<mailto:info@arin.net>> Sent: Thursday, January 9, 2025 10:56 AM To: arin-announce(a)arin.net<mailto:arin-announce@arin.net> <arin-announce(a)arin.net<mailto:arin-announce@arin.net>> Subject: [arin-announce] Apply Today for the ARIN 55 Fellowship Program Learn more about Internet governance, number resource policy, and the ARIN community by becoming an ARIN Fellow. Applications for the ARIN 55 Fellowship Program are now open, and we encourage you to apply for this specialized, interactive learning opportunity. APPLY NOW: https://arin.net/beafellow Applications are now being accepted through 27 January 2025.  Fellows will attend virtual sessions before and after the ARIN 55 Public Policy and Members Meeting on 27-30 April 2025 in Charlotte, North Carolina, and may attend ARIN 55 either in person or virtually at the discretion of the Fellowship Selection Committee. With the personal support of ARIN community member Mentors, Fellows will have the opportunity to ask questions, get feedback, and gain the knowledge and confidence to join in community discussions, propose new ideas, and become part of the future of Internet governance and policy in the ARIN region.  Individuals who are 18 years of age or older and reside in the ARIN region are eligible to apply if they have a demonstrated interest in the ARIN community and its Policy Development Process for the management of Internet number resources.   Applicants should understand the importance of ARIN’s mission and be familiar with ARIN services, the Internet number resources it manages, and the processes reflected in the Number Resource Policy Manual (NRPM).   To learn more about ARIN’s Fellowship Program, the selection process, and the Terms and Conditions, please visit: https://www.arin.net/fellowship. Applicants can email fellowships(a)arin.net<mailto:fellowships@arin.net> for more information or to request a customizable letter to their employer that highlights the benefits of taking part in ARIN’s Fellowship Program.  ARIN looks forward to receiving your application soon!  Regards,  Amanda Gauldin Project Manager American Registry for Internet Numbers (ARIN)

1 1

Comcast looking glass router
by razor＠meganet.net 13 Jan '25

13 Jan '25

Hi, hoping someone here from Comcast can help me. I need to be able to login Comcast Looking Glass router in NY to check on some route advertising but the username and password that was previously working for the LG no longer seems to work. Host: route-server.newyork.ny.ibone.comcast.net Username: rviewsxr Password: rviews and I also tried rviewsxr If anyone knows the current login info I would appreciate it. P

4 6

Google Geo IP contact
by Lou Devictoria 13 Jan '25

13 Jan '25

Hi Nanog Is there anyone from Google who can help me correcting GeoIP information for my sites . Please contact me

2 1

BFD vs network brownouts
by David Zimmerman 12 Jan '25

12 Jan '25

Hi, all. BFD is well known for what it brings to the table for improving link failure detection; however, even at a reasonably athletic 300ms Control rate, you're not going to catch a significant percentage of brownout situations where you have packet loss but not a full outage. I'm trying to: 1. find any formal or semi-formal writing about quantification of BFD's effectiveness. For example, my mental picture is a 3D graph where, for a given Control rate and corresponding Detection Time, the X axis is percentage of packet loss, the Y axis is the Control/Detection timer tuple, and the Z axis is the likelihood that BFD will fully engage (i.e., missing all three Control packets). Beyond what I believe is a visualization complexity needing some single malt scotch nearby, letting even a single Control packet through resets your Detection timer. 2. ask if folks in the Real World use BFD towards this end, or have other mechanisms as a data plane loss instrumentation vehicle. For example, in my wanderings, I've found an environment that offloads the diagnostic load to adjacent compute nodes, but they reach out to orchestration to trigger further router actions in a full-circle cycle measured in minutes. Short of that, really aggressive timers (solving through brute force) on BFD quickly hit platform limits for scale unless perhaps you can offboard the BFD to something inline (e.g. the Ciena 5170 can be dialed down to a 3.3ms Control timer). Any thoughts appreciated. I'm also pursuing ways of having my internal "customer" signal me upon their own packet loss observation (e.g. 1% loss for most folks is a TCP retransmission, but 1% loss for them are crying eyeballs and an escalation). -dp

6 10

ZANOG25: Call for Papers
by Amreesh Phokeer 11 Jan '25

11 Jan '25

Hello all. The ZANOG25 Programme Committee is now seeking contributions for presentations for the ZANOG 2025 Conference, which will be held on 23-24 April 2025 in Durban, South Africa. Details about the Call for Papers, how you can submit a proposal for the conference, and the submission deadlines, can be found at the link below: https://events.nog.net.za/event/58/abstracts/ We look forward to receiving your papers and seeing you in Durban. Many thanks! ZANOG25 Programme Committee -- Amreesh Phokeer

1 0

Weekly Global IPv4 Routing Table Report
by Routing Table Analysis Role Account 10 Jan '25

10 Jan '25

This is an automated weekly mailing describing the state of the Global IPv4 Routing Table as seen from APNIC's router in Japan. The posting is sent to APOPS, NANOG, AfNOG, SANOG, PacNOG, SAFNOG UKNOF, TZNOG, MENOG, BJNOG, SDNOG, CMNOG, LACNOG and the RIPE Routing WG. Daily listings are sent to bgp-stats(a)lists.apnic.net. For historical data, please see https://thyme.apnic.net. If you have any comments please contact Philip Smith <pfsinoz(a)gmail.com>. IPv4 Routing Table Report 04:00 +10GMT Sat 11 Jan, 2025 IPv4 BGP Table (Global) as seen at Japan. Report Website: https://thyme.apnic.net Detailed Analysis: https://thyme.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 972945 Prefixes after maximum aggregation (per Origin AS): 370667 Deaggregation factor: 2.62 Unique aggregates announced (without unneeded subnets): 470115 Number of IPv4 prefixes with a valid ROA: 519009 Number of IPv4 prefixes with an invalid ROA: 1404 Number of IPv4 prefixes with no ROA: 452532 Total ASes present in the Internet Routing Table: 76550 Prefixes per ASN: 12.71 Origin-only ASes present in the Internet Routing Table: 65493 Origin ASes announcing only one prefix: 26848 Transit ASes present in the Internet Routing Table: 11057 Transit-only ASes present in the Internet Routing Table: 534 Average AS path length visible in the Internet Routing Table: 5.2 Max AS path length visible: 65 Max AS path prepend of ASN ( 37447) 57 Prefixes from unregistered ASNs in the Routing Table: 1083 Number of instances of unregistered ASNs: 1088 Number of 32-bit ASNs allocated by the RIRs: 46011 Number of 32-bit ASNs visible in the Routing Table: 37650 Prefixes from 32-bit ASNs in the Routing Table: 197395 Number of bogon 32-bit ASNs visible in the Routing Table: 34 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 514 Number of addresses announced to Internet: 3121197056 Equivalent to 186 /8s, 9 /16s and 176 /24s Percentage of available address space announced: 84.3 Percentage of allocated address space announced: 84.3 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 99.6 Total number of prefixes smaller than registry allocations: 318260 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 256742 Total APNIC prefixes after maximum aggregation: 76766 APNIC Deaggregation factor: 3.34 Prefixes being announced from the APNIC address blocks: 248462 Unique aggregates announced from the APNIC address blocks: 102609 APNIC Region origin ASes present in the Internet Routing Table: 14494 APNIC Prefixes per ASN: 17.14 APNIC Region origin ASes announcing only one prefix: 4435 APNIC Region transit ASes present in the Internet Routing Table: 1935 Average APNIC Region AS path length visible: 5.4 Max APNIC Region AS path length visible: 48 Number of APNIC region 32-bit ASNs visible in the Routing Table: 9962 Number of APNIC addresses announced to Internet: 757840768 Equivalent to 45 /8s, 43 /16s and 187 /24s APNIC AS Blocks 4608-4864, 7467-7722, 9216-10239, 17408-18431 (pre-ERX allocations) 23552-24575, 37888-38911, 45056-46079, 55296-56319, 58368-59391, 63488-64098, 64297-64395, 131072-153913 APNIC Address Blocks 1/8, 14/8, 27/8, 36/8, 39/8, 42/8, 43/8, 49/8, 58/8, 59/8, 60/8, 61/8, 101/8, 103/8, 106/8, 110/8, 111/8, 112/8, 113/8, 114/8, 115/8, 116/8, 117/8, 118/8, 119/8, 120/8, 121/8, 122/8, 123/8, 124/8, 125/8, 126/8, 133/8, 150/8, 153/8, 163/8, 171/8, 175/8, 180/8, 182/8, 183/8, 202/8, 203/8, 210/8, 211/8, 218/8, 219/8, 220/8, 221/8, 222/8, 223/8, ARIN Region Analysis Summary ---------------------------- Prefixes being announced by ARIN Region ASes: 286520 Total ARIN prefixes after maximum aggregation: 126612 ARIN Deaggregation factor: 2.26 Prefixes being announced from the ARIN address blocks: 288393 Unique aggregates announced from the ARIN address blocks: 132570 ARIN Region origin ASes present in the Internet Routing Table: 19209 ARIN Prefixes per ASN: 15.01 ARIN Region origin ASes announcing only one prefix: 6995 ARIN Region transit ASes present in the Internet Routing Table: 2009 Average ARIN Region AS path length visible: 4.6 Max ARIN Region AS path length visible: 39 Number of ARIN region 32-bit ASNs visible in the Routing Table: 5112 Number of ARIN addresses announced to Internet: 1348320256 Equivalent to 80 /8s, 93 /16s and 188 /24s ARIN AS Blocks 1-1876, 1902-2042, 2044-2046, 2048-2106 (pre-ERX allocations) 2138-2584, 2615-2772, 2823-2829, 2880-3153 3354-4607, 4865-5119, 5632-6655, 6912-7466 7723-8191, 10240-12287, 13312-15359, 16384-17407 18432-20479, 21504-23551, 25600-26591, 26624-27647, 29696-30719, 31744-33791 35840-36863, 39936-40959, 46080-47103 53248-55295, 62464-63487, 64198-64296, 393216-402332 ARIN Address Blocks 3/8, 4/8, 6/8, 7/8, 8/8, 9/8, 11/8, 12/8, 13/8, 15/8, 16/8, 17/8, 18/8, 19/8, 20/8, 21/8, 22/8, 23/8, 24/8, 26/8, 28/8, 29/8, 30/8, 32/8, 33/8, 34/8, 35/8, 38/8, 40/8, 44/8, 45/8, 47/8, 48/8, 50/8, 52/8, 54/8, 55/8, 56/8, 63/8, 64/8, 65/8, 66/8, 67/8, 68/8, 69/8, 70/8, 71/8, 72/8, 73/8, 74/8, 75/8, 76/8, 96/8, 97/8, 98/8, 99/8, 100/8, 104/8, 107/8, 108/8, 128/8, 129/8, 130/8, 131/8, 132/8, 134/8, 135/8, 136/8, 137/8, 138/8, 139/8, 140/8, 142/8, 143/8, 144/8, 146/8, 147/8, 148/8, 149/8, 152/8, 155/8, 156/8, 157/8, 158/8, 159/8, 160/8, 161/8, 162/8, 164/8, 165/8, 166/8, 167/8, 168/8, 169/8, 170/8, 172/8, 173/8, 174/8, 184/8, 192/8, 198/8, 199/8, 204/8, 205/8, 206/8, 207/8, 208/8, 209/8, 214/8, 215/8, 216/8, RIPE Region Analysis Summary ---------------------------- Prefixes being announced by RIPE Region ASes: 270355 Total RIPE prefixes after maximum aggregation: 130940 RIPE Deaggregation factor: 2.06 Prefixes being announced from the RIPE address blocks: 267312 Unique aggregates announced from the RIPE address blocks: 170400 RIPE Region origin ASes present in the Internet Routing Table: 28827 RIPE Prefixes per ASN: 9.27 RIPE Region origin ASes announcing only one prefix: 12086 RIPE Region transit ASes present in the Internet Routing Table: 3995 Average RIPE Region AS path length visible: 5.3 Max RIPE Region AS path length visible: 54 Number of RIPE region 32-bit ASNs visible in the Routing Table: 12191 Number of RIPE addresses announced to Internet: 732935552 Equivalent to 43 /8s, 175 /16s and 181 /24s RIPE AS Blocks 1877-1901, 2043, 2047, 2107-2136, 2585-2614 (pre-ERX allocations) 2773-2822, 2830-2879, 3154-3353, 5377-5631 6656-6911, 8192-9215, 12288-13311, 15360-16383 20480-21503, 24576-25599, 28672-29695 30720-31743, 33792-35839, 38912-39935 40960-45055, 47104-52223, 56320-58367 59392-61439, 61952-62463, 64396-64495 196608-216475 RIPE Address Blocks 2/8, 5/8, 25/8, 31/8, 37/8, 46/8, 51/8, 53/8, 57/8, 62/8, 77/8, 78/8, 79/8, 80/8, 81/8, 82/8, 83/8, 84/8, 85/8, 86/8, 87/8, 88/8, 89/8, 90/8, 91/8, 92/8, 93/8, 94/8, 95/8, 109/8, 141/8, 145/8, 151/8, 176/8, 178/8, 185/8, 188/8, 193/8, 194/8, 195/8, 212/8, 213/8, 217/8, LACNIC Region Analysis Summary ------------------------------ Prefixes being announced by LACNIC Region ASes: 123716 Total LACNIC prefixes after maximum aggregation: 29046 LACNIC Deaggregation factor: 4.26 Prefixes being announced from the LACNIC address blocks: 121137 Unique aggregates announced from the LACNIC address blocks: 48860 LACNIC Region origin ASes present in the Internet Routing Table: 11186 LACNIC Prefixes per ASN: 10.83 LACNIC Region origin ASes announcing only one prefix: 2642 LACNIC Region transit ASes present in the Internet Routing Table: 2528 Average LACNIC Region AS path length visible: 5.9 Max LACNIC Region AS path length visible: 56 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 9119 Number of LACNIC addresses announced to Internet: 177513728 Equivalent to 10 /8s, 148 /16s and 165 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-274844 + ERX transfers LACNIC Address Blocks 177/8, 179/8, 181/8, 186/8, 187/8, 189/8, 190/8, 191/8, 200/8, 201/8, AfriNIC Region Analysis Summary ------------------------------- Prefixes being announced by AfriNIC Region ASes: 34529 Total AfriNIC prefixes after maximum aggregation: 6622 AfriNIC Deaggregation factor: 5.21 Prefixes being announced from the AfriNIC address blocks: 47127 Unique aggregates announced from the AfriNIC address blocks: 15244 AfriNIC Region origin ASes present in the Internet Routing Table: 1910 AfriNIC Prefixes per ASN: 24.67 AfriNIC Region origin ASes announcing only one prefix: 690 AfriNIC Region transit ASes present in the Internet Routing Table: 373 Average AfriNIC Region AS path length visible: 6.0 Max AfriNIC Region AS path length visible: 65 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 1266 Number of AfriNIC addresses announced to Internet: 104323072 Equivalent to 6 /8s, 55 /16s and 216 /24s AfriNIC AS Blocks 36864-37887, 327680-329727 & ERX transfers AfriNIC Address Blocks 41/8, 102/8, 105/8, 154/8, 196/8, 197/8, APNIC Region per AS prefix count summary ---------------------------------------- ASN No of nets /20 equiv MaxAgg Description 9808 10240 8754 92 CHINAMOBILE-CN China Mobile Communication 7545 6197 842 664 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4754 4192 76 ERX-CERNET-BKB China Education and Resear 9498 4080 524 274 BBIL-AP BHARTI Airtel Ltd., IN 7552 3917 1331 25 VIETEL-AS-AP Viettel Group, VN 7713 3676 1036 72 TELKOMNET-AS-AP PT Telekomunikasi Indones 45899 3257 1869 101 VNPT-AS-VN VNPT Corp, VN 24560 2820 845 546 AIRTELBROADBAND-AS-AP Bharti Airtel Ltd., 4766 2279 11518 581 KIXS-AS-KR Korea Telecom, KR 4755 2220 434 192 TATACOMM-AS TATA Communications formerly Complete listing at https://thyme.apnic.net/current/data-ASnet-APNIC ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 16509 12607 38898 3295 AMAZON-02, US 11492 4693 312 549 CABLEONE, US 174 4184 8761 866 COGENT-174, US 7155 4169 287 85 VIASAT-SP-BACKBONE, US 6327 3615 1320 79 SHAW, CA 22773 3382 3033 185 ASN-CXA-ALL-CCI-22773-RDC, US 749 3262 54895 2509 DNIC-AS-00749, US 16625 2937 1263 2155 AKAMAI-AS, US 396982 2894 3656 440 GOOGLE-CLOUD-PLATFORM, US 7018 2734 23259 1860 ATT-INTERNET4, US Complete listing at https://thyme.apnic.net/current/data-ASnet-ARIN RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 12479 7664 1709 143 UNI2-AS, ES 39891 4750 290 62 ALJAWWALSTC-AS, SA 20940 3942 3395 129 AKAMAI-ASN1, NL 9009 3768 323 1907 M247, RO 12389 2979 2300 886 ROSTELECOM-AS, RU 34984 2371 360 576 TELLCOM-AS, TR 212238 1875 134 1383 CDNEXT, GB 8452 1630 1852 14 TE-AS TE-AS, EG 13188 1607 100 26 TRIOLAN, UA 62240 1499 99 752 CLOUVIDER Clouvider - Global ASN, GB Complete listing at https://thyme.apnic.net/current/data-ASnet-RIPE LACNIC Region per AS prefix count summary ----------------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 11591 3227 604 UNINET, MX 10620 3538 491 953 Telmex Colombia S.A., CO 13999 2532 538 368 Mega Cable, S.A. de C.V., MX 11830 1995 369 64 Instituto Costarricense de Electricidad y 28573 1332 2310 261 Claro NXT Telecomunicacoes Ltda, BR 3816 1329 778 207 COLOMBIA TELECOMUNICACIONES S.A. ESP BIC, 6503 1170 374 163 Axtel, S.A.B. de C.V., MX 11664 1136 278 33 Techtel LMDS Comunicaciones Interactivas 6147 1113 371 22 Telefonica del Peru S.A.A., PE 22884 1073 98 369 TOTAL PLAY TELECOMUNICACIONES SA DE CV, M Complete listing at https://thyme.apnic.net/current/data-ASnet-LACNIC AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 24835 1669 593 29 RAYA-AS, EG 24863 1645 389 18 LINKdotNET-AS, EG 29571 1585 100 68 ORANGE-COTE-IVOIRE, CI 36992 1425 1518 286 ETISALAT-MISR, EG 36903 1249 554 96 MT-MPLS, MA 36935 1001 521 42 Vodafone-, EG 20011 967 179 271 INTERNET-SOLUTIONS, ZA 37069 832 1083 15 MOBINIL, EG 6713 558 1861 35 IAM-AS, MA 36914 544 82 3 KENET-AS, KE Complete listing at https://thyme.apnic.net/current/data-ASnet-AFRINIC Global Per AS prefix count summary ---------------------------------- ASN No of nets /20 equiv MaxAgg Description 16509 12607 38898 3295 AMAZON-02, US 8151 11591 3227 604 UNINET, MX 9808 10240 8754 92 CHINAMOBILE-CN China Mobile Communication 12479 7664 1709 143 UNI2-AS, ES 7545 6197 842 664 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4754 4192 76 ERX-CERNET-BKB China Education and Resear 39891 4750 290 62 ALJAWWALSTC-AS, SA 11492 4693 312 549 CABLEONE, US 174 4184 8761 866 COGENT-174, US 7155 4169 287 85 VIASAT-SP-BACKBONE, US Complete listing at https://thyme.apnic.net/current/data-ASnet Global Per AS Maximum Aggregation summary ----------------------------------------- ASN No of nets Net Savings Description 8151 11591 10987 UNINET, MX 9808 10240 10148 CHINAMOBILE-CN China Mobile Communications Grou 12479 7664 7521 UNI2-AS, ES 7545 6197 5533 TPG-INTERNET-AP TPG Telecom Limited, AU 39891 4750 4688 ALJAWWALSTC-AS, SA 4538 4754 4678 ERX-CERNET-BKB China Education and Research Net 11492 4693 4144 CABLEONE, US 7155 4169 4084 VIASAT-SP-BACKBONE, US 7552 3917 3892 VIETEL-AS-AP Viettel Group, VN 20940 3942 3813 AKAMAI-ASN1, NL Complete listing at https://thyme.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Net Originated Transit AS Transit AS Name 400866 UNALLOCATED 2.59.148.0/23 21859 ZEN-ECN, US 22542 UNALLOCATED 8.7.205.0/24 3356 LEVEL3, US 33123 UNALLOCATED 8.10.69.0/24 174 COGENT-174, US 12169 UNALLOCATED 8.15.207.0/24 32787 PROLEXIC-TECHNOLOGIES-D 40493 UNALLOCATED 8.17.26.0/24 3356 LEVEL3, US 46639 UNALLOCATED 8.17.66.0/24 701 UUNET, US 53775 UNALLOCATED 8.20.88.0/24 7029 WINDSTREAM, US 393266 UNALLOCATED 8.23.52.0/24 46887 CROWNCASTLE-AS46887, US 396894 UNALLOCATED 8.28.201.0/24 46887 CROWNCASTLE-AS46887, US 394936 UNALLOCATED 8.33.224.0/24 22442 HOU-PHONOSCOPE, US Complete listing at https://thyme.apnic.net/current/data-badAS Prefixes from the Special Purpose Address Registry (Global) ----------------------------------------------------------- Prefix Origin AS Description 192.88.99.0/24 6939 HURRICANE, US Complete listing at https://thyme.apnic.net/current/data-spar Advertised Unallocated Addresses -------------------------------- Unassigned Network ASN Information AS Name 14.192.20.0/22 Origin: 26658 HENGTONG-IDC-LLC, US 14.192.20.0/22 Transit: 6939 HURRICANE, US 23.132.192.0/24 Origin: 30500 WOLFPAWSERVICES, CA 23.132.192.0/24 Transit: 6939 HURRICANE, US 23.140.16.0/24 Origin: 63371 RESERVED, ZZ 23.140.16.0/24 Transit: 10796 TWC-10796-MIDWEST, US 23.140.48.0/24 Origin: 63371 RESERVED, ZZ 23.140.48.0/24 Transit: 7018 ATT-INTERNET4, US 23.140.176.0/24 Origin: 40676 AS40676, US 23.140.176.0/24 Transit: 7922 COMCAST-7922, US Complete listing at https://thyme.apnic.net/current/data-add-IANA Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:16 /9:16 /10:42 /11:93 /12:311 /13:591 /14:1220 /15:2153 /16:13993 /17:8319 /18:13792 /19:24799 /20:44705 /21:52466 /22:112381 /23:100787 /24:596567 /25:694 /26:0 /27:0 /28:0 /29:0 /30:0 /31:0 /32:0 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 12479 6629 7664 UNI2-AS, ES 8151 5786 11591 UNINET, MX 11492 3555 4693 CABLEONE, US 39891 3441 4750 ALJAWWALSTC-AS, SA 6327 3410 3615 SHAW, CA 7155 3117 4169 VIASAT-SP-BACKBONE, US 22773 2518 3382 ASN-CXA-ALL-CCI-22773-RDC, US 16509 2256 12607 AMAZON-02, US 30036 2227 2565 MEDIACOM-ENTERPRISE-BUSINESS, US 10620 2178 3538 Telmex Colombia S.A., CO Complete listing at https://thyme.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1654 2:1555 3:541 4:9 5:4489 6:165 7:6 8:1556 9:1 11:172 12:1388 13:357 14:2523 15:334 16:270 17:360 18:906 20:449 21:4 22:188 23:7205 24:2733 25:2 27:2610 29:19 31:3061 32:40 34:69 35:177 36:2406 37:4510 38:9123 39:882 40:151 41:4169 42:977 43:2494 44:344 45:18100 46:4940 47:294 49:2013 50:1870 51:587 52:1570 54:307 55:1029 56:8 57:235 58:2278 59:1244 60:1160 61:2791 62:2921 63:1834 64:5409 65:2207 66:4637 67:3016 68:1226 69:3990 70:1104 71:600 72:2859 74:2787 75:1633 76:636 77:2594 78:1847 79:1705 80:2231 81:2032 82:1829 83:1419 84:1810 85:3272 86:983 87:2409 88:1273 89:4329 90:755 91:8316 92:2759 93:2842 94:3845 95:4168 96:1265 97:311 98:1006 99:733 100:71 101:1139 102:3750 103:32307 104:4546 105:747 106:1013 107:2601 108:1192 109:4072 110:2231 111:3348 112:2040 113:1526 114:1935 115:2141 116:2030 117:2740 118:2887 119:1946 120:1886 121:1414 122:2748 123:2169 124:1600 125:2880 126:62 128:1577 129:952 130:1254 131:1868 132:811 133:450 134:1513 135:322 136:1335 137:1145 138:2882 139:1547 140:1537 141:1459 142:1823 143:1592 144:1039 145:465 146:2124 147:2042 148:2590 149:2856 150:1198 151:1611 152:2113 153:500 154:7885 155:1592 156:3397 157:1867 158:1254 159:2443 160:3455 161:1782 162:3621 163:1777 164:1692 165:2157 166:1343 167:1867 168:4106 169:799 170:5071 171:999 172:4010 173:3167 174:916 175:1262 176:3577 177:4928 178:3754 179:2230 180:2542 181:3970 182:3352 183:1833 184:2259 185:21362 186:5067 187:4262 188:4236 189:4142 190:9593 191:1568 192:11230 193:9326 194:7682 195:5432 196:3242 197:3533 198:6128 199:8285 200:8072 201:6319 202:10557 203:10481 204:4601 205:3687 206:4669 207:3610 208:4199 209:5141 210:4780 211:2618 212:4525 213:3749 214:1053 215:48 216:6585 217:3082 218:1383 219:538 220:2107 221:1051 222:846 223:2328 End of report

1 0

** Sneak Peek at N93! 🚀Hackathon, Women in Tech Mixer + MORE
by Nanog News 09 Jan '25

09 Jan '25

*** Discover What’s in Store: Sneak Peek at N93! 🚀* ------------------------------------------------------------ Only 25 Days Until NANOG 93! Don't Miss Out - Register Now! *Preview Keynote Speaker, Socials, Fun Facts about Atlanta, + More!* *Coming to the NANOG 93 Stage:* + The Road Towards a Quantum Internet + Networking for AI + Demystifying Clos Fabrics + DNS Session: Let's Stop Using DNS + Measuring Starlink Protocol Performance *MORE INFO* <https://nanog.org/events/nanog-93/> ( https://nanog.org/events/nanog-93/) *** Don't Wait to Register — Hackathon Intro Kicking Off Soon!* ------------------------------------------------------------ *Hackathon Introduction — Friday, 31 Jan. On Zoom* *Theme:* Put Your Sleuthing Skills to the Test! *Focus: *Problem-Solving/Troubleshooting Competitions *Important Dates:* Friday, 31 Jan. — Hackathon Welcome, Introduction, Infrastructure Tutorial, and Team-Forming session over Zoom. Monday + Tuesday, 03-04 Feb. — Hackathon Competition at Conference *MORE INFO <https://nanog.org/events/nanog-93-hackathon/> *( https://nanog.org/events/nanog-93-hackathon/) *** Trailblazers Unite: Join Us at the Women in Tech Mixer!* ------------------------------------------------------------ *Taking Place On Sunday, 02 Feb. BEFORE N93 In Atlanta!* Your opportunity to connect, share, + have some fun with fellow brilliant Women in Tech shaping our future! *MORE INFO* <https://nanog.org/events/nanog-93/socials/> ( https://nanog.org/events/nanog-93/socials/) *** Video of the Week — NANOG 92 Recap!* ------------------------------------------------------------ *Reflecting on NANOG 92: Memories That Inspire Us Forward* As we look back on the incredible moments of N92, we’re reminded that this isn’t just a gathering—it’s a community. What’s next? The road doesn’t end here! Mark your calendars and join us for N93—a chance to reconnect, grow, and continue building the future of networking together. *WATCH NOW <https://nanog.org/stories/nanog-tv/nanog-92-recap/> *( https://nanog.org/stories/nanog-tv/nanog-92-recap/) *** Get Ready for an Exciting Year with NANOG in 2025!* ------------------------------------------------------------ *Save the Dates (and Locations): Fantastic Lineup Headed Your Way* *📅 Upcoming NANOG 2025 Meetings:* 🗓 NANOG 93: 3 - 5 Feb. — Atlanta, GA 🗓 NANOG 94: 9 - 11 Jun. — Denver, CO 🗓 NANOG 95: 27 - 29 Oct. — Arlington, TX *SEE MORE <https://nanog.org/events/future/> *( https://nanog.org/events/future/) *** Stay Connected* ------------------------------------------------------------ http://www.facebook.com http://www.instagram.com/nanog_org/ http://www.linkedin.com/company/nanog/ https://www.twitter.com/nanog/ http://nanog.org

1 0