[outages] Windstream voice issues?
Anyone seeing issues with Windstream’s voice network this morning? We’re seeing intermittent problems with inbound and outbound calling, looks like it started shortly after 8:45am CST. -- Julian Y. Koh Acting Associate Director, Telecommunications and Network Services Northwestern University Information Technology (NUIT) 2001 Sheridan Road #G-166 Evanston, IL 60208 847-467-5780 NUIT Web Site: http://www.it.northwestern.edu/ PGP Public Key:http://bt.ittns.northwestern.edu/julian/pgppubkey.html ___ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
[outages] unsubscribe
unsubscribe ___ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
[outages] Windstream voice issues?
We had a few reports of not being able to dial out but not all outcalls seemed to be affected and we were receiving calls. WS said it was a nation-wide issue that was getting extreme priority. Things got back to normal by about 11am EST. Keeping an eye on it, though, since the tech also mentioned that they were still getting reports that indicated it was sporadic and may intermittently still affect some customers. Brian Kovats, IT Technician ___ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
[outages] unsub test
test ___ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Re: [outages] unsubscribe
Looks like the list web interface is down and the usual mailman LISTNAME-leave unsub method isn't working either. Perhaps a benevolent admin could take care of your unsub request? Regards, SG On 11/17/2014 11:39 AM, Ronnie Montgomery via Outages wrote: unsubscribe ___ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages ___ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Re: [outages] unsubscribe
List-Id: Outages \(planned unplanned\) Reporting. outages.outages.org List-Unsubscribe: https://puck.nether.net/mailman/options/outages, mailto:outages-requ...@outages.org?subject=unsubscribe Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Mon, Nov 17, 2014 at 1:39 PM, Ronnie Montgomery via Outages outages@outages.org wrote: unsubscribe ___ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages ___ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Re: [outages] unsubscribe
Or use the correct email address =) Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Mon, Nov 17, 2014 at 2:13 PM, Spencer Gaw via Outages outages@outages.org wrote: Looks like the list web interface is down and the usual mailman LISTNAME-leave unsub method isn't working either. Perhaps a benevolent admin could take care of your unsub request? Regards, SG On 11/17/2014 11:39 AM, Ronnie Montgomery via Outages wrote: unsubscribe ___ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages ___ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages ___ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Re: [outages] Level3 LAX latency - backhoe fever?
nothing on my l3 status board that I have access to . *Luke Rockwell* Systems Administrator Information Technology . On Mon, Nov 17, 2014 at 12:22 PM, Andrew Losey via Outages outages@outages.org wrote: Howdy, Seeing some heavy latency once I hit Level3’s LAX edge - anyone else experiencing latency out in LA? traceroute to xxx.x.com (xx.xx.xx.xx), 30 hops max, 60 byte packets 1 xxx.xxx.local.xx.xx.in-addr.arpa (xx.xx.xx.xx) 0.395 ms 0.379 ms 0.324 ms 2 xe-8-2-2.edge2.Washington4.Level3.net (4.53.114.221) 0.652 ms 0.694 ms 0.691 ms 3 * * * 4 ae-2-70.edge3.LosAngeles1.Level3.net (4.69.144.73) 107.206 ms ae-3-80.edge3.LosAngeles1.Level3.net (4.69.144.137) 108.328 ms 109.351 ms 5 .edge3.LosAngeles1.Level3.net (xx.xx.xx.xx) 94.529 ms 94.589 ms 91.664 ms 6 ..com (xx.xx.xx.xx) 66.823 ms 77.933 ms 76.571 ms ___ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages ___ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Re: [outages] Level3 LAX latency - backhoe fever?
Seeing about the same latency out of the Chicago suburbs. From: Luke Rockwell via Outages outages@outages.org To: Andrew Losey and...@addthis.com Cc: outages outages@outages.org Sent: Monday, November 17, 2014 2:26:38 PM Subject: Re: [outages] Level3 LAX latency - backhoe fever? nothing on my l3 status board that I have access to . Luke Rockwell Systems Administrator Information Technology . On Mon, Nov 17, 2014 at 12:22 PM, Andrew Losey via Outages outages@outages.org wrote: Howdy, Seeing some heavy latency once I hit Level3’s LAX edge - anyone else experiencing latency out in LA? traceroute to xxx.x.com (xx.xx.xx.xx), 30 hops max, 60 byte packets 1 xxx.xxx.local.xx.xx.in-addr.arpa (xx.xx.xx.xx) 0.395 ms 0.379 ms 0.324 ms 2 xe-8-2-2.edge2.Washington4.Level3.net (4.53.114.221) 0.652 ms 0.694 ms 0.691 ms 3 * * * 4 ae-2-70.edge3.LosAngeles1.Level3.net (4.69.144.73) 107.206 ms ae-3-80.edge3.LosAngeles1.Level3.net (4.69.144.137) 108.328 ms 109.351 ms 5 .edge3.LosAngeles1.Level3.net (xx.xx.xx.xx) 94.529 ms 94.589 ms 91.664 ms 6 ..com (xx.xx.xx.xx) 66.823 ms 77.933 ms 76.571 ms ___ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages ___ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages ___ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Re: [outages] Level3 LAX latency - backhoe fever?
just had a chance to catch up on this email, i had a ticket open between LAX and VA, that had problems. their response was and i quote Called customer and spoke with *. I let him know that our Core engineers found that there was a backbone transport issue between DC and LAX that was causing traffic to shift onto a backup path which got saturated as we started hitting peak usage times. That trouble has now cleared and the main backbone link is now up. We will hold this ticket for 24 hours. If you have any further trouble, let us know and we will look back into the issue. hope that helps others :) On Mon, Nov 17, 2014 at 12:22 PM, Andrew Losey via Outages outages@outages.org wrote: Howdy, Seeing some heavy latency once I hit Level3’s LAX edge - anyone else experiencing latency out in LA? traceroute to xxx.x.com (xx.xx.xx.xx), 30 hops max, 60 byte packets 1 xxx.xxx.local.xx.xx.in-addr.arpa (xx.xx.xx.xx) 0.395 ms 0.379 ms 0.324 ms 2 xe-8-2-2.edge2.Washington4.Level3.net (4.53.114.221) 0.652 ms 0.694 ms 0.691 ms 3 * * * 4 ae-2-70.edge3.LosAngeles1.Level3.net (4.69.144.73) 107.206 ms ae-3-80.edge3.LosAngeles1.Level3.net (4.69.144.137) 108.328 ms 109.351 ms 5 .edge3.LosAngeles1.Level3.net (xx.xx.xx.xx) 94.529 ms 94.589 ms 91.664 ms 6 ..com (xx.xx.xx.xx) 66.823 ms 77.933 ms 76.571 ms ___ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages ___ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
