If your website is down, your organization is losing money. It’s as simple as that. And if your company website is down, it’s likely part of a larger issue affecting the network. So whether the lost revenue comes from lost sales if you’re an e-commerce site, a decrease in productivity of your employees who can’t access the whole network, engineering costs to resolve the issue, or negative impacts to the brand, the costs quickly add up.
But how much does network downtime really cost your company? It all depends on the size and industry you operate in; the larger the organization the higher the costs will be.
The most recent study performed by Ponemon Institute puts the average unplanned data center outage cost at nearly $9,000 per minute for the duration of the incident, with the most expensive incidents exceeding $17,000 per minute of unplanned outage. This represents a 32% increase from 2013, and a 81% increase from 2010. And these numbers are expected to continue to rise each year.
Another Ponemon report showed that network downtime will cost small and medium-size businesses between $8,000 and $74,000 per hour. What’s even more shocking is that most of the SMBs who experience an incident are forced to shut their doors during the incident, many never to reopen. This happens because these organizations don’t have a disaster recovery plan in place. Without a plan in place before an event occurs, it can take up to 3 months to recover. And for many small businesses, this is a long enough period to cause irrecoverable damages.
For enterprise level companies, the average cost of network downtime for a critical server ranges between $301,000 and $400,000 dollar per hour. And for the largest organizations, the costs can reach a staggering $5 million per hour.
Even the most strategically designed networks experience network downtime. Network downtime is something that every company will have to deal with at some point. However companies shouldn’t just accept network downtime as a cost of doing business. By taking a proactive approach to avoiding network downtime, you can minimize the risks (and thus the costs) associated with downtime.
You’ve spent thousands of dollars purchasing network security appliances like firewalls, IPS, and DLPs, not to mention the countless hours installing and programming these systems. But they aren’t worth anything if one failure takes your whole network down and renders them unable to do their job. By installing a Bypass Network TAP for each or multiple inline security tool, you can essentially eliminate any possibility of network downtime caused by the inline security appliance itself. The cost of the Bypass TAP is insignificant compared to the costs associated with network downtime, making it a smart step towards reducing your likelihood of network downtime.
[To learn more about how to design a network utilizing Bypass TAPs to reduce your network downtime and increase the lifecycle of your inline appliances, contact a member of the Garland Technology Design-IT team today!]
If the inline security tool goes off-line, the TAP will bypass the tool and automatically keep the link flowing. The Bypass TAP does this by sending heartbeat packets to the inline security tool. As long as the inline security tool is on-line, the heartbeat packets will be returned to the TAP, and the link traffic will continue to flow through the inline security tool.
If the heartbeat packets are not returned to the TAP (indicating that the inline security tool has gone off-line), the TAP will automatically 'bypass' the inline security tool and keep the link traffic flowing. The TAP also removes the heartbeat packets before sending the network traffic back onto the critical link.
While the TAP is in bypass mode, it continues to send heartbeat packets out to the inline security tool so that once the tool is back on-line, it will begin returning the heartbeat packets back to the TAP indicating that the tool is ready to go back to work. The TAP will then direct the network traffic back through the inline security tool along with the heartbeat packets placing the tool back inline.
Some of you may have noticed a flaw in the logic behind this solution! You say, “What if the TAP should fail because it is also in-line? Then the link will also fail!” The TAP would now be considered a point of failure. That is a good catch – but in our blog on Bypass vs. Failsafe, I explained that if a TAP were to fail or lose power, it must provide failsafe protection to the link it is attached to. So our network TAP will go into Failsafe mode keeping the link flowing.
Single point of failure: a risk to an IT network if one part of the system brings down a larger part of the entire system.
Heartbeat packet: a soft detection technology that monitors the health of inline appliances. Read the heartbeat packet blog here.
Critical link: the connection between two or more network devices or appliances that if the connection fails then the network is disrupted.