Re: AS7018 upstream loss via 32.130.88.22 (SF Bay Area) — per-flow, unidirectional

[Christopher Morrow via NANOG <nanog () lists nanog org>]

On Tue, Aug 25, 2026 at 1:13 PM BEASLEY, JOSH via NANOG
<nanog () lists nanog org> wrote:
> Hop 9 is the last hop on AS7018. The hop you were concerned with is no longer in the path and it would have been one 
> of the first few hops in your trace if it was there.
>
> Josh
>
> From: Al via NANOG <nanog () lists nanog org>
> Sent: Tuesday, August 25, 2026 11:00 AM
> To: mikecika--- via NANOG <nanog () lists nanog org>
> Cc: Al <awnanog () sunnyside com>
> Subject: Re: AS7018 upstream loss via 32.130.88.22 (SF Bay Area) — per-flow, unidirectional
>
> Maybe Josh fixed it, but I'm not seeing packet loss here. Odd that traceroutes stop at the 32. 130. . . Because of 
> that I cannot see if I am transiting 32. 130. 88. 22 → 32. 130. 20. 157 or not. al@ post: /z/dns$ traceroute ibm. com 
> traceroute to ibm. com
>
>
> Maybe Josh fixed it, but I'm not seeing packet loss here.
>
> Odd that traceroutes stop at the 32.130...
>
> Because of that I cannot see if I am transiting 32.130.88.22 →
>
> 32.130.20.157 or not.

I'd guess that (since traceroutes to this space from outside 7018 seem
to just die a the 7018 border) this is CGNat space for ATT Fiber
customers...
I suspect  this all has to be fixed inside the 7018 cloud, and there's
not much 'nanog' peoples can generally do for this problem, eh? :)
(so calling the att support folks, booting your win98 computer and
rebooting it with them on the phone - pstn -  THEN getting them perf /
traceroute data is required)
_______________________________________________
NANOG mailing list 
https://lists.nanog.org/archives/list/nanog () lists nanog org/message/4C6KWQUU2C2KZNLMSBRPYZWZDFYF6QJS/