Resolved incidents
NYC gateway — emergency event
February 23rd, 2017
On January 23rd, at 11:50 EDT (US East), the sip-NYC session border controller became unreachable due to Internap's network failure in the LGA11 facility (75 Broad Street, NYC). We apologize strongly for the inconvenience caused by the service interruption. Internap has declared an emergency over this network breakdown and their engineering team is putting in their maximum best effort to correct routing. We have not had a serious issue in NY for couple of years now.
February 23rd, 2017
On January 23rd, at 11:50 EDT (US East), the sip-NYC session border controller became unreachable due to Internap's network failure in the LGA11 facility (75 Broad Street, NYC). We apologize strongly for the inconvenience caused by the service interruption. Internap has declared an emergency over this network breakdown and their engineering team is putting in their maximum best effort to correct routing. We have not had a serious issue in NY for couple of years now.
Emergency event at the Cape Town facility
February 17th, 2017
On February 17th, at 18:45 GMT+2 (South Africa time), the sip-ZA session border controller became unreachable due to MTN's network failure in the the facility. We apologize strongly for the inconvenience caused by the service interruption.
February 17th, 2017
On February 17th, at 18:45 GMT+2 (South Africa time), the sip-ZA session border controller became unreachable due to MTN's network failure in the the facility. We apologize strongly for the inconvenience caused by the service interruption.
NYC gateway — issue resolved
January 23rd, 2017
The facility provider has corrected the routing errors caused by a fiber cut. The network is coming back as we speak. We apologize strongly for the inconvenience caused by the service interruption. Our US team will have a meeting later in the day for post-incident analysis. We hope that we have been prompt and efficient, apologies again for the facility issues.
January 23rd, 2017
The facility provider has corrected the routing errors caused by a fiber cut. The network is coming back as we speak. We apologize strongly for the inconvenience caused by the service interruption. Our US team will have a meeting later in the day for post-incident analysis. We hope that we have been prompt and efficient, apologies again for the facility issues.