Game Servers
⛏️ Minecraft: Java Edition 🌐 Minecraft: Bedrock Edition 🎮 All Game Servers
Site
Learn Support Status Service Level Agreement
Account
👤 Billing 🖥️ Panels 💬 Discord

Service Level Agreement

A plain-English commitment to what you can expect from Beyer Hosting — and what happens if things go wrong.

Effective: April 2026
👋

A note from Rowan

Beyer Hosting is run by one person — me, Rowan. I don't have a legal team or a 24/7 NOC. What I do have is a genuine commitment to keeping your servers running and making things right when they don't. This SLA is my promise to you, written as clearly as I can manage.

01
Uptime Commitment

I aim to keep your server's host node online and reachable as close to 100% of the time as possible. Realistically, no infrastructure is perfect, but here's what I'm committing to:

Target Uptime
99.5%
Per month, measured at the node level. That's less than 4 hours of unplanned downtime per month.
Measured At
Node Level
The physical server your game server runs on. Individual server crashes caused by mods or configs aren't counted.

Uptime is calculated as: ((Total minutes in month – Unplanned downtime minutes) / Total minutes in month) × 100

I chose 99.5% rather than claiming 99.99% like big hosts do — because I'm being honest. I run this solo, and I think a realistic promise you can actually hold me to is worth more than an inflated number.

02
What Counts as Downtime

Downtime means your server's host node is completely unreachable or non-functional due to something on my end — hardware failure, network outage, or infrastructure problems within my control.

It does not include your individual game server crashing, running out of memory due to mods, or being stopped from the panel. That's your server, not the node.

03
What's Not Covered

The following situations are outside the scope of this SLA — meaning they won't count against my uptime commitment and won't qualify for credits:

  • Your server crashing due to mods, plugins, misconfigurations, or running out of RAM for your workload.
  • Scheduled maintenance that I announce in advance (at least 24 hours where possible).
  • Emergency maintenance to prevent data loss or hardware failure — I'll notify you as fast as I can.
  • DDoS attacks that overwhelm mitigation — see Section 5.
  • Data center or upstream issues beyond my control — power outages, ISP failures, etc.
  • Force majeure — natural disasters, widespread internet outages, or other unforeseeable events.
  • Suspended accounts due to non-payment or Terms of Service violations.
  • Issues with third-party services your server connects to, like Steam or external APIs.
04
Maintenance

Scheduled maintenance: I'll give at least 24 hours' notice before any planned work that might affect your server — usually via Discord and/or email. Scheduled maintenance doesn't count against uptime.

Emergency maintenance: Sometimes hardware needs urgent attention to prevent something worse (like data loss). In those cases I'll notify you as quickly as I can and get things back online fast. Emergency maintenance is also excluded from the uptime calculation.

The best place to follow maintenance updates in real time is the status page and the Discord server.

05
DDoS Protection

Basic DDoS mitigation is in place at the network level. I'll do my best to absorb and filter attacks, but I'll be upfront: large-scale attacks can still cause disruption. No hosting provider can guarantee 100% DDoS immunity, and downtime caused by attacks beyond my mitigation capacity is excluded from this SLA.

If your server is being targeted repeatedly, reach out on Discord and we'll figure out next steps together.

06
Credits & Compensation

If node uptime falls below 99.5% in a given month due to something covered by this SLA, you can request a credit. Here's how it works:

Qualifying Downtime Credit Applied
1–2 hours1 day added to your service
2–4 hours2 days added to your service
4–8 hours4 days added to your service
8+ hoursUp to 7 days, reviewed case-by-case

To claim a credit, just reach out within 7 days of the incident via Discord or the support page. Tell me what happened, when, and which server was affected. I'll look into it and apply the credit if it qualifies — no bureaucracy, no runaround.

Credits are applied as service extensions, not cash refunds. The maximum credit per incident is 7 days.

Need to report an outage?Reach out directly on Discord — it's the fastest way to get a response and start a credit claim.

Open a Ticket on Discord
07
General Notes

This SLA is the full extent of what I'm committing to for infrastructure-related issues. It doesn't cover things outside my control or situations caused by your own configuration choices.

I may update this SLA as the service grows or changes. If I make significant changes, I'll post an announcement in Discord. Continued use of the service after changes means you accept the updated terms.

At the end of the day — if something goes wrong, just talk to me. I'd rather fix a problem and keep you as a happy customer than hide behind fine print.