Racko
SERVICE AVAILABILITY

Service Level Agreement

Understand the availability commitments, measurement methods, and service credit process for eligible Racko sovereign cloud infrastructure and managed technical fabrics.

DOC-REF: SLA-2025-V1
EFFECTIVE DATE: [Effective date]·LAST UPDATED: [Last updated date]·SCOPE: Eligible Enterprise & Public Cloud Infrastructure
AWAITING RATIFICATION

01 /Overview

This Service Level Agreement describes the availability commitments and service credit process applicable to eligible Racko services. Coverage depends on the purchased product, deployment configuration, and applicable order or service agreement.

Contractual Boundary Scope

Service-specific commitments: [Identify the agreements or service schedules that determine coverage].

Effective coverage period: [Confirm when SLA coverage begins and ends].

Note: Where an individually signed agreement contains different commitments, the applicable agreement determines the service levels and remedies.

02 /Covered services

The following table identifies service coverage and the infrastructure components included in each commitment.

Listing does not establish a confirmed SLA commitment until finalized by Racko operations.
SERVICESLA COVERAGECOVERED COMPONENT
VPS & Cloud VPS[Confirm eligibility][Define covered compute and network components]
Dedicated Servers[Confirm eligibility][Define covered hardware, power and network components]
Private Cloud[Confirm agreement-specific coverage][Define covered infrastructure boundary]
GPU Cloud[Confirm eligibility][Define covered GPU infrastructure and access components]
S3 Storage[Confirm eligibility][Define covered storage endpoints and operations]
Backup Storage[Confirm eligibility][Define covered storage access and backup service components]
CloudLabs[Confirm eligibility][Define covered lab infrastructure components]
Web Hosting[Confirm eligibility][Define covered hosting components]
Managed Cloud Operations[Confirm agreement-specific coverage][Define covered operational services]

03 /Availability commitments

Availability targets apply only to the covered components and configurations specified in the applicable agreement.

AVAILABILITY TARGET
[Approved target by eligible service]
MEASUREMENT PERIOD
[Approved measurement period and time zone]
COVERAGE BOUNDARY
[Infrastructure components and endpoints covered]
COVERAGE START
[Provisioning, acceptance or other approved start condition]
SERVICE TIERAVAILABILITY TARGETMEASUREMENT PERIOD
Public Cloud Tier: VPS, GPU Cloud, S3 Storage[Approved availability target][Approved measurement period]
Enterprise Bare Metal & Private Cloud[Approved availability target][Approved measurement period]
!Contractual availability targets must be confirmed by Racko. No marketing reliability claims are substituted.

04 /Measurement and downtime

Availability is assessed using the measurement method defined for the eligible service.

MEASUREMENT SOURCE[Approved monitoring system and records]
SERVICE UNAVAILABLE MEANS[Approved definition and failure threshold]
DOWNTIME BEGINS[Approved detection or reporting condition]
DOWNTIME ENDS[Approved restoration condition]
PARTIAL DEGRADATION[Approved treatment of reduced performance or partial failures]
EXCLUDED TIME[Approved treatment of maintenance and other exclusions]
MATHEMATICAL VERIFICATION STANDARD

Calculation Method: [Insert the approved availability formula, including numerator, denominator, exclusions and rounding rules].

Availability (%) = ((Total Time - Excluded Time - Downtime) / (Total Time - Excluded Time)) × 100
[Approved Formula Pending Formal Certification]

05 /Maintenance

Racko may perform maintenance to maintain, secure, or upgrade its physical and virtual infrastructure.

SCHEDULED MAINTENANCE NOTICE
[Approved notice period]
NOTIFICATION CHANNELS
[Approved email, dashboard or status notification channels]
MAINTENANCE WINDOW
[Approved window and time zone, where applicable]
EMERGENCY MAINTENANCE
[Approved notification and handling process]
SLA TREATMENT
[Confirm whether and how maintenance affects availability calculations].

06 /Exclusions

The applicable SLA must specify which events fall outside its availability commitment. Items requiring confirmation include:

