« network status »
Look here first before reporting problems. We will do our best to clearly communicate current network status events at this location as they occur.
Network News- 5:51am
Successful test of rewired circuit. All services online. - 2014-10-31 2:27am
AT&T is on-site. - 11:57pm
AT&T tech has been dispatched to CO. - 10:05pm
AT&T tech is en route to our location. - 8:39pm
AT&T is still in process of circuit redesign. - 7:48pm
AT&T is still in process of circuit redesign. - 6:29pm
AT&T is conducting tests from CO. - 5:06pm
AT&T is now "redesigning the circuit" -- moving us to a completely separate connection. - 4:24pm
We are seeing sporadic up/down events on the network. Among our techs and partners who collectively represent many decades of experience we all agree this is one of the longest downtime events experienced with a high-quality network circuit. Most sincere apologies to affected customers. We continue to work with AT&T and our upstream provider to resolve this situation. - 2:35pm
Once again the circuit is down *sigh*. - 2:15pm
Circuit is back online. We are waiting for a Reason For Outage report from upstream and will report here once received. Separately, our network management team is working on a plan to further expand our network redundancy with aim to prevent these types of outages in the future. - 1:40pm
Again we are hearing there is a problem with AT&T in their CO. We are waiting on a report back as their techs diagnose the issue. - 1:21pm
Network is sporadically hopping up and down. - 2014-10-30 12:34pm
Suddenly experiencing upstream network problems again. All hands on deck. :/ - 3:45pm
Word is that AT&T found a bad physical cable in their CO. It has been fixed and we are back online. No network errors reported at this time. - 12:01pm
Together with upstream provider double-check all possible points of failure at Burly House. All tests clear. AT&T being called out again. - 10:37am
After further testing still unable to identify the root cause. Both AT&T and upstream provider continuing to work on the problem. - 2014-10-28 5:45am
Continued problems - AT&T back en route. - 9:30pm
AT&T has found a fault in their network and is investigating further. At the moment we are online. - 7:06pm
AT&T local loop testing appears good; isolating possible fault upstream. - 6:10pm
AT&T testing/analysis continues. - 5:34pm
Link has gone done again. - 5:17pm
Network is back online. We are continuing to investigate the cause and will be monitoring closely for the next 48 hours. - 3:45pm
AT&T is on site and investigating. - 3:20pm
AT&T is en route to assess the local loop. - 2:35pm
Continued testing from our primary upstream provider. Multiple loopback tests have been performed and the circuit is still not functional. - 12:21pm
Continued testing from our primary upstream provider. - 2014-10-27 11:19am
Failed upstream network link; techs are on-site and working to remedy the situation as quickly as possible. We are grateful for your patience.
Historical log of past events which occurred in 2012:
- 2012 - October
- Our shared hosting server Gaia experienced a major hardware failure. The root cause was bad/failed capacitor in the power supply. All customers moved to new server Surya.
Historical log of past events which occurred in 2009:
- 2009 - July 22nd
- The failed UPS has been replaced.
- 2009 - July 20-21st
- We are experiencing some troubles with one of the primary backup UPS system, which has caused a few short periods of downtime due to loss of power. Tech staff is working through the problem, and will be installing a new UPS power system to replace the failing unit.
- 2009 - Sunday, January 18th
- T1 maintenance scheduled. Interruption of service may be possible but not expected. Some reduced network performance may occur during this period.
Log of past events which occurred in 2008:
- 2008- Wednesday, July 16th
- Several software upgrades applied to Gaia. No downtime, but some services may have degraded for short periods while the work was in progress.
Log of past events which occurred in 2007:
- 2007- November 20th
- We lost t1 connectivity due to link failure. All services were affected while techs were called in to swap the line to a different circuit. All services back online after one hour (11:25am-12:35pm).
- 2007- October 16th
- Webmail was offline for a period due to connectivity problems with the secure server. This problem has been fixed.(reported 8:20pm, Oct. 16th 2007; resolved 3:38pm Oct. 17th 2007)
- 2007- May 22nd
- A t1 service outage caused our network to go offline from 10am-2pm CST. The cause was due to a hardware failure with one of our upstream providers.
Log of past events which occurred in 2006:
- 2006- Jan. 4th
- Scheduled maintenance on Sterling will cause slight interruption in some services while the work is being performed. Expected downtime is 5-10 minutes for e-mail and database users. Web hosts should be mostly unaffected. (12:21am)
- 2006- Oct. 12th
- we conduct the big move into our newly-built green network operation center. expected downtime is 30 minutes to 1 hour as we power down our entire network and move it into the new facility. (12:21am)
- 2006- Oct. 11th
- a slight interruption of 5-15 minutes is expected while we reroute our incoming line to prepare for move to the upgraded network operation center. (12:21am)
- 2006- Sept. 15th
- g-noc move-in cancelled - no downtime experienced; task resecheduled for 10/12/06
- 2006- Sept. 14th
- network reroute cancelled - no downtime experienced; task resecheduled for 10/11/06