VoicePulse outage Nov 6, 2015
-
woot! first in line!
-
Yeah we are also considered Legacy as well. We have been with them for YEARS!!!
-
@Minion-Queen said:
Yeah we are also considered Legacy as well. We have been with them for YEARS!!!
Ten!
-
From VP: "We have an upstream provider that is currently experiencing issue where calls are not reaching our network.
We have an escalated trouble ticket open with them to get this issue resolved.
As soon as we have more information, we will provide you updates as we get them." -
My ticket officially opened with them also.
This issue last occurred on September 18, 2015. The outage was reported to me by a user @ 07:30 CDT. I spent an hour attempting to find a local problem because inbound calls were actually being half ass delivered.
I reported it to VoicePulse by 08:30 and the issue was resolved by 09:30.
-
This just in from VP:
We have just received an estimated time of repair of 30 minutes.
-
Same here just got it.
-
Just recieved:
Hello,
We deeply apologize for the inconvenience of this recent outage.
As of 3:15 PM, our upstream provider has been able to resolve their issue and restored inbound traffic to our network.
If you experience any residual issues that seem out of the ordinary, please reply directly to this email so we can immediately investigate this issue. -
Calls have been flowing here again.
-
I posted this at 13:42 CST. Calls were restored to my knowledge by 14:30 CST when I received the email from VoicePulse. Prior to that I had our trunks offline. I will go check the PBX logs and see if any calls came into the failover number.
-
Looks like calls were going to the failover starting at 14:11 CST. But the first two never completed correctly.
The first valid failover call was 14:13:51
-
And it looks like the last valid call I had on the VoicePulse trunk was 12:14 CST
So that is a 2 hour outage in my book.
-
We have to look but we thought it was awful quiet (but Friday afternoons can be around here). Last call we got was at 1:08pm est today until
