Policy
Service level agreement
Operational targets for uptime, maintenance and response handling
Last updated 11 Apr 2026 support@tryb4host.com
This page describes the service targets Tryb4Host works toward for active hosting services, along with the exclusions and review process that apply to availability incidents. It is meant for active production services. It is not a promise that no outage, routing issue or upstream event can ever occur.
Availability target
99.9% monthly for standard managed workloads
Critical acknowledgement
Within 2 hours
Credit requests
support@tryb4host.com within 30 days of the incident
1. Availability targets
- Shared hosting and standard managed workloads are operated toward a monthly availability target of 99.9%.
- Higher-complexity routed or offshore-aware deployments may follow service-specific targets agreed during onboarding.
- Domain registration and DNS propagation timing can depend on registry, resolver and upstream factors outside direct SLA control.
2. Support acknowledgement targets
- Critical service-impact incidents: acknowledgement within 2 hours.
- Billing, renewal and provisioning questions: acknowledgement within 1 business day.
- Routine information requests or non-urgent advisory questions: acknowledgement within 2 business days.
3. Planned maintenance and exclusions
Availability calculations exclude scheduled maintenance, upstream registry issues, registrar delays, abuse-mitigation actions, force majeure and customer-caused incidents.
- Emergency maintenance may occur without long notice when security or infrastructure stability requires it.
- Routing changes performed to reduce risk or restore continuity are treated as operational mitigation, not an SLA breach by default.
- Customer application bugs, unsupported custom code and external service dependencies are outside platform uptime review.
4. Credit review
Where an availability target is missed for reasons within our control, you may request a service credit against the affected service.
- Submit the request within 30 days of the incident, with the affected service and the observed impact window.
- Credits are applied against future service on the same account and are not paid out in cash.
- Credits are the sole remedy for missed availability targets under this agreement.
Questions about this policy?
Write to support@tryb4host.com
and a person will answer — we do not route policy questions to a bot.