7 Signs It's Time to Switch Hosting Providers
Changing hosting providers is something most people put off. The hassle of migrating, the fear of downtime and the thought that "it's good enough" get in the way. Yet a slowing site loses visitors, frequent outages erode customer trust and unresolved technical problems quietly eat up your time.
In this guide, we cover 7 signs that it's time to change hosting providers. For each sign, we explain what it looks like, its impact on your business, how to measure it with your own data and how to tell whether the problem really comes from the provider. Then you'll find which type of hosting to move to, which questions to ask providers and the steps for a seamless migration.
A single bad day isn't a reason to switch. If two or three of the signs below keep recurring for weeks and your provider can't offer a written, lasting solution, it's time to consider another hosting solution. Base your decision on the measurements you collect, not on gut feeling.
- First, the Right Diagnosis: Is the Problem Really the Hosting?
- 1. The Site Is Frequently Unreachable
- 2. The Site Is Slow and It's Not Your Fault
- 3. Support Is Slow or Superficial
- 4. Your Site Has Hit Its Plan Limits
- 5. Security and Updates Are Neglected
- 6. Pricing Isn't Transparent
- 7. Backup and Recovery Aren't Reliable
- Decision Checklist: How Many Signs Do You See?
- Which Type of Hosting Should You Move To?
- Questions to Ask Providers
- A Safe Migration Plan
- Frequently Asked Questions
- Conclusion
First, the Right Diagnosis: Is the Problem Really the Hosting?
Changing hosting is a demanding decision; made on a wrong diagnosis, the problem moves to the new server too. So before moving on to the signs, you need to identify where the problem starts. The basic logic is simple: if the same symptom continues when your site is changed, the problem is most likely in the infrastructure.
Quick isolation tests
- Static file test: Measure the response time of an image or a simple
.txtfile on your site. These files don't depend on your application code; if they're slow too, the problem is on the server or network side. - Clean install test: If you use a system such as WordPress, activate the default theme and temporarily disable plugins (preferably on a copy). If the speed or error improves, the problem is in your site.
- Time pattern: Does the problem occur at the same times every day? Slowness limited to peak hours points to insufficient resources, while outages at random times point to infrastructure instability.
- Location test: Try accessing the site from several different networks and cities. If the problem occurs only in certain regions, routing or the server location comes into question.
Keep a problem log. Collect the date, time, symptom, measurement result and the report you made to the provider in a single table. This record both strengthens your diagnosis and puts you at the table with "data" rather than "gut feeling" when talking to the support team.
The Site Is Frequently Unreachable
Any infrastructure can have short outages from time to time. The warning sign is outages that recur, follow a certain pattern, or that the provider doesn't explain.
Downtime in numbers
Uptime percentages look small, but their monthly equivalents are anything but:
- 99.9% uptime equals about 43 minutes of downtime per month.
- 99.5% uptime means about 3.5 hours of downtime per month.
- 99% uptime means more than about 7 hours of downtime per month.
For an e-commerce site or a corporate site that takes appointments, which hours these periods fall on matters more than the total. Ten minutes of downtime during a campaign costs more than an hour of downtime at midnight.
How do you measure it?
- Set up an independent uptime monitoring service and have it monitor your site at 1β5 minute intervals for at least 2β4 weeks.
- Monitor not only the home page but also a page that touches the database (search, cart or login page). The home page may be served from the cache while the application has crashed in the background.
- Add the date, duration and the provider's response to your outage records.
- Look at the HTTP status codes. Recurring 502, 503 and 504 errors usually point to server or load problems.
Is the problem on the server or on your side?
If an outage affects several separate sites at the same time (for example, if you have multiple domains on the same account), the cause is most likely on the server side. If only one site goes down, the cause could also be a faulty plugin, a full disk, an exceeded memory limit or an expired component.
Testing an outage only from your own browser is misleading. Your local connection, DNS cache or browser extensions can affect the result. Leave the monitoring to a service that measures from different locations.
Decision threshold
If you've had more than one outage longer than a few minutes in the last 1β2 months and your provider hasn't explained the cause and the measures taken in writing, this sign is confirmed.
The Site Is Slow and It's Not Your Fault
Slowness is the most common and most misdiagnosed problem. Visitors may leave the site while waiting for the page to load, and slow sites also produce negative signals in search engine experience metrics. What you need to determine here is whether the slowness comes from the page itself or from the time it takes the server to start responding.
What is TTFB and why does it matter?
TTFB (Time To First Byte) is the time from the browser sending a request to receiving the first byte from the server. The images, scripts and theme on the page don't affect this time much; what really determines it is how quickly the server starts producing the response. web.dev considers a TTFB under 0.8 seconds good and over 1.8 seconds poor.
How do you measure it?
A single measurement can be misleading. The command below requests the page 10 times and prints the TTFB value in seconds each time. Use your own domain instead of example.com:
for i in $(seq 1 10); do curl -o /dev/null -s -w "%{time_starttransfer}\n" https://example.com; done
In Windows PowerShell, curl is an alias for another command, so use curl.exe:
1..10 | ForEach-Object { curl.exe -o NUL -s -w "%{time_starttransfer}\n" https://example.com }
Repeat the measurement in the morning, in the afternoon and during evening peak hours. Note the differences between the numbers and the highest value. Remember that cached responses may be slow on the first request and fast on subsequent ones.
Signs that suggest the problem is on the server
- TTFB is consistently above 1 second even with caching enabled and unnecessary plugins disabled.
- Values rise noticeably at peak hours and drop at night.
- Even a static image file arrives late.
- On shared hosting, processes are queued or throttled during busy periods because of resource limits.
- Network latency is high because the server is far from the region where most of your visitors are.
Caching, image optimization and using a CDN greatly improve page load time, but they don't always fix the server's own response time. If TTFB is still high after applying these measures, the problem is much more likely to be in the infrastructure.
Decision threshold
If, after applying the improvement measures, TTFB stays above 1β1.5 seconds for many hours of the day and the provider can't explain it, this sign is confirmed.
Support Is Slow or Superficial
The real quality of a hosting service shows when something goes wrong. A support team you don't notice on normal days becomes part of your business continuity during an outage. When support goes unanswered, a technical problem turns into a business problem.
Typical signs of poor support
- Your ticket goes unanswered for days, or the first response time isn't clearly stated.
- Responses are made up of template sentences and contain no findings specific to your problem.
- The problem is said to be "resolved", but the root cause isn't explained, and the same problem recurs a few days later.
- You have to explain the same issue several times or start over with a new person each time.
- There's no clear communication channel or priority system for emergencies.
How do you test support quality?
You don't have to wait for a problem to occur. Send your current or prospective provider a question whose answer genuinely requires technical knowledge. For example, you could ask what a specific error log entry means, how to increase the PHP memory limit or how to restore a single file from a backup. Look at three things:
- Speed: How long did the first response take?
- Depth: Does the answer understand your question and give concrete guidance?
- Consistency: Do you get the same quality of answer to a follow-up question?
Decision threshold
If you can't get a written response within an acceptable time for an important problem, or you can't get an explanation of the root cause of the same problem twice, this sign is confirmed. Support quality is a more decisive criterion than price, especially for site owners with limited server administration knowledge.
Your Site Has Hit Its Plan Limits
As visitor numbers, product counts or the database grow, a plan that was enough at the start becomes insufficient. That isn't the provider's fault; it's a sign that your business is growing. But running into the limits every month isn't a sustainable model.
Signs that you've hit the limits
- On some platforms, you get resource limit errors such as 503 or "Resource Limit Is Reached" (508).
- The CPU, memory, disk I/O or concurrent process limits in the panel look constantly full.
- The site slows down or goes down during campaigns, launches or seasonal peaks.
- You're approaching the file count (inode) or database size limits.
- The provider keeps saying "upgrade to a higher plan" to solve the problem but can't clearly explain what the higher plan will change.
First: are you really the one exceeding the limit?
Your resource usage may be inflated by a plugin, a broken script or heavy crawling by bots. Review the resource graphs and access logs in the panel. Upgrading a plan without distinguishing between a healthy traffic increase and uncontrolled bot traffic may mean throwing money at the problem.
Decision threshold
If you're still getting limit errors every week even after optimization, it's time to move to the next level of hosting. If you're looking for a setup where resources are dedicated only to you, you can review the VDS server options in the hosting types section.
Security and Updates Are Neglected
Security is a shared responsibility between you and the provider. The provider's side is keeping server software up to date, isolating accounts from each other, basic network-level protections and transparent communication during security incidents. Your side is keeping your application, plugins and passwords up to date and strong.
Warning signs on the provider side
- Only PHP versions whose official support has ended can be selected in the panel, or moving to a current version isn't possible.
- Installing an SSL certificate is difficult, costs extra or has to be renewed manually all the time.
- Your site gets reinfected with malware shortly after being cleaned, and the provider doesn't investigate the root cause.
- During a security incident, you aren't given concrete information backed by logs.
- There's a suspicion that other accounts on the same server can access your files, and the provider doesn't take it seriously.
Check the SSL status yourself
You can see the certificate's validity dates with the following command. The notAfter line shows when the certificate expires:
echo | openssl s_client -connect example.com:443 -servername example.com 2>/dev/null | openssl x509 -noout -dates
The cause of recurring infections is often old plugins, weak passwords or stolen accounts. Before changing hosting, clean the site and renew all passwords. Otherwise, you'll move the problem to the new server too.
Decision threshold
Outdated software on the provider side, recurring and unexplained security incidents or a suspicion of poor isolation can be enough of a reason on their own. Unlike the others, this sign is the one that tolerates waiting the least.
Pricing Isn't Transparent
A low introductory price looks attractive; the problem is when that price multiplies on renewal and this wasn't clearly stated up front. A high price isn't a problem in itself. Uncertainty is.
Check your contract and invoices
- How different is the renewal price from the introductory price, and was that difference visible when you bought?
- Are services that seem basic, such as SSL, backups, migration support, additional IPs or domain privacy, charged separately?
- Are the cancellation and refund terms clearly written? Is cancelling deliberately made difficult?
- When you exceed resource limits, are extra fees, automatic plan upgrades or service restrictions applied?
- Are the invoice items understandable, or do you face a different surprise every billing period?
How do you compare correctly?
Look at the total cost over 2β3 years, not the monthly price. A plan with a low introductory price that becomes expensive on renewal can end up costing more than a higher but fixed-price plan. Include items added later, such as backups, SSL and migration, in the comparison.
Decision threshold
If you can't anticipate price changes, or the real cost of the service can't be worked out from the contract text, this sign is confirmed. Price alone is almost never a sufficient reason. A low price becomes meaningful when combined with the other signs above.
Backup and Recovery Aren't Reliable
A backup is an invisible service until you need it. When an update breaks the site, a file is accidentally deleted or the server fails, realizing that there's no backup, that it's old or that it can't be restored is the most expensive lesson.
Warning signs
- You don't know whether automatic backups are taken, how often or how many days they're kept.
- You can't restore a backup on your own and have to open a support ticket every time.
- Backups are kept on the same server; if the server fails, the backups are lost too.
- The backup contains only files, not the database or emails.
- You've never tried a restore.
What does a good backup strategy look like?
- Automatic and regular: The frequency should match how quickly your site changes. Hourly or daily backups may suit a store that takes orders every day, while weekly backups may be enough for a brochure site that's rarely updated.
- Independent of the server: At least one copy should be stored in a location outside the hosting.
- Tested: Restores should be tried in a test environment at regular intervals.
- Comprehensive: Files, databases and, if needed, emails should be backed up together.
No matter how good the provider's backups are, keep an up-to-date copy of your site under your own control. A backup that has never been test-restored doesn't count as a reliable backup.
Decision threshold
If the provider's backup policy is unclear, you depend on a support ticket to restore and you have no alternative, this sign is confirmed. Backups alone may not be a reason to move, because you can cover the gap with your own backups. But combined with the other signs, they increase the risk.
Decision Checklist: How Many Signs Do You See?
Count a sign for each item below that you can answer "yes" to. This isn't a scientific scale; it's a practical method to help you structure your decision.
- β In the last 1β2 months, I've had more than one outage longer than a few minutes, and the cause wasn't explained.
- β Despite optimization, my TTFB is above 1β1.5 seconds for many hours of the day.
- β For an important problem, I didn't get a technically satisfying answer from support within an acceptable time.
- β Even after optimization, I regularly get resource limit errors.
- β I have concerns about outdated software, recurring infections or isolation.
- β I can't clearly anticipate the renewal price, extra fees or cancellation terms.
- β I'm not sure my backup exists, what it covers or whether it can be restored.
How do you interpret the result?
- 0β1 signs: There's no strong reason to move. Keep measuring and follow developments.
- 2β3 signs: Start evaluating alternatives. Ask your current provider for a written solution and date for the problems; factor the answer into your future decision.
- 4 or more signs: It's time to plan the migration. Run the process in a controlled way by following the migration plan below.
Some signs carry more weight regardless of the count. Situations such as recurring security incidents or running without backups may require urgent action on their own.
Which Type of Hosting Should You Move To?
Once you decide to change providers, the second decision is which type of service to move to. Choosing the wrong type means living with the same problems on a new invoice. The summary below offers a starting point based on your needs.
- Shared web hosting: Suitable for corporate brochure sites, blogs and low-to-medium traffic sites. It's the most practical option for users who don't want to deal with server management. You can take a look at our web hosting plans.
- WordPress hosting: A service configured for the specific needs of WordPress sites. If your site runs entirely on WordPress, you can review the options on our WordPress hosting page.
- VPS server: Suitable for projects that require root access and flexible configuration. The extent to which resources are dedicated to you may vary by provider, so always ask whether resources are guaranteed. For options, see our VPS server page.
- VDS server: Provides full control with resources dedicated to you. Suitable for applications where performance needs to be predictable. It requires server management knowledge; for the initial setup, you can use our Ubuntu VDS initial setup guide. For plans, take a look at our VDS server page.
- Dedicated server: A setup where all the hardware belongs to you alone. Preferred for projects with high traffic, heavy database loads or special compliance requirements. For details, see our dedicated server page.
- Reseller hosting: For agencies and developers who want to offer hosting to their own customers. You can find out more on our reseller hosting page.
If you don't want to manage a server, products with root access (VPS, VDS, dedicated) leave you alone with the responsibility for updates, security and monitoring. Decide from the start whether you'll use a plan where the provider takes on management or a server you'll manage yourself.
Questions to Ask Providers
Before deciding to move, it's worth giving your current provider a chance to fix things, and before choosing a new provider, asking the right questions. Asking for written answers makes what you're told verifiable.
To your current provider
- What is the root cause of the outages and slowdowns I've reported, and what measure will be taken by which date?
- What resource limits are defined for my account, and what percentage of those limits am I using?
- How often are my backups taken, where are they stored and can I restore them myself?
- What are the renewal, cancellation and refund terms of my contract?
To a new provider
- In which data center, in which country and on what infrastructure is the service provided?
- Are resources shared or dedicated to you? Is this written into the contract?
- Is there a service level (SLA) commitment, and what happens if it's breached?
- What is the backup policy, and how is a restore done?
- Is migration support provided, and if so, what is its scope and cost?
- Through which channels, during which hours and with which target response times is support provided?
- What is the renewal price, and is the price fixed?
- How can I move to a higher service when my needs grow?
There can be a difference between the statements on a provider's marketing page and the contract text. Look for promises such as uptime, backups or resource guarantees in the contract and service level documents; if you can't find them, ask for written confirmation.
A Safe Migration Plan
Done in the right order, a migration goes through without downtime. When the order breaks down, you may face lost email, a few hours of access problems or data inconsistencies. The plan below offers a framework for small and medium-sized sites.
1. Preparation (1β2 weeks before the migration)
- List all domains, subdomains, email accounts, cron jobs and databases on the site.
- Note your current PHP, MySQL/MariaDB and plugin versions. Choose compatible versions on the new server.
- Take a full backup: site files, databases and emails.
- List the external services you use (payment gateways, API keys, IP restrictions). When the new server's IP address changes, you'll need to update some of these.
2. Copying and testing (3β7 days before the migration)
- Copy the site to the new server.
- Test the site on the new server before changing DNS. At this stage, make sure search engines don't index the temporary address.
- Try the forms, checkout flow, login system, email sending and cron jobs.
To test the new server without touching DNS, you can use the --resolve option of curl. This command temporarily resolves the domain to the new server's IP address. Replace 203.0.113.10 in the example with your new server's IP address:
curl -I --resolve example.com:443:203.0.113.10 https://example.com
If you'd like to test in a browser, you can add a temporary line to your computer's hosts file. On Windows the file is at C:\Windows\System32\drivers\etc\hosts, and on Linux and macOS at /etc/hosts. Don't forget to delete this line when you finish testing.
3. DNS preparation (24β48 hours before the migration)
The TTL value of your DNS records determines how long a change takes to propagate. At least as long before the migration as the old TTL, lower this value to a short period (for example 300 seconds). You can see the current TTL value with this command:
dig example.com A +noall +answer
The number in the output is the record's TTL value in seconds. On Windows, the nslookup -type=A example.com command can also be used.
4. Migration day
- On sites where data changes frequently (e-commerce, membership, bookings), plan a short maintenance window. That way, orders written to the old server after the data has been copied aren't lost.
- Take a final backup and do a final data sync.
- Point the A record (or the nameservers) in DNS to the new server.
- If your email is on the old server, update the MX records and, if necessary, the SPF and DKIM records for the new server.
- Confirm that the SSL certificate is active on the new server. Many automatic certificate systems can issue a certificate once the domain points to the new server.
5. Post-migration checks
- Test the home page, important inner pages, forms, and the login and checkout flows.
- Confirm that scheduled tasks (cron) are running on the new server.
- Check the email flow by sending and receiving test emails.
- Check whether a
noindextag orrobots.txtrule blocking search engine visibility was left over from testing. - Keep a close eye on uptime monitoring and Search Console crawl errors for a few weeks.
- Keep the old account open for at least one or two weeks and cancel it only after confirming everything works without problems.
Common mistakes
- Starting the migration without a backup.
- Cancelling the old account immediately and missing incoming emails.
- Forgetting to lower the TTL and prolonging propagation.
- Running the site on the new server without noticing an old PHP version or a different configuration.
- Not removing the maintenance mode or
noindexsetting added during testing before going live. - Moving outdated or infected files as they are without cleaning them.
Frequently Asked Questions
Does changing hosting affect SEO?
If you move while keeping your domain and URL structure, the hosting change itself usually doesn't cause a loss of rankings. The risk comes from prolonged downtime, slowness after the move, or a noindex or robots.txt block left over from testing. A properly executed migration can even have a positive effect thanks to faster infrastructure.
Will there be downtime during the migration?
With preparation, downtime can be very short or nonexistent. While DNS propagates, some visitors may reach the old server and some the new one for a while. That's why you should keep the old server running and use a short maintenance window on sites where data changes frequently.
Will I lose my emails?
If you don't move your mailboxes to the new server, old messages stay on the old server. You can transfer existing mail to the new account via IMAP sync or a backup. Because mail arriving within a few hours of changing the MX records may be split between the two servers, don't close the old account right away.
Do I need to move my domain as well?
No. Domain registration and hosting are separate services. To change hosting, updating the DNS pointing (the A record or nameservers) is enough. If you want to bring management together in one place, you can transfer the domain separately.
Can I leave before my contract ends?
This depends on your contract and refund terms. If you can document that the committed service level wasn't met (outage records, correspondence), you can ask the provider for a refund or early cancellation. If there's a legal matter, read the contract text carefully and seek expert advice if needed.
When should I move from shared hosting to a VDS?
A VDS is a sensible step if you constantly get resource limit errors despite optimization, if you need custom software, services or configuration that the shared environment doesn't allow, and if you have the knowledge to take on server management. If you don't have that knowledge, first consider a hosting plan with more resources or a managed solution.
Conclusion
Frequent outages, unexplained slowness, inadequate support, plan limits, neglected security, unclear pricing and unreliable backups: these are the seven signs that it's time to change hosting providers. You don't need to see all of them. If a few have been recurring for weeks and your provider isn't producing a solution, you have enough data to make a decision.
The right approach is this: first confirm with measurements that the problem really is in the infrastructure, choose the hosting type that suits your needs, ask providers written questions and carry out the migration with backups, testing and a gradual DNS switch. That way, changing hosting isn't a risky step but a controlled improvement.
If you're evaluating a new hosting solution for your website, you can explore Netiyo web hosting plans.
Explore Web Hosting Plans