Customer-managed applications and operating systems.
Customer configuration changes and software patches.
Customer credentials, key rotations, and access controls.
Networks outside the agreed service boundary and peer transit.
Third-party services, downstream software, and dependencies.
Planned and certified emergency infrastructure maintenance.
Service suspension under applicable terms of service or AUP.
Preview, beta, early access, or non-production trial services.
Events outside the agreed operational scope (including external Force Majeure).
FORMAL LEGAL CLAUSE
Confirmed exclusions: [Insert the approved exclusions and their precise conditions].

07 /Incident reporting

If you experience a service issue, report it through [approved support channel].

REQUIRED INCIDENT SUBMISSION DETAILS
•Account or organization identifier
•Affected service identifier
•Region or deployment location
•Time the issue began (with time zone)
•Comprehensive description of impact
•Relevant logs or diagnostic telemetry
Security Protocol

Do not include passwords, private keys, API secrets or sensitive customer data in incident reports.

INCIDENT UPDATES[Approved update channel and communication frequency]
INITIAL RESPONSE[Approved response targets by support plan or severity, if offered]
RESTORATION[Approved restoration commitment, if any]
Initial support response is clearly distinguished from service restoration.View System Status

08 /Service credits

Where an eligible service falls below its approved availability commitment, the customer may qualify for a service credit under the applicable terms.

CREDIT ELIGIBILITY[Approved conditions]
CALCULATION BASIS[Eligible service charge and billing period]
CREDIT APPLICATION[Approved method of applying credits]
MAXIMUM CREDIT[Approved cap per service and measurement period]
REFUND RELATIONSHIP[Confirm whether credits can be paid as cash or applied only to future charges]
MEASURED AVAILABILITYCREDIT PERCENTAGECALCULATION BASIS
[Approved availability band 1][Approved percentage][Approved basis]
[Approved availability band 2][Approved percentage][Approved basis]
[Approved availability band 3][Approved percentage][Approved basis]

09 /Submit a claim

STEP 01
Report the incident

Submit the service issue through the approved support channel and retain the ticket reference.

STEP 02
Prepare supporting details

Gather affected service identifiers, incident timestamps, invoice details, and relevant diagnostic evidence.

STEP 03
Submit the credit request

Send the formal claim through [approved SLA claim channel] referencing your incident ticket.

STEP 04
Receive formal outcome

Racko will review the claim against the applicable SLA and communicate the final credit determination.

CLAIM TIMELINES & PARAMETERS

Claim submission deadline: [Approved deadline and when it begins]

Review timeframe: [Approved review timeframe]

Credit application timeframe: [Approved timeframe following approval]

MANDATORY SUPPORTING DOCUMENTS
Account IDService IDTicket ReferenceStart/End TimestampsInvoice PeriodTelemetry Evidence

10 /Responsibilities

Racko's Responsibilities

[Insert confirmed responsibilities for operating, monitoring and maintaining covered infrastructure].

Customer Responsibilities

[Insert confirmed requirements for reporting incidents, maintaining contact details and managing customer-controlled components].

Data Protection & Backup Boundaries

Availability, backups, and recovery are separate service considerations. Any backup retention, recovery point, or recovery time commitments must be defined in the applicable service agreement.

RECOVERY POINT OBJECTIVE (RPO)
[Approved RPO, if contracted]
RECOVERY TIME OBJECTIVE (RTO)
[Approved RTO, if contracted]

Explicit Rule: An availability SLA does not automatically guarantee data recovery or prevent data loss.

11 /Updates & contact

Racko may revise this SLA as its services and contractual arrangements change.

NOTICE OF CHANGES[Approved notification process]
EXISTING SERVICES[Approved treatment of existing subscriptions and agreements]
ENTITY GOVERNANCE
Racko — A product of Gisul Software Services Pvt. Ltd.
SLA SUPPORT CHANNEL
[Approved email or support URL]
ESCALATION CONTACT
[Approved escalation contact]
SUPPORT OPERATIONAL HOURS
[Approved hours and time zone]
CORPORATE ADDRESS
[Confirmed company contact address]