Folosește codul WELCOME10 și beneficiezi de 10% reducere la toate serverele de jocuri, ofertă valabilă exclusiv pentru clienții noi, la prima comandă!
Service Level Agreement
Summarizes uptime guarantees, support expectations, and available service credits.
INTRODUCTION:
- This Hosting Service Level Agreement ("Agreement") is a legally binding contract between the Client (the person or entity using LIGAHOSTING Services) and LIGAHOSTING.RO (Despa Alexandru-Marian PFA) ("Company") and applies to any use of the Company's Services on the .ro domain.
- By using our services, the Client acknowledges that they have read, understood, and agreed to all the terms contained herein. LIGAHOSTING reserves the right to modify or update this Agreement at any time, with modifications becoming effective upon posting on our website.
- This SLA covers our core hosting services, including, but not limited to: game server hosting.
DEFINITIONS:
- Service(s): Hosting, game servers, managed services, or any other products provided by LIGAHOSTING.RO.
- Downtime: Any period during which the Service is unavailable or inaccessible through normal operation, measured from detection or reporting until restoration (excluding maintenance and exclusions).
- Unavailability: The failure of the Service to operate as described or guaranteed in this SLA.
- Rolling period: The preceding time window (e.g., 30 or 90 days) used for availability calculations.
- Service Credit: Monetary credit granted as compensation for SLA breaches.
- Scheduled maintenance: Planned downtime announced in advance to maintain system stability, performance, or security.
- Force majeure: Events beyond the reasonable control of LIGAHOSTING, such as natural disasters, acts of war, or government actions.
Service Availability and Guarantees
- Network Availability: Guaranteed 99.5% uptime over any 90-day period. If network uptime falls below 99.5% and the Service is inaccessible for more than 60 consecutive minutes (excluding maintenance), you are eligible for a pro-rata credit or a free day.
- Control Panel and Management Interfaces: 99.9% guaranteed availability. If inaccessible for more than 60 consecutive minutes while the server remains operational, the SLA credit applies.
- Hardware Reliability: Guaranteed physical server uptime. If hardware failure causes disruptions exceeding 480 consecutive minutes, the SLA credit applies.
- DDoS/DoS Mitigation: Mitigation initiated within 15 minutes of detection or confirmed report. If the service remains unavailable beyond that window, the SLA credit applies.
- Third-party Incidents: If the outage is caused by third-party providers (e.g., Dataforest) exceeding 3 continuous hours, the SLA credit applies.
Scheduled and Emergency Maintenance
- Maintenance is essential to ensure security and performance. Maintenance windows are announced in advance on our status page or via email.
- Downtime due to scheduled or emergency maintenance is excluded from uptime calculations.
- Emergency maintenance may occur without notice in cases where immediate actions are required to protect infrastructure integrity.
Notification Protocols
- All service statuses, maintenance notifications, and incident updates are available at https://as201131.net.
- Clients can subscribe to updates to receive notifications about outages or maintenance.
- Incident updates are communicated via tickets and/or email notifications until resolution.
Support and Response Times
- Support is available 24/7 via ticket, email, Discord, or WhatsApp.
- Response time for urgent/critical issues is under 24 hours during business hours; under 48 hours for non-critical matters.
- Response time refers to initial acknowledgment and communication, not full resolution.
- Resolution times depend on issue complexity, severity, and third-party dependencies.
- Support efforts are on a best-effort basis and depend on the accurate information provided by the Client.
- Business hours are Monday through Friday, between 09:00 and 22:00 UTC.
Incident Management and Resolution
- LIGAHOSTING follows an internal incident management procedure: detection, diagnosis, isolation, resolution, and recovery.
- Clients can request an incident report, including root cause, resolution steps, and mitigation timeline.
- Updates are provided during major incidents until normal operation is restored.
Data Backup and Recovery
- Automatic backups are offered free of charge by LIGAHOSTING.RO.
- The automatic backup service is an additional feature provided free of charge to LIGAHOSTING clients and does not constitute an absolute guarantee against data loss.
- LIGAHOSTING cannot guarantee that these backups will always be available or intact in the event of major technical failures.
- Clients are solely responsible for maintaining external backups of critical data.
- LIGAHOSTING is not liable for any data loss resulting from hardware or software failures.
Service Credits and Compensation
- In the event that SLA guarantees are not met, eligible clients may request service credits proportional to the downtime.
- Credits are capped at 100% of the monthly service fee and are non-transferable and non-refundable.
- Credits apply only to future invoices and represent the sole remedy for SLA breaches.
- Credit requests must be submitted via ticket within 7 days of the incident, including timestamps and supporting details.
- LIGAHOSTING will determine credit eligibility and value based on logs, monitoring data, and incident records.
Exclusions and Limitations
- Events beyond LIGAHOSTING's control are excluded, such as natural disasters, power outages, or upstream network disruptions.
- Downtime caused by scheduled or emergency maintenance is excluded from SLA metrics.
- Client misconfiguration, abuse, or violation of the Terms and Conditions or Acceptable Use Policy voids eligibility.
- Large-scale DDoS attacks that exceed providers' mitigation capabilities are excluded.
- Third-party service failures (software vendors, domain registrars, external APIs) are not covered.
- Indirect, incidental, or consequential damages, such as lost profits or data, are not claimable.
Liability and Client Responsibilities
- Service credits are the exclusive remedy for any SLA breach or service unavailability.
- LIGAHOSTING's total liability shall not exceed the service fee paid for the affected month.
- Clients must maintain accurate contact information and cooperate during investigations.
- Clients are responsible for their system configuration, data integrity, and securing their environments.
- Suspensions or terminations related to abuse are not eligible for credits or refunds.
Measurement Rules and Eligibility
- Authorized Measurement: Availability and downtime are measured using LIGAHOSTING's monitoring systems and incident logs, corroborated by the status page timeline.
- Availability Formula: Availability % = (Total minutes − Downtime minutes) ÷ Total minutes × 100.
- Downtime Start/End: Downtime begins at the earlier of (a) the verified monitoring alert or (b) the client ticket with reproducible evidence and ends when the service is restored.
- Per Service Basis: Credits apply only to the specifically affected service(s), not to unaffiliated services within the same account.
- Non-stacking: Credits for a single incident do not stack across multiple metrics; the highest applicable credit applies.
- Good Standing: To receive credits, the account and associated service must be active and not suspended or terminated.
- Authorized Requester: Credit requests must come from the account owner or authorized contact via the ticketing system within 7 calendar days of the incident.
- Planned Changes and Force Majeure: Scheduled/emergency maintenance and events beyond our control are excluded from downtime calculations.
- Configuration Requirement: The Client must follow documented setup and security instructions; material deviations or insecure modifications may invalidate eligibility.
Change Management and Transparency
- LIGAHOSTING reserves the right to update this SLA. Updated versions become effective immediately upon publication.
- Availability and incident statistics are transparently published on our status page.