- NANOG - lists.nanog.org

Twelve99 Contact Info
by Elijah Savage 08 Feb '23

08 Feb '23

For the past two weeks we have seen increased latency coming from Asia. On my side this is from multiple providers/AS's below is just one example. I have tried to reach out to them directly but no response as of yet. Anyone with a contact or seeing the same high latency?

1 0

LINX is down?
by Dmitry Sherman 08 Feb '23

08 Feb '23

Hello any problems with Linx? Dmitry

2 1

Lima, OH Spectrum/Charter Severe Node/Hop Latency Issues
by Austin Ayers 08 Feb '23

08 Feb '23

Hello all, One of my NetOps engineers resides in Lima, Ohio and they are receiving terrible bufferbloat, packet loss, and random disconnects. I have been pinging 24.33.160.213 (Lima, OH Spectrum/Chart Node) and it's rejecting a ton of packets. This has been going on for weeks. Node having problems: lag-1.limaohid01h.netops.charter.com NOC seems like they don't care, same with OSP in the field. There is no reason why this hop (#13) should have up to 613ms ping times. Thank you, Austin [cid:d929237e-d932-4060-9dbb-f4b99b12afa4]

4 3

Re: [EXTERNAL]INC000026031132 RE: Lima, Ohio Spectrum Hop/Node Having Severe Packet Loss
by Austin Ayers 07 Feb '23

07 Feb '23

Thank you, The IP of his gateway is 65.29.110.132 - as you can see it's having horrible ping times to go a few city blocks (56ms) in addition to the horrid drops. I believe several tickets have been opened for his address too, 1718 Leland Ave. Lima, OH 45805 Thank you! -Austin [cid:53d8905f-681a-4dfd-819e-ab68644238fd] ________________________________ From: NOC.AUS.NATL.BBN <NOC.AUS.NATL.BBN(a)charter.com> Sent: Tuesday, February 7, 2023 5:03 PM To: Austin Ayers <austin(a)coretransit.net>; nanog(a)nanog.org <nanog(a)nanog.org> Cc: NOC.AUS.NATL.BBN <NOC.AUS.NATL.BBN(a)charter.com> Subject: [EXTERNAL]INC000026031132 RE: Lima, Ohio Spectrum Hop/Node Having Severe Packet Loss All I opened INC000026031132 for our CBO-CSC team to review Thank you, James Wynn | Network Engineer III | Austin NOC 866.248.7662 option 2 option 5 [cid:image001.png@01D93B0D.995D1C10] 13620-A North FM 620, Suite 200 | Austin, TX 78717 From: Austin Ayers <austin(a)coretransit.net> Sent: Tuesday, February 7, 2023 3:53 PM To: nanog(a)nanog.org Cc: NOC.AUS.NATL.BBN <NOC.AUS.NATL.BBN(a)charter.com> Subject: [EXTERNAL] Re: Lima, Ohio Spectrum Hop/Node Having Severe Packet Loss CAUTION: The e-mail below is from an external source. Please exercise caution before opening attachments, clicking links, or following guidance. [cid:image002.jpg@01D93B0D.995D1C10] [cid:image003.png@01D93B0D.995D1C10] ________________________________ From: Austin Ayers Sent: Tuesday, February 7, 2023 4:46 PM To: nanog(a)nanog.org<mailto:nanog@nanog.org> <nanog(a)nanog.org<mailto:nanog@nanog.org>> Cc: NOC.AUS.NATL.BBN(a)charter.com<mailto:NOC.AUS.NATL.BBN@charter.com> <NOC.AUS.NATL.BBN(a)charter.com<mailto:NOC.AUS.NATL.BBN@charter.com>> Subject: Lima, Ohio Spectrum Hop/Node Having Severe Packet Loss Hello all, One of my NetOps engineers resides in Lima, Ohio and they are receiving terrible bufferbloat, packet loss, and random disconnects. I have been pinging 24.33.160.213 (Lima, OH Spectrum/Chart Node) and it's rejecting a ton of packets. This has been going on for weeks. Node having problems: lag-1.limaohid01h.netops.charter.com NOC seems like they don't care, same with OSP in the field. There is no reason why this hop (#13) should have up to 613ms ping times. Thank you, Austin [cid:image003.png@01D93B0D.995D1C10] The contents of this e-mail message and any attachments are intended solely for the addressee(s) and may contain confidential and/or legally privileged information. If you are not the intended recipient of this message or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message and any attachments. If you are not the intended recipient, you are notified that any use, dissemination, distribution, copying, or storage of this message or any attachment is strictly prohibited.

1 0

About emails impersonating Path Network
by Konrad Zemek 07 Feb '23

07 Feb '23

Hi Nanog, It looks like someone with an axe to grind against our company has decided to email every AS contact they could find on PeeringDB, impersonating us and sometimes spoofing our domains. We're aware of the emails and are sorry for the inconvenience. We've since added SPF records to the domains we own but don't use (the perps have since name-squatted some new ones). We're also actively working with law enforcement on the matter. Thanks Konrad Zemek CTO Path Network AS396998

7 10

Watch NANOG Hackathon, N87 Socials, + More
by Nanog News 07 Feb '23

07 Feb '23

*WATCH Hackathon Welcome Session* *Meet Project Vendors, Get Project Ideas, + More * *Hybrid NANOG 87 Hackathon kicked-off last Friday, 3 Feb. and will continue until Sunday, 12 Feb. * Watch video to meet project vendors, get ideas for potential Hackathon projects, and check out resources to ensure a successful Hackathon. *WATCH NOW* <https://www.nanog.org/events/nanog-87-hackathon/> *Connect with Old + New Friends at NANOG 87 Socials!* *Don't Miss out on NANOG 87 Social Events Next Week* *Our community is what makes NANOG special. *Connect with the phenomenal women and men that make up the heart of our mission at our NANOG Social events, taking place during NANOG 87. Check out full details below! * MORE INFO <https://www.nanog.org/events/nanog-87/socials/>* *Can't Make it to Atlanta? Still Time to Register Virtually* NANOG 87 will Kick Off Monday! There is still time to register for NANOG 87. Can't make it to Atlanta? Join us virtually! Stream presentations, participate in real-time chat forums, and enjoy the 360 camera views of NANOG 87 General Session + more! *REGISTER NOW* <https://www.nanog.org/events/nanog-87/> *What's Hot on The Mailing List? * *Participate or Find a Tech Solution in the Community Forum Mailing List * Remember, a NANOG account must be created to access the Community Forum. *Current Trending Conversations:* • Spectrum (legacy TWC) Infrastructure - Contact Off List Replies 26 <https://community.nanog.org/t/spectrum-legacy-twc-infrastructure-contact-of…> • Smaller than a /24 for BGP? Replies 32 <https://community.nanog.org/t/smaller-than-a-24-for-bgp/56993> • Typical last mile battery runtime (protecting against power cuts) Replies 31 <https://community.nanog.org/t/typical-last-mile-battery-runtime-protecting-…> • 202203071610.AYC Re: Making Use of 240/4 NetBlock Replies 338 <https://community.nanog.org/t/202203071610-ayc-re-making-use-of-240-4-netbl…> • Increasing problems with geolocation/IPv4 access Replies 13 <https://community.nanog.org/t/increasing-problems-with-geolocation-ipv4-acc…> *WHAT'S HOT* <https://community.nanog.org>

1 0

MX204 and MPC7E-MRATE EoL - REVOKED
by Aaron Gould 07 Feb '23

07 Feb '23

Did you hear? EoL was revoked December 2022... I'm so glad, I like and use the MX204 and the MPC7E-MRATE TSB69626 - 12/5/2022 - Revoke End of Life Announcement: MX204 https://supportportal.juniper.net/s/article/Revoke-End-of-Life-Announcement… <https://supportportal.juniper.net/s/article/Revoke-End-of-Life-Announcement…> TSB69631 - 12/2/2022 - Revoke End of Life Announcement: MPC7E-MRATE, MPC7E-MRATE-RTU https://supportportal.juniper.net/s/article/Revoke-End-of-Life-Announcement… <https://supportportal.juniper.net/s/article/Revoke-End-of-Life-Announcement…> -Aaron

3 3

Caribnog email list
by David Bass 07 Feb '23

07 Feb '23

Anyone on here run it? The URL to sign up on the website doesn’t seem to work at the moment.

3 2

recaptcha
by William Herrin 07 Feb '23

07 Feb '23

Has anybody else noticed that when Google Recaptcha falls over to presenting images, their data is of such poor quality that they've misclassified at least one image in upwards of half the presentations, rendering them unsolvable? If y'all aren't going to maintain the service to a production standard, you should retire it. Regards, Bill Herrin -- For hire. https://bill.herrin.us/resume/

2 2

Widespread connectivity problems in the west, possibly Lumen
by Mel Beckman 06 Feb '23

06 Feb '23

We are getting reports of widespread connectivity problems: VPN failures, email delivery failures, RingCentral VoIP dropped calls, and the inability to reach O365. Affected users are as far East as Las Cruces, NM. All failing destinations are so far in California-based data centers. So far a common thread appears to be Lumen connectivity, although we can’t verify this is exclusive to Lumen transit. However, the reachability problems don’t seem to be getting resolved by BGP routing, so multi homed customers are still using lumen, even if lumen has no apparent reachability. -mel

1 0