I think that's precisely the problem, that the issue could not have been handled "though other methods". I agree NANOG is not a replacement for NOCs, but what about when the NOCs are utterly useless and the issue is global in scope? Given the parties involved, I'd like to think that Logan tried to go through standard channels prior to posting. Please realize this is no slight against nLayer, but rather, "the new AT&T" and their concept of customer service. Paul On Fri, Jul 18, 2008 at 1:50 PM, Ren Provo <ren.provo@gmail.com> wrote:
What did your upstream transit supplier advise before you escalated this to the global audience at NANOG? This is the second time in 24hrs you have requested assistance here which could have been handled via other methods. -ren
On Fri, Jul 18, 2008 at 1:30 PM, Logan Rawlins <logan.rawlins@highwinds.com> wrote:
Anyone from sbcglobal out there? i'm seeing a routing loop. Please contact me off list thanks.
sourceip: 69.16.137.66
tracert 75.58.215.133
Tracing route to adsl-75-58-215-133.dsl.hstntx.sbcglobal.net [ 75.58.215.133] over a maximum of 30 hops:
1 2 ms <1 ms <1 ms 192.168.113.1 2 1 ms 2 ms 2 ms 69.16.137.66 3 1 ms 2 ms 2 ms e-2-21-1000m.core-04.phx2.puregig.net [69.16.128 .110] 4 2 ms 2 ms 5 ms v303.ar1.ph.hwng.net [69.16.128.137] 5 1 ms 1 ms 2 ms ve1011.r2.ph.hwng.net [69.16.190.161] 6 11 ms 20 ms 11 ms 2-1.r1.la.hwng.net [69.16.191.37] 7 12 ms 11 ms 11 ms vl101.ar1.lax1.us.nlayer.net [69.31.127.29] 8 11 ms 11 ms 11 ms ae0-60.cr1.lax1.us.nlayer.net [69.31.127.165] 9 11 ms 11 ms 11 ms ex1-g12-0.eqlaca.sbcglobal.net [69.31.127.50] 10 11 ms 11 ms 11 ms 151.164.188.139 11 11 ms 11 ms 11 ms bb2-p14-0.scrm01.sbcglobal.net [151.164.188.138]
12 11 ms 11 ms 11 ms 151.164.188.139 13 11 ms 11 ms 11 ms bb2-p14-0.scrm01.sbcglobal.net [151.164.188.138]
14 14 ms 11 ms 11 ms 151.164.188.139 15 11 ms 11 ms 11 ms bb2-p14-0.scrm01.sbcglobal.net [151.164.188.138]
16 11 ms 11 ms 11 ms 151.164.188.139 17 11 ms 12 ms 11 ms bb2-p14-0.scrm01.sbcglobal.net [151.164.188.138]
18 11 ms 11 ms 11 ms 151.164.188.139 19 12 ms 11 ms 11 ms bb2-p14-0.scrm01.sbcglobal.net [151.164.188.138]
20 12 ms 11 ms 11 ms 151.164.188.139 21 11 ms 11 ms 12 ms bb2-p14-0.scrm01.sbcglobal.net [151.164.188.138]
22 11 ms 11 ms 11 ms 151.164.188.139 23 14 ms 11 ms 12 ms bb2-p14-0.scrm01.sbcglobal.net [151.164.188.138]
24 11 ms 11 ms 11 ms 151.164.188.139 25 11 ms 11 ms 16 ms bb2-p14-0.scrm01.sbcglobal.net [151.164.188.138]
26 14 ms 11 ms 12 ms 151.164.188.139 27 11 ms 12 ms 12 ms bb2-p14-0.scrm01.sbcglobal.net [151.164.188.138]
28 12 ms 11 ms 11 ms 151.164.188.139 29 11 ms 12 ms 12 ms bb2-p14-0.scrm01.sbcglobal.net [151.164.188.138]
30 11 ms 11 ms 11 ms 151.164.188.139
Trace complete.