[outages] Level 3 Peering with Verizon/MCI

[Grant Ridder]

This is being discussed on the NANOG list.
http://mailman.nanog.org/pipermail/nanog/2013-August/060642.html


On Wed, Aug 28, 2013 at 9:23 AM, Daniel Green <dgreen at momentumtelecom.com>wrote:

>  Anyone else seeing huge latency between level 3 and Verizon this
> morning? I am have complaints of voice quality and call failures tracing to
> certain locations my times start jumping up.****
>
> ** **
>
> traceroute 98.109.171.43****
>
>  ****
>
> Type escape sequence to abort.****
>
> Tracing the route to static-98-109-171-43.nwrknj.fios.verizon.net(98.109.171.43)
> ****
>
>  ****
>
>   1 4 msec 0 msec 0 msec****
>
>   2 ge-6-18.car1.LasVegas1.Level3.net (4.71.176.101) 68 msec 4 msec 4 msec
> ****
>
>   3 ae-2-5.bar1.LasVegas1.Level3.net (4.69.148.130) [MPLS: Label 306688
> Exp 0] 0 msec 0 msec 4 msec****
>
>   4 ae-0-11.bar2.LasVegas1.Level3.net (4.69.148.126) [MPLS: Label 303936
> Exp 0] 0 msec 0 msec 0 msec****
>
>   5 ae-6-6.ebr1.Denver1.Level3.net (4.69.148.2) [MPLS: Label 1948 Exp 0]
> 36 msec 36 msec 32 msec****
>
>   6 ae-2-2.ebr2.Dallas1.Level3.net (4.69.132.106) [MPLS: Label 1935 Exp
> 0] 36 msec 36 msec 32 msec****
>
>   7 ae-62-62.csw1.Dallas1.Level3.net (4.69.151.129) [MPLS: Label 1921 Exp
> 0] 36 msec 36 msec****
>
>     ae-92-92.csw4.Dallas1.Level3.net (4.69.151.165) [MPLS: Label 1728 Exp
> 0] 32 msec****
>
>   8  *****
>
>     4.69.145.82 32 msec *****
>
>   9 MCI-level3-ae.dallas3.level3.net (4.68.62.34) 352 msec****
>
>     mci-level3-30g.dallas3.level3.net (4.68.62.166) 136 msec 420 msec****
>
> 10 P0-15-0-0.NWRKNJ-LCR-22.verizon-gni.net (130.81.199.17) 384 msec 348
> msec****
>
>     P0-4-0-0.NWRKNJ-LCR-22.verizon-gni.net (130.81.22.65) 176 msec****
>
> 11  *  *  *****
>
> 12  *  *****
>
>     static-98-109-171-43.nwrknj.fios.verizon.net (98.109.171.43) 336 msec*
> ***
>
> ** **
>
> tracert 98.109.171.43****
>
>  ****
>
> Tracing route to static-98-109-171-43.nwrknj.fios.verizon.net[98.109.171.43]
> ****
>
> over a maximum of 30 hops:****
>
>  ****
>
>   1    <1 ms    <1 ms    <1 ms  ****
>
>   2     1 ms     1 ms     1 ms  ****
>
>   3     4 ms     4 ms     4 ms  atlanta2.level3.net ****
>
>  ****
>
>   4    24 ms    24 ms    24 ms  ae-13-13.car1.atlanta2.level3.net[4.69.151.17]
> ****
>
>  ****
>
>   5    26 ms    24 ms    24 ms  vlan52.ebr2.atlanta2.level3.net[4.69.150.126]
> ****
>
>   6    24 ms    24 ms    24 ms  ae-73-73.ebr3.atlanta2.level3.net[4.69.148.253]
> ****
>
>  ****
>
>   7    24 ms    24 ms    24 ms  ae-7-7.ebr3.dallas1.level3.net[4.69.134.21]
> ****
>
>   8    24 ms    24 ms    24 ms  ae-83-83.csw3.dallas1.level3.net[4.69.151.157]
> ****
>
>  ****
>
>   9    24 ms    24 ms    24 ms  ae-3-80.edge10.dallas1.level3.net[4.69.145.146]
> ****
>
>  ****
>
> 10   332 ms   329 ms     *     mci-level3-ae.dallas3.level3.net[4.68.62.34]
> ****
>
> 11   341 ms   343 ms   339 ms  p0-4-0-0.nwrknj-lcr-21.verizon-gni.net[130.81.2
> ****
>
> 2.63]****
>
> 12     *        *        *     Request timed out.****
>
> 13   352 ms   356 ms   359 ms
> static-98-109-171-43.nwrknj.fios.verizon.net [98****
>
> .109.171.43]****
>
> ** **
>
> ** **
>
> ---****
>
> Respectfully,****
>
> ** **
>
> ** **
>
> *Daniel L. Green II*
> Network Engineer
> Momentum | www.gomomentum.com
> O: 702.933.1545 Ext: 1337****
>
> W: 702.403.1234****
>
> F: 702.365.8647
> Facebook <http://www.facebook.com/MomentumBusiness> | Twitter<https://twitter.com/#!/MomentumTelecom>
>  | LinkedIn <http://www.linkedin.com/company/55869>****
>
> [image: Description: Description: Description: Momentum Logo] ****
>
>  ****
>
>  ****
>
> 8350 S. Durango | Suite 220 | Las Vegas | Nevada | 89113****
>
> ** **
>
> _______________________________________________
> Outages mailing list
> Outages at outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages/attachments/20130828/a5bbcb53/attachment.htm>