Excess Availability Borrowers shall have Excess Availability at all times of at least (i) as of any date of determination during the period from July 25, 2016 through and including August 29, 2016, $10,000,000, (ii) as of any date of determination during the period from August 30, 2016 through and including October 17, 2016, $13,000,000, (iii) as of any date of determination during the period from October 18, 2016 through and including October 31, 2016, $17,500,000, and (iv) as of any date of determination during the period from November 1, 2016 through and including December 31, 2016, $20,000,000.
Maximum Consolidated Leverage Ratio The Consolidated Leverage Ratio at any time may not exceed 0.75 to 1.00; and
Minimum Excess Availability Borrower shall have Excess Availability under the Revolving Credit Loans facility of not less than the amount specified in the Schedule, after giving effect to the initial advance hereunder and after giving effect to any applicable Loan Reserves against borrowing availability under the Revolving Credit Loans.
Minimum Availability Borrower shall have minimum availability immediately following the initial funding in the amount set forth on the Schedule.
Minimum Consolidated EBITDA The Borrower will not permit Modified Consolidated EBITDA, for any Test Period ending at the end of any fiscal quarter of the Borrower set forth below, to be less than the amount set forth opposite such fiscal quarter: Fiscal Quarter Amount September 30, 1997 $36,000,000 December 31, 1997 $36,000,000 March 31, 1998 $36,000,000 June 30, 1998 $37,000,000 September 30, 1998 $37,000,000 December 31, 1998 $38,000,000 March 31, 1999 $38,000,000 June 30, 1999 $39,000,000 September 30, 1999 $40,000,000 December 31, 1999 $41,000,000 March 31, 2000 $41,000,000 June 30, 2000 $42,000,000 September 30, 2000 $43,000,000 December 31, 2000 $44,000,000 March 31, 2001 $44,000,000 June 30, 2001 $45,000,000 September 30, 2001 $46,000,000 December 31, 2001 $47,000,000 March 31, 2002 $47,000,000
System Availability Although we will try to provide continuous access to the Service, we cannot and do not guarantee that the Service will be available 100% of the time and will not be liable in the event Service is unavailable. Actual service or network performance is dependent on a variety of factors outside of our control. If you notify us within twenty-four (24) hours and we confirm an outage consisting of a period of two (2) hours in any calendar month, and not due to any service, act, or omission of you, a third party, your applications, equipment or facilities, or reasons outside of our control, you shall be eligible for a service credit. A service credit shall be computed as a pro-rated charge for one day of the regular monthly fees for the Service in the next monthly statement. Intermittent service outages for periods of less than two (2) hours are not considered service outages. Outages caused by routine scheduled maintenance are also not considered an outage. You shall receive advance notice no less than forty-eight (48) hours in advance of our scheduled maintenance. Scheduled maintenance will be performed between 12:00 a.m. and 6:00 a.m. CST.
RDDS availability Refers to the ability of all the RDDS services for the TLD, to respond to queries from an Internet user with appropriate data from the relevant Registry System. If 51% or more of the RDDS testing probes see any of the RDDS services as unavailable during a given time, the RDDS will be considered unavailable.
FUNDING AVAILABILITY This Contract is contingent upon the continued availability of funding. If funds become unavailable through the lack of appropriations, legislative or executive budget cuts, amendment of the Appropriations Act, state agency consolidation or any other disruptions of current appropriations, DFPS will reduce or terminate this Contract.
Annual Percentage Rate Each Receivable has an APR of not more than 25.00%.
High Availability Registry Operator will conduct its operations using network and geographically diverse, redundant servers (including network-‐level redundancy, end-‐node level redundancy and the implementation of a load balancing scheme where applicable) to ensure continued operation in the case of technical failure (widespread or local), or an extraordinary occurrence or circumstance beyond the control of the Registry Operator. Registry Operator’s emergency operations department shall be available at all times to respond to extraordinary occurrences.