Network Alerts

Click here to learn how to subscribe to Network Alerts
We are continuing to track down an issue with calls that are forwarded to Junction Networks DIDs (phone numbers) from outside carriers. We have escalated the issue with our carrier and will continue to update with the progress. Outbound calls are unaffected. Direct inbound calls to Junction Network's DIDs are unaffected.
We are currently tracking down an issue with calls that are forwarded to Junction Networks DIDs (phone numbers) from outside carriers. We have escalated the issue with our carrier and will continue to update with the progress. Outbound calls are unaffected. Direct inbound calls to Junction Network's DIDs are unaffected.

There is a large Global Crossing (GLBX) outage in New York. It is affecting all customers coming to Junction Networks via the GLBX network. We are attempting to re-route traffic, but the issue is inside their network. They are still advertising routes to Junction Networks (and others) but not routing the traffic. We have escalated the issue with GLBX.

We are currently experiencing one-way audio on all inbound phone calls. Outbound calls are unaffected. We are currently tracking the issue.

The upgrades are going well and we expect to be done around 2pm EST. Thank you for your consideration.

We are currently doing some network upgrades to add additional capacity to our core routers. While we don't expect any issues with 99% of calls during this period, it is possible that some customers may experience short term interruptions to some in progress calls. Thanks for your consideration.

Starting at around 7:20pm EST and continuing until around 8:13pm EST, routes from Junction Networks to the Global Crossing networks were corrupted. No traffic was able to reach Junction Networks from anywhere on the Global Crossing network. All inbound and outbound traffic would have been affected. Unable to repair the situation, the Global Crossing network peer was disabled forcing all traffic around the issue. Service was fully restored at 8:13pm.

One an unrelated note, Junction Networks will be performing a network upgrade from 9am until Noon on Saturday, April 12th. We do not expect any customer affecting service interruptions from this operation.

Starting this morning, a subset of New York state phone numbers, area codes (212, 718, 845), were not completing when called from withing New York state. Only some numbers were affected. Outbound calling was unaffected. When the calls were not completing, they were not hitting the Junction Networks switch. We immediately opened a ticket with our inbound carrier. Around 11:45am EST, the issue was resolved.

We received the following analysis from our carrier:
"Early this morning a peering customer's switching fabric went offline from a
failed maintenance window. We then began to see flooding into the SS7
network with critical errors flooding our SS7 links. They were unable to
resolve and put our network into a level 3 congestion state. At the same
time our major inbound carrier had a major outage as well which limited
their ability to assist in restoration causing them to continue to stream
RSC messages. This caused an unhappy state between our LSG and LNC and STP.
Our switch vendor continues to review root cause. We have all executive
levels working the issues with providers and vendors at this time and are
systemically treating each circuit level issue trying to process the most
calls possible at this time. The impact is not entire but partial."

There appears to be a capacity issue on our carrier's NYC switch. Only about 25% of the inbound calls to NY area codes (718, 212 and 845) are hitting the Junction Networks switch. We have a ticket open with our carrier and will update shortly.

We will post status messages in our Network Alert blog. You can access our Network Alerts blog by clicking on "system status" from your log in page. Only inbound calls to some New York phone numbers are affected. Outbound calls are unaffected.

There was an issue with one of our our outbound providers today from approximately 11:32am until around 11:40am EST. This outage would have affected the majority of outbound calls. That issue has been resolved by removing that carrier from the outbound routing table.
Inbound calls were unaffected.

We apologize for the inconvenience.

Syndicate content