The following PhoenixNAP Service Level Agreement ("SLA") is a policy governing the use of the PNAP Colocation under the terms of the Master Service Agreement (the "MSA") between PNAP, LLC., and Clients of PNAP. Unless otherwise provided herein, this SLA is subject to the terms of the MSA and capitalized terms will have the meaning specified in the Agreement. We reserve the right to change the terms of this SLA in accordance with the MSA.
PNAP guarantees that datacenter HVAC and power will be functioning 100% of the time in a given month, excluding scheduled maintenance. Power includes all distribution infrastructures up to and including the outlet in the Client area. Infrastructure downtime exists when a particular piece of system critical equipment is shut down due to power, heat, or humidity issues.
Client must monitor services and events as agreed upon by Client and PNAP. If Client identifies a failure event they are required to provide an e-mail to PNAP at [email protected] regarding the failure. Upon receipt of the email, PhoenixNAP will begin responding to event within 15 minutes using response plan provided by Client.
Client understands they are given the option to purchase power from divergent systems (Primary/Secondary Power) and it is PNAP’s strong suggestion that all Clients requiring mission critical uptime take advantage of this option. Due to the increase in redundancy recognized by utilizing Primary and Secondary circuits, Client will receive a significantly increased payment schedule in the event of an outage on both circuits. Client understands that by utilizing a pair of circuits as Primary/Secondary, the total amperage of both circuits cannot exceed 40% of their combined total load. For example, if both primary and secondary circuits have an amperage rating of 20 amps each—totaling 40 amps—then the amperage load combined across both circuits cannot exceed 16 amps (40% of 40 amps) combined. Exceeding this total will negate PNAP’s SLA. PNAP will provide an outlet for both the Primary and Secondary Power drops. It is the Client’s sole responsibility to utilize redundant power supplies and/or an automatic transfer switch (ATS) to failover in the event of an outage. PNAP is not responsible for Client equipment that does not perform as desired during a transition.
Client will be provided with up to 80% of breakered circuit (as mandated by 2008 NEC Section 210-19a) in a Primary power scenario or 40% of the total breakered circuit in the case of Primary/Secondary power.
The table below sets forth the Client’s sole and exclusive remedy for failures to meet Facility Service Level Objectives for the related datacenter colocation services referenced therein (Service Level Failure).
Credit Schedule for Power |
||
Power Failure Time |
Service Level Credit Schedule for Failure of Primary Circuit in a Single Power Configuration2 |
Service Level Credit Schedule for Concurrent Failure of Both Primary and Secondary Circuits in a Dual Power Configuration3 |
00:00:01 – 00:10:00 |
1% |
25% |
00:10:01 – 01:30:00 |
5% |
35% |
01:30:01– 08:00:00 |
10% |
50% |
08:00:01 – 16:00:00 |
20% |
75% |
16:00:01 – 24:00:00 |
30% |
100% |
24:00:01 – 32:00:00 |
40% |
100% |
32:00:01 – 48:00:00 |
50% |
100% |
48:00:01 or greater |
100% |
100% |
1. Time accumulation begins as per section 1.E: Service Level Credits. |
PNAP’s service level objective is to maintain an ambient temperature of 72 degrees Fahrenheit plus or minus 5 degrees (72° F ± 5° F), measured at the nearest supply grill, at all times. Client is obligated to monitor temperature for variations that would result in credit and request temperature to be measured by on-site staff.
PNAP’s service level objective is to maintain an ambient humidity of 45 percent plus or minus 15 percent (45% ± 15%) at all times. Client is obligated to monitor humidity for variations that would result in credit and request measurement by on-site staff.
The table below sets forth the Client’s sole and exclusive remedy for failures to meet the Facility Service Level Objectives for the related datacenter colocation services referenced therein (Service Level Failure):
Credit Schedule for Temperature and Humidity SLA |
||
Service Level Objective |
Service Level Failure |
Service Level Credit |
Temperature |
A Service Level Failure occurs when the ambient air temperature average falls outside of the range defined in 4.A. above and continues to be outside of that range for four (4) consecutive hours after the initial temperature reading outside of that range. |
The Service Level Credit shall equal 5% of the total monthly recurring charges for Datacenter colocation services of the affected Client Area--each temperature failure consisting of a consecutive four (4) hour Service Level Failure. |
Temperature: |
A service critical level failure occurs if the ambient air temperature average, as measured at the nearest supply grill is eighty-seven degrees Fahrenheit (87° F)or higher. |
The Service Level Credit shall equal 10% of the total monthly recurring charges for datacenter colocation services of the affected Client area each four (4) hour period of critical temperature failure. Client receives an initial Service Level Credit immediately upon the first occurrence of the critical temperature failure and receives further Service Level Credits for each subsequent consecutive four (4) hour period during which critical temperature failure continues. |
Humidity |
A Service Level Failure occurs when the ambient air relative humidity average as measured across all measurement points is outside the range of forty-five percent (45%), (plus or minus) fifteen percent (15%) relative humidity six (6) hours after the primary humidity reading fell outside of forty-five percent (45%), plus or minus fifteen percent (15%) relative humidity range. |
The Service Level Credit will equal the total monthly recurring charges for datacenter colocation services of the Client area multiplied by five percent (5%) for each humidity failure. For purposes of clarification Client receives a Service Level Credit after each consecutive six (6) hour period during which a humidity failure continues. |
Humidity: |
A Service Level Failure occurs when the ambient air relative humidity average as measured across all measurement points is over sixty-one percent (61%) 6 hours after the primary humidity reading was over sixty-one percent (61%) and critical humidity failure causes water to condense in the Client area. |
The Service Level Credit will equal the total monthly recurring charges for datacenter colocation services of the Client area multiplied by ten percent (10%) for each critical humidity failure. For purposes of clarification Client receives a Service Level Credit after each six (6) hour period during which a critical humidity failure continues. |
A Service Level Failure period begins upon receipt of an email by PNAP from Client of a detailed report of an incident and ends when the affected service is operational. Client will provide the report via email and trouble ticket. An applicable Service Level Credit Allowance will appear on Client’s invoice following processing. Service Level Credits will not have any cash value at the end of the Client’s term or otherwise. Service Level Credits will be calculated as a credit to the Monthly Recurring Charges for datacenter colocation services related to the specific datacenter and suite that experienced the Service Level Failure.
No Service Level Credits will be given for network services which are provided as part of a bundled package, or due to a service interruption:
The maximum total credit for all failures of PNAP to meet its Facility Service Level Agreement is limited to the total monthly recurring charge for datacenter colocation services by Client for the month in which the failure occurs.
Network SLA
This Network SLA applies only to clients who have selected the PNAP network services. If the Client uses a third-party carrier instead of the PNAP network, then the Client relies solely on that carrier's SLA. In such case, PNAP does not provide a Network SLA and this section does not apply to the Client.
PNAP guarantees that the network will be available 100% of the time during the billing cycle (excluding scheduled maintenance and promotional bundles which include bandwidth). Clients are not entitled to a credit if the downtime is caused by:
Client should report downtime incidents to us via email to [email protected] or submission through PNAP’s portal at https://portal.phoenixnap.com within three (3) days of the event's commencement. Only one event per report, please. Please include the service type, IP Address, and a full description of the service interruption including logs (if applicable). Downtime officially begins at the time PNAP receives the email "ticket" and verifies an outage, and ends when PNAP has, at its sole discretion, resolved the issue.
If Client are currently behind in payments for Client’s accounts, or have been behind 3 or more times in the preceding 12 months, Clients don't qualify for an SLA credit for Downtime. Valid SLA claims can't be credited if Client has outstanding abuse issues, but once Client’s abuse issues are resolved PNAP will gladly credit all valid claims. Making false or repetitive claims will cost Client $50 per incident and may place Client in violation of account Acceptable Use Policy and Terms and Conditions. Clients engaging in malicious or aggressive Internet activities such as attacks or counter-attacks are in violation of the Acceptable Use Policy and Terms and Conditions and are therefore not entitled to SLA credits.
20 Minute Support Response Guarantee. PNAP guarantees that one of PNAP’s talented professionals will respond to Client’s support tickets or inquiry within 20 minutes of submission. This applies to support tickets emailed to [email protected].
EXCEPTING THE REPRESENTATIONS, WARRANTIES, AND COVENANTS LISTED ABOVE, PNAP PERFORMS SERVICES AND PROVIDES SPACE TO CLIENT ON AN "AS-IS" BASIS. CLIENT'S USE OF THE SERVICES IS AT CLIENT'S OWN RISK. PNAP MAKES NO GUARANTEES ABOUT WARRANTIES INCLUDING, BUT NOT LIMITED TO, TENANTABILITY, HABITABILITY, MERCHANTABILITY, AND FITNESS FOR A PARTICULAR PURPOSE, TITLE, NON-INFRINGEMENT, OR WARRANTIES ARISING FROM THE COURSE OF DEALING, USE, OR TRADE PRACTICE. PNAP DOES NOT WARRANT THAT THE FACILITY SERVICES PROVIDED UNDER THIS AGREEMENT WILL BE UNINTERPTED, ERROR-FREE, OR COMPLETELY SECURE.
Both parties represent, warrant, or covenant that they haven't dealt with a broker or referrer that is not recorded on the SOF. Should a person or entity other than that broker/referrer claim a finder's fee, brokerage commission, or other compensation for acting in that capacity, the party the claimant claims to have brokered for holds the other party harmless, and/or indemnifies them against any claims and costs, expenses, and liabilities in connection with that claim--including, but not limited to, attorney's fees and court costs for defense of the claim.
Client SOF may allow for Client to complete some work in Client Area, or to designate someone to do that work. These provisions govern that work, if specified:
v.2; 11152021