Back to Services

Instant Emergency Response
Our technicians are available by phone 24/7 to respond to emergency situations that may occur.

Burstable Bandwidth & Live Bandwidth Reporting
There’s nothing worse than having a huge surge of traffic to your website and not having the bandwidth available to handle all the new visitors simultaneously. The network provisioning system can quickly provide network capacity to accommodate unexpected network activity.

Hardware Replacement Guarantee
ITI guarantees that all components on systems will function normally. Should any component fail, ITI will replace the failed component at no extra cost. Hardware replacement will begin immediately upon identification of component failure and is guaranteed to be completed within 24 hours of problem identification. Hardware is defined as any component operated by ITI. This includes but is not limited to Servers, Firewalls, Load-balancers, Switches, and Routers.

System Uptime Monitoring
Our monitoring system is capable of monitoring primary services such as HTTP, FTP and DNS, and secondary services such as PostgreSQL, MySQL and HTTPS.

Network Intrusion Detection System
ITI has acquired a multi-layered approach to network security. Your system’s first line of defense from malicious network activity is our proprietary intrusion detection system. Our IDS is a host-based system that constantly monitors server network connections to detect malicious activity. If suspicious network activity is detected, our team of security specialists is immediately notified and deployed to investigate the activity.

Multiple Bandwidth Providers
ITI utilizes connections to multiple backbones to ensure that data reaches the end-user in the fastest, most efficient manner possible. Our network also has plenty of excess capacity.


Infrastructure:

Connectivity
ITI utilizes connections to multiple backbones to ensure that data reaches the end-user in the fastest, most efficient manner possible.

Routing
ITI runs the Border Gateway Protocol (BGP4) for best case routing. Our entirely switched, Cisco powered network employs first class routers to ensure that data can be routed even in the event of a router failure. The BGP4 protocol is a standard that allows for the routing of packets of information sent out from the Network. Each packet of information is evaluated and sent over the best route possible. Because of our redundant network architecture, packets may be sent via alternative routes even if they are being delivered to the same end user. Should one of our providers fail, packets leaving our network are automatically redirected through another route via a different provider.

Bandwidth Utilization
The Network currently has plenty of excess capacity. This allows for us to accommodate even the largest spikes in traffic. We are always adding network connectivity and new routes in an effort to make sure content is delivered to your users as efficiently as possible. Low bandwidth utilization also allows for maximum uptime, even if one of our providers has an outage.

Data Center Environment
ITI provides the world-class infrastructure necessary to keep your servers up and running uninterrupted around the clock. Our data center has been engineered with fully redundant connectivity, power and HVAC to avoid any single point of failure, and is staffed 24 x 7 by our highly trained technical support personnel.

Security of your mission-critical Internet operations is of paramount importance. Multiple levels of security are employed to ensure that only Data Center Operations Engineers are physically allowed near your routers, switches, and servers.

Security Procedures:

No Public Access
Public access to the data center is strictly forbidden. Because we manage all equipment and are the only ones allowed in the data center environment, we are able to provide a higher level of service than anyone else in the industry.

Video Surveillance
Live video surveillance of the entire data center building is monitored 24/7. All entrances to the building as well as the data center are monitored to ensure that only authorized personnel are allowed into sensitive areas.

Onsite Security Personnel
Onsite security personnel monitor the data center building 24/7. The security team is responsible for making sure that only authorized personnel are allowed into the sensitive areas of the data center building. Security personnel provide the first layer of security for entering the data center.


Servers:

Load Balanced Server Cluster
Load Balanced Server Clustering allows a group of servers to intelligently service requests made to a host name. This high performance architecture allows for significantly greater performance than can be achieved by a single server.

In addition, if any of the services on a single server fail, the requests will be automatically routed to the remaining server. As a result, downtime related to server failures or administrative maintenance can be significantly reduced or eliminated!

Load Balanced server clusters feature the following:

-ASIC based, wire speed, hardware load balancing of HTTP, FTP, and SSL traffic
-Twice the performance of a single server is possible
-Automatic failover if a server or service becomes unavailable
-Private network (PNET) "ready"
-Remote console management to both servers
-Remote reboot either server independently at the power strip

How Clustering works:
The servers come in pairs, and each physical server has 4 IP numbers. Also, in addition to the IP addresses bound to the physical servers, there are an additional 4 virtual IP addresses configured on the load balancer. When HTTP, FTP or SSL requests are made to any of the virtual IP numbers, the load balancer sends the request to one of the physical servers, provided that server is "up" on that service port. If the server is not responding to that service port, all requests will be automatically sent to the remaining server.

Examples:
A standard high availability Load Balanced server cluster is configured with these IP numbers:

Example #1:

a) Create DNS records pointing towards the virtual IP addresses:

b) Create identical web sites, FTP data and SSL sites on both servers and bind the HTTP, FTP and SSL services to IP addresses as follows:

c) Clients communicate to the Load Balanced server cluster through the virtual IP numbers, and the supported requests are balanced across both real servers by changing the destination address at wire speed:

The following example is HTTP, but the same would also apply to both FTP and SSL.

Notice neither the client nor the server is aware of the load balancer as the traffic looks normal to both.

Notes:

- All IP addresses bound to the actual servers are also accessible from the Internet, including the 4 IP addresses on each server that participate in the load balancing. Additional IP addresses are available on request, however none of these additional IP addresses will participate in the load balancing.

- A client will always be mapped to the same physical server while communicating while using the same protocol. This will remain true until either the service fails, or the client has not communicated with the load balancer on that protocol for 1 hour.

- The load balancing method is based on the number of active clients allocated to each physical service. A request from a new client will be mapped to the server with the fewest active clients on that service. An active client is one that has communicated with the load balancer within the last hour.

- The load balancer performs layer 4 checks (opens a TCP connection to the service port) to determine if each service on both servers is "up". These checks are done every 10 seconds, and the service will be marked "down" if it fails 4 consecutive tests. The next time the server responds on the service port, it will be again be marked as available for requests.

- Both active and passive FTP are supported.

- Special server software is typically not necessary, and both the client and the servers are totally unaware of the load balancer.

* The private network (PNET) can be used to communicate between the two servers with un-metered bandwidth. This can be used to synchronize file system data, or utilize the same database. Moreover both of the load balanced servers can use the PNET to share a database hosted by a third server located anywhere on the network, even across datacenters.