We have known for a couple months now that we have made the Inc. 5000 list, but today we have learned our exact spot, #370, meaning we have made the prestigious Inc. 500 list of 500 fastest growing private companies in the US. You can see our full profile on the Inc.com site and there you can also see we are also #19 in the Chicago metro area and #46 in the IT Services category.
I would like to thank all of our employees, past and present, as well as all of our clients for helping us get to this point. I certainly couldn't have done it all by myself.
Today we have just added a new MySQL server to our shared hosting product to help improve overall MySQL performance. If you are a current shared hosting customer and are experiencing slowness on MySQL, please open a ticket with our support department and they will be able to schedule a time to move your databases over. This database migration would require the database to be taken down for a period of time to assure the data is migrated properly.
Note: If you are using the new MySQL server make sure to specify in any scripts you may be using to access mysql2.steadfast.net, not localhost or mysql.steadfast.net. All newly registered shared hosting accounts will use the new MySQL server by default.
I am happy to announce that our direct links to Comcast are now live. This gives us direct connectivity to the network that is most frequently accessing our network, as Comcast users alone currently counts for over 15% of our total network output. Comcast had also served as a trouble spot, where we would often get odd BGP routes broadcast, etc. but now that we have a direct contract with Comcast, and thus a direct line to their commercial transit NOC, we are hoping that such issues are an issue of the past. Comcast users, enjoy your new, faster speeds to our network!
Note: We currently have 2 Gbit/sec of capacity to Comcast, but will look at expanding that as our traffic to Comcast grows.
After the very successful network maintenance last night, we now have a single unified network. There is no more performance or standard network, it is just the Steadfast Networks network. Overall, this has greatly decreased the complexity of our network and gives us more flexibility overall. Already, this change has increased our internal network capacity and greatly improved our resiliency to DDoS and similar attacks.
Now that we have a single network, we are establishing a single group of carriers, to provide the same high level of service our performance network customers have come to expect. Over the past year we have been greatly expanding our own peering relationships, and once Comcast peering is added in the next couple days, we will be peering off nearly 50% of our traffic, greatly reducing our demand on full Internet transit. Since the demand for full transit is greatly reduced, we will be reducing the total number of carriers, though we will still be utilizing top quality providers and still primarily based on the two Tier 1's we have stuck with since the beginning, Level(3) and Savvis. Level(3) and Savvis will be supplemented by nLayer, who gets us Global Crossing routes, and TeliaSonera and all network traffic will still be optimized by our InterNAP FCP.
As for a timeline, the network are already unified, nLayer and TeliaSonera 10 GigE lines are up and running and our various GigE's to private and public peers will be complete when our connection with Comcast is fully configured, which should be today or tomorrow. All that is left then is adding our Level(3) 10 GigE, upgrading our Savvis circuit to a 10 GigE circuit, and finishing configuration changes on the InterNAP FCP, as it still hasn't caught up from all the changes last night. We are hoping to have all of these things completed by this time next month.
As many of our customers and visitors noticed (and were kind enough to let us know about), we had a lot of problems with our blog being redirected and modified through WordPress exploits in various versions of the software. Upgrading didn't seem to help and the exploits would occasionally render WordPress unusable or substantially modify its behavior. As this appears to be a common occurrence with WordPress, we decided to replace it with b2evolution to see if things run any smoother. Please let us know if you identify any problems with the new software. If we continue to have issues, we'll look into other alternatives.