<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0"><channel><atom:link rel="hub" href="http://tumblr.superfeedr.com/" xmlns:atom="http://www.w3.org/2005/Atom"/><description>Updates on the condition of and changes to the Teliax network.</description><title>Teliax Status</title><generator>Tumblr (3.0; @teliax)</generator><link>http://status.teliax.com/</link><item><title>Note: help.teliax.com replaces status.teliax.com</title><description>&lt;p&gt;As we have a different ticketing system, we can now provide better updates through our system at help.teliax.com. This status page (at status.teliax.com) will no longer be updated and will eventually be redirected to help.teliax.com.&lt;/p&gt;</description><link>http://status.teliax.com/post/534273667</link><guid>http://status.teliax.com/post/534273667</guid><pubDate>Mon, 19 Apr 2010 17:00:23 -0600</pubDate></item><item><title>Resolved: Trouble: Toll-Free Termination - Mesg/OptIcpt</title><description>&lt;p&gt;The routing issue regarding toll-free termination has been resolved. We apologize for any trouble this may have caused.&lt;/p&gt;</description><link>http://status.teliax.com/post/465834780</link><guid>http://status.teliax.com/post/465834780</guid><pubDate>Mon, 22 Mar 2010 10:01:03 -0600</pubDate></item><item><title>Trouble: Toll-Free Termination - Mesg/OptIcpt</title><description>&lt;p&gt;We are experiencing routing trouble with toll-free termination. We are working to resolve this issue as quickly as possible. Users attempting to dial a toll-free number will receive a message/operator intercept and the call will not connect.&lt;/p&gt;</description><link>http://status.teliax.com/post/465692566</link><guid>http://status.teliax.com/post/465692566</guid><pubDate>Mon, 22 Mar 2010 08:20:37 -0600</pubDate></item><item><title>Call Routing Issue Resolved</title><description>&lt;p&gt;The call routing issue that we experienced earlier today has been resolved.  Thank you for your patience.&lt;/p&gt;</description><link>http://status.teliax.com/post/454813239</link><guid>http://status.teliax.com/post/454813239</guid><pubDate>Wed, 17 Mar 2010 12:11:54 -0600</pubDate></item><item><title>Call Routing Issue</title><description>&lt;p&gt;We are currently experiencing issues with routing of inbound and outbound calls.  The problem has been escalated and we are working to resolve it as quickly as possible.&lt;/p&gt;</description><link>http://status.teliax.com/post/454743940</link><guid>http://status.teliax.com/post/454743940</guid><pubDate>Wed, 17 Mar 2010 11:22:39 -0600</pubDate></item><item><title>Update: DEN Proxy Outage</title><description>&lt;p&gt;The DEN proxy is now operational. We sincerely apologize for the downtime. If you switched to a different proxy, please make sure you switch both your physical device and the Proxy on the Dashboard. We are working to prevent this type of outage in the future.&lt;/p&gt;</description><link>http://status.teliax.com/post/452703223</link><guid>http://status.teliax.com/post/452703223</guid><pubDate>Tue, 16 Mar 2010 13:16:35 -0600</pubDate></item><item><title>Den.teliax.net Proxy outage</title><description>&lt;p&gt;We are experiencing difficulties on the Denver 2.0 proxy.  If you are having any trouble, please register your device to atl.teliax.net, nyc.teliax.net, or lax.teliax.net. We are diligently working to resolve the issue and will update this status page periodically. Thank you for your patience.&lt;/p&gt;</description><link>http://status.teliax.com/post/452640125</link><guid>http://status.teliax.com/post/452640125</guid><pubDate>Tue, 16 Mar 2010 12:34:58 -0600</pubDate></item><item><title>Resolved: Trouble: Dallas Area Inbound - Recording/OpIcpt</title><description>&lt;p&gt;Service to DIDs in the Dallas/Fort Worth area has been restored.&lt;/p&gt;</description><link>http://status.teliax.com/post/394034100</link><guid>http://status.teliax.com/post/394034100</guid><pubDate>Tue, 16 Feb 2010 21:10:36 -0700</pubDate></item><item><title>Trouble: Dallas Area Inbound - Recording/OpIcpt</title><description>&lt;p&gt;This is unconfirmed from our carrier, however several Dallas-area DIDs are not being handed off to our network. Customers may hear a recording or operator intercept (three tones and message) instead of a completed call. We have opened a ticket with our origination provider in this area and will post status updates as we have them.&lt;/p&gt;</description><link>http://status.teliax.com/post/393560342</link><guid>http://status.teliax.com/post/393560342</guid><pubDate>Tue, 16 Feb 2010 16:43:00 -0700</pubDate></item><item><title>General Status</title><description>&lt;p&gt;All systems are currently 100% operational. The trouble seen late Thursday was resolved as of Thursday evening.&lt;/p&gt;</description><link>http://status.teliax.com/post/391277645</link><guid>http://status.teliax.com/post/391277645</guid><pubDate>Mon, 15 Feb 2010 13:06:45 -0700</pubDate></item><item><title>Update: Trouble: Network Outage</title><description>&lt;p&gt;All inbound/outbound on Dashboard is working at this time, we are working on the Legacy proxies now. ETR less than 15 minutes.&lt;/p&gt;</description><link>http://status.teliax.com/post/384492461</link><guid>http://status.teliax.com/post/384492461</guid><pubDate>Thu, 11 Feb 2010 16:36:11 -0700</pubDate></item><item><title>Trouble: Network Outage</title><description>&lt;p&gt;We are currently experiencing a partial network outage on Legacy proxies and some Dashboard proxies. We are working to resolve this as quickly as possible.&lt;/p&gt;</description><link>http://status.teliax.com/post/384405725</link><guid>http://status.teliax.com/post/384405725</guid><pubDate>Thu, 11 Feb 2010 15:35:04 -0700</pubDate></item><item><title>Resolved: Trouble: DEN Proxy</title><description>&lt;p&gt;As of 0730MST, all services on the DEN proxy have been restored. We sincerely apologize for any inconvenience this may have caused.&lt;/p&gt;</description><link>http://status.teliax.com/post/381991157</link><guid>http://status.teliax.com/post/381991157</guid><pubDate>Wed, 10 Feb 2010 09:21:49 -0700</pubDate></item><item><title>Trouble: DEN.net Proxy</title><description>&lt;p&gt;We are currently experiencing trouble with the den.teliax.net proxy. Calls routed to and from this proxy will not connect. We are working to resolve the trouble as quickly as possible but currently have no ETR. Please use one of the other 3 proxies in the meantime and check back for updates.&lt;/p&gt;

