Legal
Service Level Agreement
This SLA framework explains how availability and support commitments should be defined for BryskBits services.
This page describes the SLA structure. Binding uptime targets, hardware replacement targets, support response targets, credit percentages, and measurement windows must be stated in the written order or master service agreement.
1. Scope
The SLA may apply to network availability, dedicated server hardware availability, support response, or custom managed-service obligations, depending on the ordered service. Self-managed software and customer applications are outside the SLA unless expressly included.
2. Availability commitments
Check your written SLA for a specific availability target. To assess an interruption, identify the service boundary, monitoring method, outage start and end rules, maintenance exclusions, and customer reporting requirements.
3. Hardware replacement
Hardware replacement commitments depend on datacenter access, part availability, fault confirmation, and whether equivalent replacement hardware is acceptable. The written order should state the target and exclusions.
4. Support response
Support response targets should define priority levels, support hours, required ticket information, escalation path, and what counts as acknowledgement versus resolution.
5. Maintenance
Scheduled maintenance, emergency maintenance, upstream carrier events, security response, and customer-requested changes may be excluded from availability calculations depending on the written SLA.
6. Credits
Service credits, if offered, should be requested through support and are typically the sole remedy for SLA failure. The written SLA should define credit percentages, caps, eligibility, request deadlines, and non-creditable events.
7. Exclusions
SLA coverage should exclude downtime caused by customer software, misconfiguration, abuse, non-payment, violated terms, DDoS events beyond the agreed mitigation scope, force majeure, third-party services outside BryskBits control, or customer failure to cooperate.
8. Custom service levels
100 Gbps, bandwidth pool, IPTV, and custom infrastructure customers can request written service levels during configuration review. Do not rely on a verbal target; it should appear in the final order.
Read alongside your written order and the related policies below.
Questions & answers
Availability and credits
Browse all topicsDoes a network chart establish an SLA entitlement?
No. A credit depends on the SLA applicable to your order, its measurement method, exclusions and claim procedure. An illustration or isolated ping result does not establish entitlement.
What evidence helps with an availability claim?
Keep the service ID, incident interval with time zone, symptoms and relevant correspondence. Use the reporting method and deadlines in the written agreement.
Is application playback covered by a network SLA?
Not automatically. Player errors, origin storage and transcoding faults can interrupt playback while the network remains reachable. Check which service boundary your order covers.
Does a maintenance notice count as downtime?
Use the maintenance terms in the applicable agreement. Keep the notice and record the actual interruption in the same time zone.
Are response and repair targets the same thing?
No. A response target concerns acknowledgement or initial action. A repair or restoration target concerns returning the covered service to operation.
