Fusion Arc Hosting is committed to providing reliable, secure, and high-performance hosting services while maintaining a stable hosting environment for all customers.
Shared hosting platforms are designed around the principle that customers use resources as needed without any single account continuously consuming a disproportionate amount of the underlying server capacity.
This Fair Usage Policy (“FUP”) explains how Fusion Arc Hosting evaluates resource usage across Shared Hosting, WordPress Hosting, Reseller Hosting, Agency & Enterprise Hosting, and Semi-Dedicated Hosting services.
This policy should be read together with the applicable Fusion Arc Hosting Terms of Service, Acceptable Use Policy, Privacy Policy, product descriptions, and any service-specific terms.
This Fair Usage Policy applies to the following Fusion Arc Hosting services.
NanoVault
CloudLite
ByteBoost
NanoNet
TurboTitan
HyperHaven
NanoNet
TurboTitan
HyperHaven
Elite Reseller
Ultra Reseller
Titan Reseller
Olympus
Zenith
Aether
PowerEdge
ProEdge
HyperEdge
VPS and VDS services generally operate within the resources allocated to the applicable virtual server and may be subject to separate service-specific resource and acceptable-use requirements.
Certain provisions of this policy, including network abuse, security, email reputation, and infrastructure protection requirements, may also apply to VPS, VDS, or other Fusion Arc Hosting services where appropriate.
Fusion Arc Hosting does not evaluate fair usage based solely on one measurement.
We may consider factors including:
CPU utilization
Physical memory usage
Disk I/O
IOPS
Entry processes
Total processes
Concurrent processes
Database activity
Database connections
Inode usage
Disk storage
Bandwidth
Network connection volume
Email activity
Backup activity
Filesystem activity
Application behavior
Cron job frequency
Security scanning impact
Malware activity
Traffic patterns
Resource duration
Resource frequency
Overall effect on the hosting platform
Short bursts of increased resource usage are generally expected during normal website operation.
A temporary traffic spike, software update, backup operation, administrative task, cache rebuild, or other short-duration workload is not normally considered excessive solely because it temporarily consumes significant resources.
Our primary concern is sustained, recurring, abnormal, abusive, or inefficient resource usage that materially affects the stability, security, or performance of the hosting platform or other customers.
Fusion Arc Hosting may use technical resource controls to maintain platform stability.
Depending on the service, these may include limits or controls for:
CPU
Physical memory
Virtual memory
Disk I/O
IOPS
Entry processes
Process counts
Concurrent processes
Database activity
PHP workers
Application processes
Network activity
Email sending
Filesystem operations
These controls may be implemented using technologies including cPanel, CloudLinux, LVE, CageFS, LiteSpeed, operating-system controls, database management systems, security software, or other infrastructure systems.
Technical limits may vary between hosting plans.
The applicable resource allocations for a specific hosting plan may be displayed on our website, order form, product description, customer portal, cPanel interface, or other service documentation.
Technical resource limits and fair usage thresholds are not necessarily the same thing.
A customer may technically remain below an individual resource limit while still generating a workload that requires review due to its overall impact on the server.
Likewise, a short temporary burst to a resource limit does not automatically mean that an account is violating this policy.
CPU resources are shared among accounts on Shared, Reseller, Agency, Enterprise, and Semi-Dedicated hosting platforms.
Normal CPU usage may include:
PHP execution
WordPress requests
Database queries
Control panel operations
Website administration
Application execution
Scheduled jobs
Software updates
Cache generation
Normal traffic spikes
Accounts should not continuously consume disproportionate CPU capacity for extended periods.
Examples of CPU-intensive workloads that may require review include:
Poorly optimized PHP applications
Infinite application loops
Excessive WordPress cron activity
Runaway scripts
Extremely high-frequency cron jobs
Continuous data processing
Video transcoding
Large-scale image processing
Cryptocurrency mining
Computational workloads unrelated to normal web hosting
Continuously executing background scripts
Applications repeatedly hitting CPU limits for extended periods
Repeated or sustained CPU exhaustion may indicate that the application requires optimization or a higher-resource hosting environment.
Fusion Arc Hosting may recommend Semi-Dedicated Hosting, VPS, VDS, or other dedicated resources when an application consistently requires significant CPU capacity.
Hosting accounts may use memory as necessary within the allocation associated with their hosting plan.
Memory usage may include:
PHP processes
Node.js applications
Python applications
Database operations
Application frameworks
WordPress plugins
Caching systems
Control panel processes
Email-related processes
Applications should not continuously exhaust available physical memory.
Repeated memory exhaustion can cause:
Application failures
HTTP 500 errors
HTTP 503 errors
Process termination
Reduced application performance
Increased server load
Instability
Customers experiencing repeated memory exhaustion may be asked to optimize their application or move to a service with additional resources.
Disk I/O represents the rate at which an account reads or writes data to server storage.
IOPS represents the number of input/output operations performed against storage.
Heavy filesystem workloads may affect the performance of other accounts even where total disk storage usage remains relatively small.
Examples include:
Applications constantly creating or deleting files
Extremely large cache directories
Large numbers of temporary files
High-frequency logging
Continuous backup generation
Repeated archive extraction
Large import or export operations
Large database operations
Filesystem-intensive scripts
Excessive email storage operations
Applications scanning millions of files repeatedly
Accounts generating sustained or unusually high disk activity may be reviewed even if their storage and inode usage remain within normal ranges.
Entry processes generally represent concurrent requests entering an account through supported application interfaces.
High entry-process usage can result from:
Large traffic spikes
Slow PHP applications
Bots
Crawlers
API traffic
Poor database performance
Long-running web requests
WordPress plugin activity
Application loops
Malicious traffic
Occasional entry-process spikes are normal.
Repeated exhaustion may indicate that the website requires optimization, caching, security controls, or additional hosting resources.
Hosting platforms may limit the number of processes that can simultaneously execute under an account.
Processes may include:
PHP
LSAPI
Node.js
Python
Cron jobs
Shell commands
Email processes
Application workers
Control panel operations
Customers must not intentionally bypass process controls or create uncontrolled process-spawning workloads.
Examples of problematic behavior include:
Fork bombs
Recursive process spawning
Infinite worker creation
Excessive daemon processes
Scripts continuously relaunching failed processes
Applications generating hundreds or thousands of unnecessary concurrent processes
Fusion Arc Hosting may terminate individual runaway processes when necessary to protect server stability.
An inode generally represents a filesystem object such as:
A file
Directory
Email message
Cache object
Session file
Application file
Log
Temporary file
Fusion Arc Hosting generally uses soft inode review thresholds rather than automatic hard inode limits on the hosting services covered by this policy.
General soft review thresholds are:
| Hosting Plan | General Soft Review Threshold |
|---|---|
| NanoVault | Approximately 150,000 inodes |
| CloudLite | Approximately 250,000 inodes |
| ByteBoost | Approximately 350,000 inodes |
| NanoNet | Approximately 250,000 inodes |
| TurboTitan | Approximately 400,000 inodes |
| HyperHaven | Approximately 600,000 inodes |
| Elite Reseller | Approximately 250,000 per cPanel account |
| Ultra Reseller | Approximately 400,000 per cPanel account |
| Titan Reseller | Approximately 600,000 per cPanel account |
| Olympus | Approximately 500,000 per cPanel account |
| Zenith | Approximately 650,000 per cPanel account |
| Aether | Approximately 800,000 per cPanel account |
These figures are review thresholds and not automatic hard limits.
Crossing a threshold does not automatically result in suspension, restriction, additional charges, or a required upgrade.
Fusion Arc Hosting may permit inode usage beyond these thresholds when the workload remains appropriate for the hosting platform.
Requests for additional inode capacity may be reviewed based on:
Filesystem composition
Disk usage
Account purpose
Backup performance
Security scanning performance
Filesystem activity
Application behavior
Email volume
Server capacity
I/O impact
Overall platform health
Accounts approaching approximately 750,000 to 1,000,000 inodes may receive additional review.
This does not mean such usage is automatically prohibited.
However, sustained usage at this level may indicate that the account is beginning to exceed the workload characteristics expected on a standard Shared, Reseller, or Agency Hosting platform.
Accounts exceeding approximately 1,000,000 inodes may be better suited to:
Semi-Dedicated Hosting
VPS Hosting
VDS Hosting
Other dedicated-resource environments
Multi-million inode workloads are generally considered specialized workloads and may require Semi-Dedicated or isolated resources.
A large number of files can affect server operations even when the files themselves consume relatively little disk space.
High inode usage can increase the time and resources required for:
Backups
Backup indexing
Restores
Malware scanning
File-integrity scanning
Security scanning
Account migrations
File searches
Directory traversal
Metadata operations
Ownership changes
Permission changes
cPanel account packaging
Email processing
Filesystem maintenance
Account statistics
Disaster recovery operations
For this reason, inode usage is evaluated together with the characteristics of the workload rather than purely as a numerical limit.
PowerEdge, ProEdge, and HyperEdge are designed for workloads requiring substantially greater resources than normal Shared, Reseller, or Agency Hosting.
Semi-Dedicated Hosting may accommodate substantially higher:
CPU usage
Physical memory usage
Disk I/O
Process usage
Traffic levels
Database activity
Storage usage
Inode usage
Semi-Dedicated accounts are not subject to the same standard inode soft thresholds used for other hosting tiers.
There is no single published inode ceiling for Semi-Dedicated Hosting.
High or multi-million inode workloads may be permitted where the workload remains compatible with the hosting platform and available server capacity.
Semi-Dedicated Hosting does not mean that physical server resources are unlimited.
All usage remains subject to:
Available hardware capacity
Server stability
Filesystem health
Backup performance
Security requirements
Reasonable resource use
Impact on other customers
Customers requiring consistently extreme workloads may eventually require a VPS, VDS, dedicated server, or another isolated-resource environment.
Disk space provided with hosting services is primarily intended for content associated with websites, applications, databases, and email hosted through the applicable service.
Permitted normal usage may include:
Website files
CMS installations
Application files
Images
Documents used by websites
Databases
Website-generated content
Application assets
Unless specifically permitted by the applicable service, hosting accounts should not primarily function as:
General-purpose cloud storage
Personal disk storage
Long-term archival storage
Remote computer backups
Device backups
Disk-image repositories
ISO repositories
Software mirrors
General download repositories
Large media archives unrelated to hosted websites
Fusion Arc Hosting may review accounts where storage usage is disproportionate to the actual website or application being hosted.
Customers may create reasonable temporary backups of their websites and applications.
However, hosting account storage should not normally be used to maintain large numbers of historical backup archives.
Examples include:
Repeated full-account backups
Large ZIP or TAR archives
Multiple historical WordPress backup sets
Local copies of remote backups
Database dumps retained indefinitely
Large backup archives can consume significant disk space, inodes, and I/O while also being duplicated by Fusion Arc Hosting’s own backup systems.
Fusion Arc Hosting may ask customers to remove unnecessary historical backups or move them to an external backup platform.
Backup and restore operations may temporarily consume substantial resources.
Fusion Arc Hosting generally permits reasonable backup activity.
However, automated applications or plugins should not perform continuous or excessively frequent full-account backups that materially affect server performance.
Examples may include backup systems that repeatedly:
Compress the entire website
Export large databases
Scan millions of files
Create large temporary archives
Upload large backup sets
Delete and regenerate full backup archives
Customers with unusually large backup requirements may be asked to reduce backup frequency or use an external backup system.
Where a hosting plan includes large or unlimited bandwidth allocations, such usage remains subject to fair use.
Normal bandwidth usage may include:
Website traffic
API traffic
Application downloads
Images
Website assets
Streaming associated with normal website functionality
Email traffic
Shared web hosting services should not primarily be used as:
Public file distribution networks
High-volume software mirrors
Peer-to-peer distribution systems
Dedicated video streaming platforms
Dedicated CDN nodes
Large download repositories
High bandwidth usage alone does not automatically violate this policy.
Fusion Arc Hosting generally reviews bandwidth when its volume, purpose, or traffic characteristics create an abnormal impact on the hosting platform or network.
Applications may establish outbound network connections where supported.
However, customers must not use shared hosting accounts to generate excessive network connections or connection rates.
Examples that may require review include:
High-volume web scraping
Continuous API polling
Automated scanners
Large numbers of simultaneous outbound connections
Port scanning
Network probing
Proxy services
VPN services
Traffic relays
Automated attacks
Denial-of-service activity
Shared hosting is not designed to operate as a general-purpose network server.
MySQL, MariaDB, or other supported database resources are intended to support websites and applications hosted on the applicable account.
Database workloads may be reviewed based on:
Query frequency
Concurrent connections
Query execution time
CPU consumption
Memory consumption
Temporary table creation
Disk I/O
Database size
Lock contention
Slow queries
Overall server impact
Large databases are not automatically prohibited.
However, poorly optimized database workloads can consume disproportionate resources even where the database itself is relatively small.
Fusion Arc Hosting may recommend:
Database optimization
Index improvements
Application optimization
Caching
Query changes
Plugin replacement
Database cleanup
Migration to a higher-resource platform
Applications should use database connections efficiently.
Accounts should avoid unnecessary persistent or excessive simultaneous database connections.
Applications repeatedly exhausting available database connections may require optimization or additional resources.
Fusion Arc Hosting may temporarily limit problematic database activity where required to maintain database-server stability.
Cron jobs are permitted for legitimate website and application functions.
Examples include:
WordPress scheduled tasks
Billing automation
Application maintenance
Database cleanup
Scheduled imports
Scheduled exports
Cache maintenance
Cron jobs should not run more frequently than reasonably necessary.
Extremely frequent, overlapping, continuously executing, or resource-intensive cron jobs may be reviewed.
Customers should ensure that a new cron execution does not continually start while a previous execution remains active.
Sub-minute or continuously looping scheduled workloads are generally unsuitable for shared hosting unless specifically supported by the applicable service.
Fusion Arc Hosting may support PHP, Node.js, Python, and other application environments depending on the service.
Applications must operate within the resources assigned to the hosting account.
Applications should not attempt to:
Bypass resource controls
Escape account isolation
Circumvent CloudLinux restrictions
Launch unrestricted system daemons
Bind to unauthorized ports
Modify system-level configuration
Access another customer’s files
Consume disproportionate server resources
Long-running applications may be permitted where supported by the hosting platform and plan.
Applications requiring persistent high-resource workers, large memory footprints, custom services, unrestricted system access, or specialized operating-system configuration may require VPS, VDS, or dedicated infrastructure.
Caching is encouraged where appropriate because it can substantially reduce CPU, database, and application resource usage.
Customers using applications such as WordPress are encouraged to use compatible caching technologies.
However, cache systems themselves should not generate unreasonable filesystem activity or uncontrolled numbers of cache files.
Large or continuously regenerated cache trees may be reviewed if they materially affect:
Inode consumption
Filesystem performance
Backups
Security scanning
Disk I/O
Email hosted through a cPanel account contributes to the account’s:
Disk usage
Inode usage
Backup size
Security scanning workload
Filesystem activity
A large mailbox may contain hundreds of thousands or millions of individual files depending on the mail storage format.
Customers maintaining unusually large quantities of historical email may be encouraged to:
Archive older email
Remove unnecessary messages
Use dedicated email services
Upgrade to a hosting environment designed for the workload
Email storage is evaluated as part of overall account resource consumption.
Hosting accounts may send legitimate transactional, personal, business, or website-generated email.
Customers must not use Fusion Arc Hosting services for unsolicited bulk email or other prohibited messaging activity.
Fusion Arc Hosting may impose reasonable sending limits to:
Protect server reputation
Prevent spam
Prevent compromised accounts from sending large volumes of email
Maintain deliverability
Protect shared IP addresses
Reduce abuse
Sending limits may be applied at levels including:
Individual sender
Domain
cPanel account
Server
IP address
Sending limits may vary depending on the service and reputation conditions.
Customers sharing outbound mail infrastructure also share responsibility for maintaining its reputation.
Fusion Arc Hosting may restrict, temporarily suspend, reroute, or investigate outbound email where activity creates a material risk to:
IP reputation
Domain reputation
Spam-blocklist status
Email deliverability
Other customers
Accounts compromised and used to send spam may be temporarily restricted while the compromise is investigated and corrected.
Accounts generating unusually large mail queues or receiving abnormal quantities of abusive mail may be reviewed.
Fusion Arc Hosting may take reasonable steps to protect mail-server stability, including:
Rate limiting
Rejecting abusive connections
Blocking malicious senders
Temporarily restricting compromised mailboxes
Adjusting mail routing
Malware and compromised accounts can generate extreme CPU, process, I/O, email, and network usage.
Fusion Arc Hosting may immediately take protective action where an account:
Contains active malware
Participates in attacks
Sends spam
Hosts phishing content
Executes malicious scripts
Attempts lateral movement
Scans external networks
Threatens server stability
Threatens customer data
Protective actions may include:
Killing malicious processes
Blocking scripts
Quarantining files
Restricting outbound connections
Temporarily disabling affected functionality
Temporarily suspending the account
Where reasonably possible, Fusion Arc Hosting will work with the customer to restore normal service once the security issue has been corrected.
Fusion Arc Hosting may perform security, malware, file-integrity, or reputation scanning to protect customers and infrastructure.
Accounts containing extremely large numbers of files, archives, or frequently changing filesystem objects may require substantially more scanning resources.
Security scanning impact may therefore be considered when evaluating whether an account remains appropriate for a particular service tier.
Normal search-engine crawlers and legitimate automated traffic are permitted.
However, accounts may experience resource exhaustion due to:
Aggressive crawlers
AI crawlers
Scrapers
Brute-force activity
Vulnerability scanners
Automated login attempts
Malicious bots
Customers are encouraged to implement reasonable bot management, caching, rate limiting, or security controls.
Where automated traffic repeatedly consumes disproportionate resources, Fusion Arc Hosting may assist with mitigation or recommend additional protection.
Fusion Arc Hosting understands that websites may experience unexpected popularity or traffic spikes.
Short-duration spikes are generally treated differently from continuously excessive resource consumption.
We will generally attempt to allow legitimate temporary spikes where server capacity permits.
If traffic levels become sustained beyond the appropriate service class, we may recommend migration to a service with additional resources.
Accounts that become the target of denial-of-service activity may consume substantial network or server resources.
Fusion Arc Hosting may take temporary protective measures where necessary, including:
Filtering traffic
Blocking sources
Rate limiting
Temporarily disabling affected services
Moving or isolating services where practical
Where attacks become persistent or unusually large, additional mitigation services or alternative infrastructure may be required.
Unless a service specifically permits them, shared hosting accounts are not intended for workloads whose primary purpose is general computation rather than website hosting.
Examples may include:
Cryptocurrency mining
Password cracking
Hash cracking
Large scientific computation
Distributed computing
Machine-learning model training
Continuous video encoding
Continuous media transcoding
General-purpose compute farms
These workloads may require VPS, VDS, dedicated servers, or specialized infrastructure.
Hosting services may be used to provide files normally associated with a customer’s website.
However, standard cPanel hosting should not primarily function as a public file-hosting service where the majority of server activity involves storage and distribution of large files unrelated to the hosted website.
Fusion Arc Hosting may review workloads involving:
Very large public download libraries
Software distribution
Large archives
Disk images
Installer repositories
Media repositories
Reseller Hosting is designed to allow customers to host and manage multiple cPanel accounts.
Fair usage may be evaluated both:
Per individual cPanel account
Across the reseller service as a whole
A reseller account may contain many normal websites without issue.
However, a single unusually large cPanel account may exceed the workload characteristics appropriate for Reseller Hosting even where the reseller’s total storage allocation has not been exhausted.
Fusion Arc Hosting may recommend moving individual high-resource accounts to Semi-Dedicated, VPS, or VDS hosting while allowing the remaining reseller accounts to remain unchanged.
Olympus, Zenith, and Aether plans are intended for agencies, developers, organizations, and customers managing multiple websites or cPanel environments.
These plans generally provide greater flexibility than entry-level shared hosting.
However, Agency & Enterprise Hosting remains a shared infrastructure service.
A large aggregate storage allocation does not mean that a single cPanel account is automatically suitable for:
Multi-million inode workloads
Extremely high sustained CPU
Extremely high database activity
Large persistent application workers
Heavy filesystem workloads
Specialized compute workloads
Particularly large individual workloads may be better suited to Semi-Dedicated Hosting or isolated infrastructure.
Fusion Arc Hosting may consider total resource consumption across related accounts hosted under the same service.
For example, a reseller or agency account containing many individual cPanel accounts may be reviewed where the combined workload materially affects the parent server.
This review may consider:
Aggregate CPU
Aggregate memory
Aggregate I/O
Aggregate processes
Aggregate storage
Aggregate inode usage
Aggregate network usage
The presence of many individually compliant accounts does not automatically make unlimited aggregate resource consumption appropriate for a shared platform.
Hosting accounts are generally permitted to temporarily burst into available resources where supported by the applicable service and infrastructure.
Burst usage may occur during:
Traffic spikes
Software updates
Administrative activity
Cache rebuilding
Application deployments
Database maintenance
Burst capacity should not be interpreted as guaranteed continuously available dedicated capacity.
A workload that permanently requires burst-level resources may require migration to a higher service tier.
Fusion Arc Hosting may recommend optimization before recommending an upgrade.
Possible optimization steps may include:
Enabling caching
Removing unnecessary plugins
Optimizing databases
Correcting application loops
Adjusting cron schedules
Removing obsolete files
Cleaning old cache directories
Archiving old email
Removing unnecessary backups
Blocking abusive bots
Updating software
Correcting broken scripts
Improving database indexing
Customers are not automatically required to upgrade merely because a resource threshold has temporarily been exceeded.
Fusion Arc Hosting may monitor infrastructure and account-level resource metrics for purposes including:
Capacity planning
Security
Abuse prevention
Performance analysis
Troubleshooting
Fair usage enforcement
Infrastructure health
Monitoring may include server-level and account-level measurements.
Fusion Arc Hosting does not guarantee that every resource condition will be detected immediately.
Where unusually high resource usage is identified, Fusion Arc Hosting may review:
The resource being consumed.
Whether the usage is temporary or sustained.
Whether the workload is legitimate.
Whether the application appears compromised.
Whether optimization can reasonably correct the issue.
Whether additional capacity can safely be provided.
Whether another Fusion Arc Hosting service is more appropriate.
Where possible, we aim to resolve resource concerns cooperatively with the customer.
Fusion Arc Hosting may increase soft resource thresholds for legitimate workloads when:
Adequate server capacity exists
The workload remains appropriate for the service
Other customers are not adversely affected
Platform stability is maintained
Approval of one increase does not create a guarantee that future increases will also be available.
Resource availability may change as the customer’s workload grows.
Fusion Arc Hosting may temporarily restrict an account where immediate action is required to protect infrastructure.
Examples include:
Runaway processes
Severe resource exhaustion
Malware
Spam outbreaks
Compromised websites
Denial-of-service activity
Network scanning
Excessive database load
Severe filesystem activity
Where practical, restrictions will be limited to the affected service, process, script, domain, or account rather than broader service disruption.
Suspension is generally considered a last resort for fair-usage concerns.
Suspension may nevertheless be necessary where:
Usage creates an immediate threat to server stability
Security has been compromised
Abuse is occurring
A customer repeatedly ignores resource notifications
The workload materially impacts other customers
Continued operation creates infrastructure or network risk
Fusion Arc Hosting may act without advance notice when immediate intervention is required to protect infrastructure or customers.
Where a workload has legitimately outgrown its current hosting class, Fusion Arc Hosting may recommend migration to:
A higher Shared Hosting tier
Agency Hosting
Semi-Dedicated Hosting
VPS
VDS
Dedicated infrastructure
Another appropriate service
Such recommendations are based on the technical characteristics of the workload rather than solely on one usage metric.
Where a Fusion Arc Hosting service is described as “unlimited” or “unmetered,” the term means that Fusion Arc Hosting does not apply a predetermined fixed usage quota for that resource under normal operation.
It does not mean that the underlying physical infrastructure provides infinite capacity.
Unlimited or unmetered resources remain subject to:
This Fair Usage Policy
Physical hardware limitations
Network capacity
Security controls
Service-specific technical limitations
Reasonable use
Platform stability
All hosting services ultimately operate on physical infrastructure with finite:
CPU capacity
Memory
Storage
I/O performance
Network capacity
Filesystem capacity
Fusion Arc Hosting attempts to provide sufficient capacity and reasonable operating headroom across its infrastructure.
However, no hosting provider can provide literally infinite physical resources.
Fair usage exists to ensure that available resources remain reasonably distributed among customers using shared infrastructure.
Unless explicitly stated otherwise in a service description or applicable agreement, exceeding a soft threshold does not by itself constitute a policy violation.
Fusion Arc Hosting considers:
Severity
Duration
Frequency
Cause
Customer behavior
Technical impact
Server capacity
Whether the usage is reasonable for the service purchased
This allows legitimate high-traffic or high-resource customers to operate without unnecessary restrictions while still protecting the shared hosting environment.
Fusion Arc Hosting reserves the right to take immediate technical action where necessary to protect:
Server availability
Customer data
Network security
Email reputation
Filesystem health
Backup systems
Databases
Other customers
Fusion Arc Hosting infrastructure
Emergency measures may be taken before customer notification where delaying action would materially increase risk.
Customers are expected to reasonably cooperate with Fusion Arc Hosting when a legitimate resource or security issue is identified.
This may include:
Updating applications
Correcting scripts
Removing malware
Disabling problematic plugins
Adjusting cron jobs
Cleaning unnecessary data
Reducing abusive automated traffic
Working with developers
Migrating workloads that have outgrown the platform
Fusion Arc Hosting will attempt to provide reasonable information regarding the identified issue.
Fusion Arc Hosting intends this Fair Usage Policy to protect customers and infrastructure, not to penalize legitimate growth.
Customers acting in good faith will generally be given reasonable opportunities to:
Understand resource concerns
Correct inefficient usage
Request additional capacity
Discuss alternative hosting options
Where a workload is legitimate but has outgrown its current hosting plan, our preferred resolution is to help the customer move to an appropriate environment rather than unnecessarily interrupt the service.
Customers must not intentionally attempt to bypass or interfere with resource controls.
Prohibited circumvention may include:
Evading CloudLinux limits
Running processes under unauthorized users
Exploiting system vulnerabilities
Bypassing filesystem isolation
Circumventing mail limits
Disabling security controls
Attempting unauthorized privilege escalation
Manipulating resource-monitoring systems
Intentional circumvention may result in immediate restriction or suspension.
Certain Fusion Arc Hosting products may include resource allowances or capabilities different from the general standards in this policy.
Where an individual service description, contract, custom agreement, or written Fusion Arc Hosting authorization provides different terms, those specific terms may take precedence for that service.
Unused server capacity may sometimes allow customers to temporarily consume resources above typical operating levels.
The availability of unused capacity at one time does not create a permanent entitlement to that additional capacity.
Infrastructure utilization changes over time as:
Customer traffic changes
Accounts are added or removed
Server workloads change
Security events occur
Maintenance is performed
Fusion Arc Hosting may therefore review workloads that previously operated without issue if their resource requirements later materially affect platform stability.
Fusion Arc Hosting actively monitors platform utilization and may:
Add capacity
Upgrade infrastructure
Rebalance workloads
Migrate accounts
Modify resource allocations
Adjust service configurations
These actions may be performed as part of routine platform management.
A fair-usage review does not necessarily mean that a customer has done anything wrong.
In many cases, a review simply means that:
A website has grown
Traffic has increased
A database has expanded
Email storage has grown
An application has become more demanding
The customer’s technical requirements have changed
Fusion Arc Hosting will generally work with customers to determine the most appropriate technical solution.
Fusion Arc Hosting may modify the technologies or systems used to deliver hosting services.
This may include changes to:
Server hardware
Operating systems
Control panels
Web servers
PHP versions
Database systems
Security systems
Resource-control systems
Backup systems
Networking
Storage architecture
Such changes may alter how particular resource measurements are technically implemented without fundamentally changing the purpose of this Fair Usage Policy.
Fusion Arc Hosting may exercise reasonable technical discretion when applying this policy.
Every workload is different.
Two accounts consuming the same amount of storage or the same number of inodes may have very different effects on a server.
Accordingly, Fusion Arc Hosting may consider the total technical characteristics of an account when determining whether usage remains suitable for its current hosting environment.
Fusion Arc Hosting may amend this Fair Usage Policy as:
Products change
Infrastructure changes
Technology changes
Abuse patterns evolve
Operational requirements change
New services are introduced
Material changes may be communicated through:
The Fusion Arc Hosting website
Customer portal
Service notices
Other reasonable communication methods
Continued use of Fusion Arc Hosting services remains subject to the current applicable policies and Terms of Service.
Customers who expect unusually high resource usage are encouraged to contact Fusion Arc Hosting before deploying the workload.
Our team can help determine whether the workload is best suited for:
Shared Hosting
Reseller Hosting
Agency & Enterprise Hosting
Semi-Dedicated Hosting
VPS
VDS
Another hosting environment
Customers may also contact Fusion Arc Hosting Support to request review of a soft resource threshold or discuss an existing resource concern.
Fusion Arc Hosting’s goal is to provide customers with sufficient room to operate and grow while protecting the reliability, security, and performance of the hosting platform for everyone.