&lt;p&gt;We appreciate your patience as we work to resolve this issue.&lt;/p&gt;</description><link>http://status.teliax.com/post/381769936</link><guid>http://status.teliax.com/post/381769936</guid><pubDate>Wed, 10 Feb 2010 06:13:06 -0700</pubDate></item><item><title>RESOLVED Trouble: Busies/OpIcpt in ATL market</title><description>&lt;p&gt;Start Date/Time: 1/19/2010 14:00 GMT &lt;br/&gt;End Date/Time: 1/20/2010 21:30 GMT&lt;/p&gt;
&lt;p&gt;Impact Area: Atlanta, GA Market&lt;/p&gt;
&lt;p&gt;Summary:  Inbound carrier experienced capacity in the Atlanta market &lt;br/&gt;Additional overflow was ordered and &lt;br/&gt;implemented to provide extra capacity. Provider will continue to monitor &lt;br/&gt;the traffic.&lt;/p&gt;</description><link>http://status.teliax.com/post/344977985</link><guid>http://status.teliax.com/post/344977985</guid><pubDate>Wed, 20 Jan 2010 16:40:22 -0700</pubDate></item><item><title>CONT Trouble: Busies/OpIcpt in ATL market</title><description>&lt;p&gt;Start Date/Time: 1/19/2010 14:00 GMT &lt;br/&gt;End Date/Time: Ongoing&lt;/p&gt;
&lt;p&gt;Symptom: Busy signal, Operator recording&lt;/p&gt;
&lt;p&gt;Impact Area: Atlanta, GA Market&lt;/p&gt;
&lt;p&gt;Estimated repair time: N/A&lt;/p&gt;
&lt;p&gt;Summary: One of our inbound carriers is currently experiencing &lt;br/&gt;blocking/capacity in the Atlanta market for certain DIDs.&lt;br/&gt;Customer may experience busies or an operator intercept message. They are currently working to get overflow in place. We currently have no ETR.&lt;/p&gt;</description><link>http://status.teliax.com/post/344901166</link><guid>http://status.teliax.com/post/344901166</guid><pubDate>Wed, 20 Jan 2010 15:45:21 -0700</pubDate></item><item><title>Trouble: Busies/OpIcpt in ATL market</title><description>&lt;p&gt;Start Date/Time: 1/19/2010 14:00 GMT &lt;br/&gt;End Date/Time: Ongoing&lt;/p&gt;
&lt;p&gt;Symptom: Busy signal&lt;/p&gt;
&lt;p&gt;Impact Area: Atlanta Market&lt;/p&gt;
&lt;p&gt;Summary: One of our termination providers is currently experiencing blocking in the Atlanta Market.&lt;br/&gt;Reports of Busies or Operator Intercept message.&lt;/p&gt;</description><link>http://status.teliax.com/post/343221392</link><guid>http://status.teliax.com/post/343221392</guid><pubDate>Tue, 19 Jan 2010 15:17:35 -0700</pubDate></item><item><title>New LNP Helpdesk Hours</title><description>&lt;p&gt;Starting Monday, January 18th, the LNP helpdesk hours will be from 1pm to 6pm, Monday through Thursday, Mountain Standard Time.&lt;/p&gt;
&lt;p&gt;New LNP requests can still be sent to ports@teliax.com and will be processed within 24 hours. The Teliax Support Team hours will not change (6a-6p, M-F, MST) and the Support Team will be able to answer basic questions including status updates.&lt;/p&gt;
&lt;p&gt;Please contact support@teliax.com with any questions.&lt;/p&gt;</description><link>http://status.teliax.com/post/320073861</link><guid>http://status.teliax.com/post/320073861</guid><pubDate>Wed, 06 Jan 2010 11:00:57 -0700</pubDate></item><item><title>Teliax Holiday Schedule</title><description>&lt;p&gt;The Teliax offices will be closed on the following days:&lt;/p&gt;

&lt;p&gt;Thursday, December 24th, 2009&lt;/p&gt;
&lt;p&gt;Friday, December 25th, 2009&lt;/p&gt;
&lt;p&gt;Friday, January 1st, 2010&lt;/p&gt;

&lt;p&gt;Please send all support requests to support@teliax.com, and enjoy your holidays.&lt;/p&gt;</description><link>http://status.teliax.com/post/295218588</link><guid>http://status.teliax.com/post/295218588</guid><pubDate>Tue, 22 Dec 2009 09:19:49 -0700</pubDate></item><item><title>Resolved: Trouble: Inbound DIDs in SE US</title><description>&lt;p&gt;The trouble affecting some DIDs in the southeast US has been resolved at this time. No further impact is expected. We apologize for any inconvenience this may have caused you.&lt;/p&gt;</description><link>http://status.teliax.com/post/288119656</link><guid>http://status.teliax.com/post/288119656</guid><pubDate>Thu, 17 Dec 2009 17:20:05 -0700</pubDate></item></channel></rss>

