Service Limitations
Last Updated: April 7, 2026
1. Fair Infrastructure Use
To preserve platform stability and equitable performance, we may apply controls on burst activity, abusive process behavior, extreme I/O saturation, or network patterns that degrade shared infrastructure health.
2. Compute and Memory Constraints
Plan specifications define baseline and maximum compute/memory allocations. Sustained usage outside plan thresholds may trigger throttling, migration advisories, or plan upgrade requirements.
3. Storage and Backup Limits
Backup retention, snapshot cadence, and storage I/O ceilings vary by service tier. Where backup services are included, restore guarantees may depend on plan type, data consistency state, and incident severity.
4. Network and Traffic Management
Plans may include committed transfer quotas, port speed caps, or peering constraints. To protect upstream and downstream availability, we may enforce temporary packet shaping, route controls, or mitigation filters during attack or abuse events.
5. Maintenance and Emergency Operations
Scheduled maintenance may affect service availability during announced windows. Emergency maintenance may be performed without prior notice where required to contain active security risk or preserve infrastructure integrity.
6. Third-Party Dependencies
Certain service components rely on external carriers, payment rails, registrars, or software providers. Performance or availability impact caused by third-party outages may fall outside direct remediation guarantees.
7. Enforcement and Corrective Action
Where these limitations are exceeded or policy risk is identified, Wensor Cloud may implement protective actions including traffic filtering, feature restrictions, temporary suspension, or migration requirements. We will provide notice when reasonably practical.