Us too.
>From WS: Greetings, In regards to ticket 202297, the issue for calls
failing in the New Orleans area, looks to be resolved. Please retest, and
inform us of your test results. We will continue to monitor this ticket for
any further issues. Thanks
On Mar 3, 2017 5:33 PM, "Ryan Collins"
Starting to get successful termination on some of my calls now.
> On Mar 3, 2017, at 5:03 PM, Aubrey Wells wrote:
>
> About 10 minutes after you posted that, this showed up on the master ticket:
>
> 16:59 EST: Windstream repair and operations teams along with local field
About 10 minutes after you posted that, this showed up on the master ticket:
16:59 EST: Windstream repair and operations teams along with local field
operations and vendor support, continue working to repair the network
impairment. No additional information can be provided at this time as far
as
I just got a call from Windstream (from this post), they are restoring a
backup and expect services to be restored within 15-20min.
WILFORD MONDE
407 447-4164 -
WINDSTREAM COMMUNICATION
--
*Doug Roberts*
d...@dougr.com
251-308-4040 (Mobile)
228-254-3035 (Biloxi)
Not really.
4p EST: Greetings: Techs are actively working to resolve the cause of the
impairment. We will have another update within the next hour. Thank You
---
Aubrey Wells
Packethead Consulting, LLC
Helping you get your bits
Any more updates from Windstream on this? We’ve got about 750 DIDs through a
telco broker that are affected. I don’t have direct access to the ticket but it
seems we’re well past the 30-60 min ETR window.
From: Aubrey Wells via Outages
Sent: Friday, March 3, 2017 15:11
To: Doug Roberts
Cc:
They've found the issue and expect it to be fixed in the next 30-60 min.
This is from just before 3p EST.
Techs have found the root cause of the issue and are currently working to
resolve it. This should take 30 minutes to 1 hour. We hope to have further
updates shortly. Thank you
"Issue affecting inbound calls to Windstream DIDs in the New Orleans, LA
area. We have received reports of affected DIDs in LATA 490. Calling
parties may experience busy signals or operator intercept messages at this
time."
--
*Doug Roberts*
d...@dougr.com
251-308-4040 (Mobile)
228-254-3035
> *To:* Ryan Prihoda <rprih...@dynaconnections.com>
> > > *Cc:* outages@outages.org
> > > *Subject:* Re: [outages] Amazon S3 down
> > >
> > >
> > >
> > > Same here. We were more or less back up about 2 hours ago.
> > >
> > >
> > >
> > > On 1 Mar 2
osts about "me too", "me too", "me too"?
>
>
> -Jim P.
> ___
> Outages-discussion mailing list
> Outages-discussion@outages.org
> https://puck.nether.net/mailman/listinfo/outages-discussion
>
--
RFO: https://aws.amazon.com/message/41926/
On Wed, Mar 1, 2017 at 11:44 AM, Chapman, Brad (NBCUniversal) via Outages <
outages@outages.org> wrote:
> Well, that makes **two** post-mortems I look forward to reading about
> this month: the Oscar night best picture kerfuffle, and now this Amazon
>
11 matches
Mail list logo