bandwidth.com outage

Bandwidth.com had an outage last night, from around 4:10pm central to around 6:30 central. It affected all of their SIP trunks. Interesting! Apparently, it was attributed to a Level3 outage, but it doesn’t appear that other VoIP trunks with other L3 resellers went down. We’ll see…

Agreed, very interesting. We are one of the bandwidth.com customers that experienced the service interruption…we have been told that the “cause of the disruption is known”, but no details as to what that cause was.

All I can say is I hope that they can show how the issue was fixed. At least this is the first outage I’ve had with them, it was reasonably close to end-of-business, it was short, and it was well-communicated.. but still.

We are in nYC and didn’t suffer thriugh that outage. We are living through an outage today (12/11). It started around noon and it’s 2:45PM.We received an email that they have identified the source of the outage. But we’re still down!!

Our inbound and outbound outage lasted approximately 90 minutes. We continue to have no inbound calling to our system and we are going on 120 minutes. Request for an explanation or an estimate of complete restoration of our service have not been provided.

I have always used the primary gateway. Per your suggestion I contacted themm regarding the secondary gateway and was informed that the secondary gateway was just “recently” able to handle both inbound and outbound, but the primary gateway was still having problems with inbound. I added the secondary and both inbound and outbound began working. Thanks for your last reply/suggestion. I hope they will be providing an explanation of what has happened this week. I have been a customer for 18 months, never had outages before.

Glad to hear you’re back up! I’ve always been under the impression that both primary and secondary gateways are configured to handle both in+out.. interesting that they told you otherwise.

I am also looking forward to an explanation; hopefully it will be publicly-scoped versus proprietary customer-eyes-only data. I’ve been a customer for over 3 years now; the original blog post that we are commented on right now was the only real outage I’ve had with them besides this one. If the issue had not recurred, I would not call this one ‘major’.. but since it repeated itself, gah! :)

Thanks for encouraging the discussion and I know that we’ve talked before about features, issues and other Bandwidth related things. :)

Unfortunately, at times issues do arise and we’re trying to approach this in several different ways.

We’ve started to use outlets like Twitter, Facebook, Uservoice and our blog to encourage a more open and engaging communication style. This does take time to fully implement and we will continue to improve. We are working internally to involve more departments and better communicate when we release new features, encounter problems and overcome any issues that do come up.

Most importantly, we appreciate feedback and discussion and use those conversations to help guide our actions. Thank you for your patience and for taking the time to share your expertise with others.

We will continue to do everything we can to improve our reliability, functionality, ease of use and effective communication to customers.