Omegabit's network operates on a co-op principle. Our hosting facility has multiple 10Gbit carrier-class (OC) connections to the Internet and we do not throttle or limit the throughput of your system by default. What this means is that peak traffic to your site can spike substantially beyond any practical limit for brief periods with no impact on cost to you. Our carrier charges us for the average of peak 95 percentile of our traffic. This is commonly referred to in the industry as 95% or "burstable" billing.  In this co-op model, customers typically enjoy performance that is well beyond the practical limits of a standard hosting agreement by sharing a larger pipe, collectively.                                                                                                                                                                                                                 Omegabit does plan for a certain amount of bandwidth to be utilized by our installations, on average, over time. Our packages scale up or down accordingly. We do monitor usage trends for our installations. If your system is consistently using a disproportionate amount of co-op bandwidth, we may opt to offer you additional guaranteed sustained throughput at a competitive market rate, or to throttle the overall throughput of your system to meet or exceed your minimum guaranteed throughput at your discretion.

The specific size of the client infrastructure is dependent upon implementation and design decisions that will occur after this selection process.  Omegabit has provided a proposed footprint that is typical of a portal implementation meeting the stated requirements.  It includes an estimated bandwidth budget that is considerate of the included allowance, which scales up or down according to the number of server nodes subscribed.

Core cloud and network infrastructure:  99.999%

Liferay application infrastructure:  greater than 99.98%

Omegabit frames uptime in terms of application vs. core infrastructure stability as a more practical measure of efficacy.  Beware of providers that only indicate core infrastructure uptime vs. Liferay application uptime, which is typically higher, and can be misleading.

Omegabit commits that Client's hosted Web applications will have a monthly availability of 99.95% or greater. Monthly application availability is calculated using the following equation:
     
Availability Percentage = 100-((Md/43800)*100)
Where Md = The total minutes of unplanned downtime for the month
And 43800 is the average number of minutes in a calendar month
(22 minutes of downtime in a month would result in a total Network Availability for the month of 99.94%)
     

Planned Downtime     

Omegabit makes every effort to perform maintenance to its private cloud services transparently in the background without interrupting Client services in any capacity.  On rare occasion, a brief outage is required to complete maintenance or repair/replace piece of equipment, or in case of emergency security remediation. Omegabit makes every effort to provide at least 5 business days advanced notice for scheduled maintenance, and will provide Client with no less than 48 hours advanced notification concerning planned outages, which will include the following information:
● Affected systems and services
● Reason for outage
● Expected downtime
● Contact information
       
Downtime due to planned outages where the outage is within the expectation set in the notification and where Omegabit has provided notification of the event to the Client at least 48 hours in advance is not used in calculating monthly application availability.
       
In the event that Web application availability falls below 99.95% in any calendar month, Client will be credited on the next billing cycle with an amount equal to the percentage of the affected month's total hosting charges as indicated per the SLA terms.
       

Schedules and approvals are managed in direct coordination with Client teams to ensure changes are controlled and do not cause breakage. Actions are scheduled according to policies defined in the Omegabit SOW/SLA, except where explicitly overridden by special policy or Client requirement.