Uptime Terms

Last updated: May 14, 2026

We do our best to keep WESK RankBot online and responsive around the clock. This page explains what "our best" realistically means, the things we can't control, and the credit we offer to paid customers when we fall short.

1. The infrastructure we sit on

WESK RankBot runs on Amazon Web Services (AWS). AWS is one of the most reliable providers in the world, but it is not infallible — regional outages, networking incidents, and degraded services do happen, and when they do, parts of our Service may be unavailable until AWS recovers. We architect for resilience where it's practical, but we cannot guarantee uptime beyond what our underlying providers themselves guarantee.

2. Our reliance on Roblox

The core of what RankBot does — ranking, group lookups, member operations — depends entirely on Roblox's APIs. When Roblox is down, throttling, deploying changes, or quietly breaking an endpoint, our Service is affected in lockstep. There will inevitably be periods where rank operations fail, queue up, or take longer than usual because of something happening on Roblox's side. We do our best to detect, retry, and degrade gracefully, but we can't fix Roblox for them.

3. What we commit to

• Monitoring our services 24/7 and responding to incidents as quickly as we can.
• Retrying transient upstream failures and surfacing real errors to you, not silent drops.
• Publishing incident updates and post-mortems for anything that materially affects customers.
• Continuously investing in redundancy, queueing, and rate-limit handling to minimize the impact of upstream issues.

4. Uptime credit (Pro & Max)

If, in any given calendar month, the Service's measured availability drops below 99.99%, customers on the Pro or Maxplan are eligible for a service credit of up to $10 USD, applied to their next invoice.

• The credit is a goodwill remedy, not a refund, and is capped at $10 per affected month regardless of plan price or number of incidents.
• Uptime is measured against our own monitoring of the Service's public API and dashboard endpoints.
• Free-tier customers are not eligible for the uptime credit, but we still take outages affecting them seriously.
• Credits are automatically applied to your account when a period of downtime is detected.

5. What doesn't count as downtime

For the purposes of the credit above, the following are excluded from the uptime calculation:

• Outages, throttling, or breaking changes originating from Roblox, Discord, or other third-party platforms we integrate with.
• Outages caused by AWS or other upstream infrastructure providers, to the extent they affect our region(s).
• Scheduled maintenance announced at least 24 hours in advance via the dashboard or email.
• Issues caused by your own configuration, exhausted plan quotas, suspended accounts, or use that violates our Terms of Service.
• Force majeure events (natural disasters, large-scale internet outages, government action, etc.).

6. No other warranties

Beyond the credit described above, the Service is provided on an "as is" and "as available" basis, as set out in our Terms of Service. Nothing on this page creates any additional warranty, SLA, or guarantee of uptime.

7. Contact

Questions about uptime, an active incident, or a credit claim? Email oliver@wesk.cc.