From approximately 5:49 pm to 8:33 pm EST on Wednesday, September 4, 2013, inbound calls to phone numbers (DIDs) in the following area codes were not completing for OnSIP Hosted customers:
Network Alert History
Start: 2013.09.04 5:49 pm EST
End: 2013.09.04 8:33 pm EST
Start: 2013.05.12 2:00 am EDT
End: 2013.05.12 3:50 am EDT
In order to implement a vital upgrade to the firmware of our switching infrastructure, a planned switch maintenance at our NYC data center occurred. The maintenance began at 2:00am EDT, with full service restored at around 3:50am EDT. During the maintenance window, some service may have seen...
Start: 2013.05.11 2:00 am EDT
End: 2013.05.11 5:00 am EDT
In an attempt to implement a vital upgrade to the firmware of our switching infrastructure, a planned switch maintenance will occur tonight starting at 2:00am EDT in our NYC data center. At some point over the following three hours the admin portal will not be available. Any unavailability...
Start: 2013.02.20 11:50 am Eastern
End: 2013.02.20 1:06 pm Eastern
11:50 am EST We are aware that some customers are experiencing choppy audio. We are currently investigating the issue, but we do not believe it is on the OnSIP network at this time. We will post updates here.
12:15 pm EST Update: We have discovered the...
Start: 2012.11.08 11:15 am Eastern
End: 2012.11.08 1:15 pm Eastern
From approximately 11:15 a.m. until 1:15 p.m. eastern time, some inbound calls to auto-attendants and a small percentage of outbound calls were failing. This was tracked down to a faulty piece of equipment, which has been removed from call routing.
Start: 2012.11.02 7:45 pm EST
End: 2012.11.03 2:00 am EST
7:45 pm EST We are aware of the issue with an upstream carrier affecting some phone numbers. The carrier is no longer sending us calls. We are contacting the carrier and will post updates here. We apologize for this service interruption.
8:07 pm EST The...
Start: 2012.07.23 8:10 PM ET
End: 2012.07.23 8:45 PM ET
An issue has been detected on a subset of phone numbers on one of our carriers. Inbound phone calls to those numbers are currently not completing.
Start: 2012.03.06 9:30 AM ET
End: 2012.03.06 12:15 PM ET
At approximately 9:30 AM, a few customers began reporting they were not receiving all of their inbound calls. After testing and further reports from customers, we diagnosed the problem to be that one of our upstream carriers has a few servers with slow response times. This caused service...
Start: 2012.02.08 6:16 PM ET
End: 2012.02.08 8:10 PM ET
On February 8, 2012 at approximately 6:16 PM ET, all OnSIP services except SIP to SIP calling became unavailable. Our Engineering staff was dispatched to our NYC datacenter and identified the problem to be a hardware failure. More specifically, a switch failed and caused critical services to...
Start: 2011.10.31 9:00 PM ET
End: 2011.11.01 5:36 PM ET
From 9 PM ET on 10/31/11 to 5:36 PM ET on 11/01/11, roughly one third of our inbound local numbers were not accessible due to an issue between 2 upstream carriers' systems. Outbound calling was unaffected.
Start: 2011.08.08 3:59 PM ET
End: 2011.08.08 4:28 PM ET
At 3:59 PM ET, we began experiencing an issue with some of our inbound phone numbers. We escalated the issue with the affected upstream carrier. Outbound service was unaffected. At 4:28 PM ET, we reported the issue had been addressed by the carrier and all services were restored.
Start: 2011.07.25 9:29 AM ET
End: 2011.07.25 10:15 AM ET
At 9:29 AM ET, we began tracking reports of service degradation wherein inbound calls were failing. We believed it be an issue with an inbound carrier and contacted their Network Operations Center to advise them of the issue. At 10:10 AM ET, we reported about two dozen inbound phone numbers were...
Start: 2011.06.28 9:00 AM ET
End: 2011.06.28 9:45 AM ET
At approximately 9:00 AM ET, we began tracking a service interruption wherein customers who appeared to be registered were not able to receive calls. This was due to an issue in one of our SIP proxies and thereby affected a portion of registrations. The issue was resolved at 9:45 AM ET.
Start: 2011.05.31 1:10 PM ET
End: 2011.05.31 1:40 PM ET
Some OnSIP customers experienced a loss of service on Tuesday 5/31/11 from approximately 1:10 pm until approximately 1:40pm. This loss of service included the inability to initiate an outbound call or to properly answer an inbound call. It was soon determined that the service interruption was...
Start: 2011.05.27 10:45 AM ET
End: 2011.05.27 12:30 PM ET
At 10:45 AM ET, we began tracking a network issue in our NYC data center that affected about 25% of customers.
At 11:15 AM, we diagnosed the problem within the NYC data center: One of the BGP peers that connects to one of our proxies was flapping, resulting in unreliable data...
Start: 2011.04.15 2:40 PM ET
End: 2011.04.15 2:43 PM ET
Between the times of 2:40 PM ET and 2:43 PM ET, customers may have experienced service degradation. This issue was resolved by 2:43 ET.
Start: 2011.01.11 7:47 PM ET
End: 2011.01.11 8:50 PM ET
The server sip.onsip.com is currently under heavy load. There is a device on the Internet sending us thousands of bad packets per second which is filling the error logs and bogging down the server.
We are attempting to isolate that traffic and allow the server to return to normal....
Start: 2010.12.04 1:00 AM ET
End: 2010.12.04 7:00 AM ET
Between the hours of 1:00 and 7:00 A.M. EST on Saturday, December 4th, Junction Networks will be performing necessary maintenance. During this maintenance window, there is an expected service interruption wherein OnSIP and PSTN Gateway customers will be unable to send or receive calls. This...
Start: 2010.11.22 3:10 AM ET
End: 2010.11.22 4:30 AM ET
Junction Networks is currently tracking an issue where no traffic is able to be routed to any Junction Networks domain. No phones are able to register and no calls are possible either in or out of the system. Engineers have been dispatched.
Start: 2010.11.16 10:58 PM ET
End: 2010.11.17 12:04 AM ET
We are currently working on an issue with a handful of inbound numbers where either the call lasts for only 20 seconds or the call is never setup in the first place. The issue is with our upstream carrier and they have escalated the issue internally. We will post updates in the comments.