A reminder to all who haven't to review this presentation on interpreting traceroutes: https://archive.nanog.org/meetings/nanog47/presentations/Sunday/RAS_Traceroute_N47_Sun.pdf
On Wed, Aug 28, 2019 at 6:11 PM Hugo Slabbert via Outages < [email protected]> wrote: > At hop 9 in your trace? > > 9. lag-82.ear2.Chicago2.Level3.net > 72.7% 45 25.9 28.3 24.5 48.5 7.1 > 10. ??? > 11. ARMSTRONG-U.ear3.Washington1.Level3.net > 0.0% 45 43.5 44.5 37.6 154.2 23.2 > > There is no loss on subsequent hops; is there a reason why drops in the > middle of the trace are a problem? Are there points past > ARMSTRONG-U.ear3.Washington1.Level3.net / 4.14.224.174 that are also > experiencing issues? > > > Hugo Slabbert > > Network Engineer > > Demonware Inc, 700 - 369 Terminal Avenue, Vancouver, BC V6A 4C4, Canada > > www.demonware.net > > > > > On Wed, Aug 28, 2019 at 3:04 PM Josh Luthman <[email protected]> > wrote: > >> The 80% packet loss. >> >> Josh Luthman >> Office: 937-552-2340 >> Direct: 937-552-2343 >> 1100 Wayne St >> Suite 1337 >> Troy, OH 45373 >> >> On Wed, Aug 28, 2019, 5:58 PM Hugo Slabbert <[email protected]> >> wrote: >> >>> The second trace from Josh Luthman completes without issue I mean; for >>> the first it doesn't complete but shows consistent latency and no loss to >>> the hop past the highlighted one(s). >>> >>> >>> Hugo Slabbert >>> >>> Network Engineer >>> >>> Demonware Inc, 700 - 369 Terminal Avenue, Vancouver, BC V6A 4C4, Canada >>> >>> www.demonware.net >>> >>> >>> >>> >>> On Wed, Aug 28, 2019 at 2:57 PM Hugo Slabbert <[email protected]> >>> wrote: >>> >>>> What's the issue? The trace completes just fine and latency and loss do >>>> not persist past that intermediate hop. >>>> >>>> >>>> Hugo Slabbert >>>> >>>> Network Engineer >>>> >>>> Demonware Inc, 700 - 369 Terminal Avenue, Vancouver, BC V6A 4C4, Canada >>>> >>>> www.demonware.net >>>> >>>> >>>> >>>> >>>> On Wed, Aug 28, 2019 at 1:13 PM Josh Luthman via Outages < >>>> [email protected]> wrote: >>>> >>>>> Looks like we're seeing this as well. This is a Spectrum DIA circuit >>>>> in Troy, OH. >>>>> >>>>> Host >>>>> Loss% Snt Last Avg Best Wrst StDev >>>>> 1. 10.10.10.1 >>>>> 0.0% 46 1.1 2.9 1.1 61.5 8.9 >>>>> 2. fwbb-192-149-254-1.inxnet.net >>>>> 0.0% 46 1.3 4.0 1.1 41.3 7.8 >>>>> 3. fwb-74-218-88-129.inxnet.net >>>>> 0.0% 46 1.7 12.0 1.6 122.8 26.6 >>>>> 4. network-065-189-190-191.bcs.neo.rr.com >>>>> 0.0% 46 3.8 20.2 2.1 149.2 33.0 >>>>> 5. be39.gmtwoh0501r.midwest.rr.com >>>>> 0.0% 46 9.8 14.0 9.6 119.0 16.9 >>>>> 6. be12.blasohdp01r.midwest.rr.com >>>>> 0.0% 46 11.4 18.9 9.5 128.5 21.8 >>>>> 7. be28.clmkohpe01r.midwest.rr.com >>>>> 0.0% 45 12.8 16.6 8.5 107.0 16.2 >>>>> 8. 107.14.17.252 >>>>> 0.0% 45 25.8 29.1 19.0 129.4 22.7 >>>>> 9. lag-82.ear2.Chicago2.Level3.net >>>>> 72.7% 45 25.9 28.3 24.5 48.5 7.1 >>>>> 10. ??? >>>>> 11. ARMSTRONG-U.ear3.Washington1.Level3.net >>>>> 0.0% 45 43.5 44.5 37.6 154.2 23.2 >>>>> >>>>> Josh Luthman >>>>> Office: 937-552-2340 >>>>> Direct: 937-552-2343 >>>>> 1100 Wayne St >>>>> Suite 1337 >>>>> Troy, OH 45373 >>>>> >>>>> >>>>> On Wed, Aug 28, 2019 at 11:03 AM Biddle, Josh via Outages < >>>>> [email protected]> wrote: >>>>> >>>>>> Seeing a traffic issue ingress to North Eastern PA from OH and KY on >>>>>> the Spectrum network. Reported issue to Spectrum but no details yet. This >>>>>> started yesterday morning 8/27. Anyone else seeing these issues? >>>>>> >>>>>> >>>>>> >>>>>> 2 142.254.147.241 20 msec 20 msec 10 msec 20 msec 20 msec 10 msec 20 >>>>>> msec 20 msec 20 msec 20 msec >>>>>> >>>>>> 3 74.128.8.57 20 msec 20 msec 10 msec 20 msec 20 msec 20 msec 20 >>>>>> msec 20 msec 20 msec 10 msec >>>>>> >>>>>> 4 65.29.31.60 30 msec 20 msec 30 msec 30 msec 30 msec 30 msec 20 >>>>>> msec 30 msec 20 msec 40 msec >>>>>> >>>>>> 5 65.189.140.166 30 msec 50 msec 30 msec 40 msec 40 msec 40 msec 40 >>>>>> msec 40 msec 50 msec 40 msec >>>>>> >>>>>> 6 66.109.6.70 50 msec >>>>>> >>>>>> 66.109.6.66 50 msec 40 msec >>>>>> >>>>>> 66.109.6.70 50 msec 50 msec >>>>>> >>>>>> 66.109.6.66 40 msec 50 msec >>>>>> >>>>>> 66.109.6.70 50 msec 40 msec 40 msec >>>>>> >>>>>> 7 107.14.19.65 40 msec >>>>>> >>>>>> 107.14.19.160 50 msec >>>>>> >>>>>> 66.109.6.167 40 msec >>>>>> >>>>>> 107.14.19.65 40 msec 40 msec 40 msec 40 msec >>>>>> >>>>>> 66.109.6.167 40 msec 50 msec 50 msec >>>>>> >>>>>> 8 * * >>>>>> >>>>>> 66.109.7.162 730 msec 580 msec * * * 700 msec 600 msec 590 >>>>>> msec >>>>>> >>>>>> 9 * * * * * * * * * * >>>>>> >>>>>> 10 4.14.224.174 50 msec 50 msec 50 msec 70 msec 50 msec 50 msec 50 >>>>>> msec 60 msec 50 msec 60 msec >>>>>> >>>>>> 11 * * * * * * * * * * >>>>>> >>>>>> 12 * * * * * * * * * * >>>>>> >>>>>> 13 * * * * * * * * * * >>>>>> >>>>>> 14 * * * * * * * * * * >>>>>> >>>>>> >>>>>> >>>>>> – Josh B >>>>>> This email and its attachments may contain privileged and >>>>>> confidential information and/or protected health information (PHI) >>>>>> intended >>>>>> solely for the use of Netsmart Technologies and the recipient(s) named >>>>>> above. If you are not the recipient, or the employee or agent responsible >>>>>> for delivering this message to the intended recipient, you are hereby >>>>>> notified that any review, dissemination, distribution, printing or >>>>>> copying >>>>>> of this email message and/or any attachments is strictly prohibited. If >>>>>> you >>>>>> have received this transmission in error, please email >>>>>> [email protected] >>>>>> immediately and permanently delete this email and any attachments. >>>>>> _______________________________________________ >>>>>> Outages mailing list >>>>>> [email protected] >>>>>> https://puck.nether.net/mailman/listinfo/outages >>>>>> >>>>> _______________________________________________ >>>>> Outages mailing list >>>>> [email protected] >>>>> https://puck.nether.net/mailman/listinfo/outages >>>>> >>>> _______________________________________________ > Outages mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/outages >
_______________________________________________ Outages mailing list [email protected] https://puck.nether.net/mailman/listinfo/outages
