Read the warning before acting
Identify the resource, measured period and plan entitlement before treating a shared-hosting warning as a capacity problem.
A percentage alone does not identify whether storage, traffic or another limit is involved. Disk space, transferred bandwidth and other account restrictions describe different things. Monthly traffic measures transferred data; disk usage measures stored files. Neither warning alone diagnoses a CPU bottleneck. Check the package or service details actually assigned to your account, or ask support for them if the panel does not show a clear entitlement.
DirectAdmin documents disk and bandwidth accounting, while resource throttling is a separate optional capability. Do not infer that a particular Novasean plan includes an add-on, a threshold or a customer-visible graph merely because the software supports it.
If the metric is disk space
Inspect the permitted account’s usage view and compare the total with known files, databases, logs, mail storage and backups where those are included. Different views may update on different schedules; a recently deleted file may not immediately change a displayed total. Preserve a backup and identify an expendable item before deleting it. An old local download is not necessarily the same as a server-side backup that can restore the site.
If usage rises rapidly or the accounting does not match visible files, note the time and ask support to reconcile it. Avoid deleting unknown application directories or mail data just to make a warning disappear.
If the metric is transfer or traffic
Compare the warning period with the account’s reporting period. Traffic can include repeated downloads or automated requests; a single busy day and a persistent trend need different responses. Check authorised access statistics if available, and look for the top paths and timing rather than assuming normal growth or an attack. Do not block broad visitor ranges or disable the site based on an unexplained number.
Ask support which traffic is counted and when the counter resets if the contract or panel is unclear. A plan change should follow a verified pattern and an explicit commercial decision, not a guess from one alert.
Choose a bounded response and confirm it
For identified disposable files, archive or remove only those files after testing recovery. For traffic, review a specific large asset or an identified abusive pattern with the application owner and operator. Record the metric again after the accounting interval allows it to update. If the warning persists despite an explained reduction, provide the original message, before-and-after values and relevant timestamps to support.
A slow page is a separate diagnosis: use the related performance guide to distinguish browser, network, server response and resource evidence. Resource warnings do not identify the slow component by themselves.
For example, a full disk may block new uploads, while a monthly transfer notice refers to traffic. Confirm the panel's measured period and entitlement before deleting files or buying capacity.
Frequently asked questions
Is bandwidth the speed of my connection? In an account usage screen it usually concerns transferred data over a period; the exact accounting comes from the actual service terms and panel.
Should I upgrade immediately? Confirm the resource, trend and entitlement first. An unexplained spike or stale counter may require investigation rather than a larger plan.
Sources and technical references
Related guides
Was this guide helpful?
If you accepted optional analytics, your Yes/No answer and this guide’s page address are sent to Google Analytics. No written feedback is collected. Read our privacy statement or change your choice in .
Need help with your service?
Open your client area or contact Novasean. Describe the symptom and checks you have performed. Keep passwords, recovery codes and private keys out of your message.