Service Availability Statement

This Service Availability Statement explains what users can expect from FPS.ms availability, maintenance, support, and downtime handling.

1. No Contractual SLA

FPS.ms does not provide a contractual Service Level Agreement, uptime guarantee, service-credit scheme, financial compensation, or downtime remedy unless we separately agree to one in writing. We aim to build and operate FPS.ms with high availability. Our internal engineering target is 99.9% availability for core production services, but this is a goal, not a legal promise, warranty, or basis for compensation.

2. Not for Mission-Critical Use

Do not use FPS.ms for mission-critical, life-safety, emergency, medical, financial trading, industrial control, critical infrastructure, legal compliance deadline, or other high-risk workloads. FPS.ms is built for game servers, apps, websites, development projects, community services, domains, DNS, and similar workloads where occasional downtime, maintenance, data loss risk, latency, or service interruption is acceptable. If downtime could cause serious harm, legal exposure, financial loss, or public safety risk, you need a provider and architecture designed for that risk.

3. Maintenance

We may perform scheduled, emergency, or unplanned maintenance to keep FPS.ms secure and reliable. Where practical, we try to announce scheduled maintenance in advance through the panel, status page, documentation, email, Discord, or another reasonable channel. Emergency maintenance may happen without advance notice. Maintenance may affect the panel, game servers, containers, apps, webhosting, domains, DNS, email-related features, databases, backups, snapshots, payments, deployments, support, APIs, or third-party integrations.

4. Exclusions

Availability issues are not covered by any compensation or credit. In particular, FPS.ms is not responsible for:

• your software, plugins, mods, apps, websites, code, configuration, databases, cron jobs, DNS records, or email setup;
• expired, suspended, deleted, downgraded, hibernated, or unpaid services;
• free services, best-effort services, preview features, beta features, or experimental features;
• DDoS attacks, abuse, malware, spam, phishing, security incidents, or enforcement actions;
• maintenance, migrations, emergency patches, capacity changes, or supplier changes;
• third-party providers, registries, registrars, payment providers, DNS providers, email providers, GitHub, Discord, Stripe, or other integrations;
• internet routing, transit providers, local network issues, client-side problems, browser issues, firewalls, blocked ports, or user devices;
• force majeure, government action, court orders, authority requests, power issues, upstream outages, supply chain incidents, or events outside our reasonable control.

5. Backups and Data Recovery

You are responsible for keeping your own backups. FPS.ms backup, snapshot, restore, export, replication, and redundancy features are convenience tools and do not remove your responsibility to keep independent backups outside FPS.ms. We do not guarantee that backups or snapshots will exist, be current, be complete, be restorable, or cover every service type.

6. Incident Communication

During incidents, we may prioritize mitigation and recovery over individual updates. When practical, we will provide updates through the panel, status page, Discord, email, documentation, or support channels. Support responses during major incidents may be delayed.

7. No Service Credits

FPS.ms does not provide service credits for downtime, packet loss, latency, maintenance, DDoS attacks, data loss, third-party outages, or other service interruptions unless we separately agree to credits in writing. Any goodwill credit we choose to provide is discretionary, may be account balance only, is not a cash refund, and does not create a future obligation.