Radar has landed - discover the latest DDoS attack trends. Get ahead, stay protected.Get the report
Under attack?

Products

Solutions

Resources

Partners

Why Gcore

  1. Home
  2. Developers
  3. What Does Blacklisted IP Mean? | Procedure to Remove IP From Blacklist

What Does Blacklisted IP Mean? | Procedure to Remove IP From Blacklist

  • By Gcore
  • June 6, 2023
  • 8 min read
What Does Blacklisted IP Mean? | Procedure to Remove IP From Blacklist

Have you recently noticed a sudden drop in website traffic or email deliverability? One possible reason is that your email IP or domain has been added to a blacklist. But you aren’t a hacker or scammer! So what does blacklisted mean in your case? Why has it happened to you, and what can you do to reverse it?

Blacklists are created as a cybersecurity tool to protect end users from ransomware attacks. According to Statista, the most common cause of ransomware infections is spam/phishing emails. This means that your emails have been flagged as a possible origin of spam or phishing. Unfortunately, blacklists don’t always get it right, and sometimes they flag incorrectly.

Being added to a blacklist doesn’t necessarily require engaging in unacceptable or unethical behavior. Your mail server IP or domain can be blacklisted because someone used your credentials for online fraud or spam. Alternatively, you may have unknowingly behaved in a way that systems mark as suspicious. This can happen to anyone running email campaigns for innocent reasons like overusing spam words or forgetting to update their email authentication (DMARC, SPF, and DKIM).

But don’t worry; you can recover your IP and domain. In this article, we will explain the causes of blacklisting in depth, share how to recover from blacklisting, and help you prevent being blacklisted in the future.

What Does Blacklisted Mean?

Blacklisted IP or domain means your mail server IP or domain is associated with suspicious activity on the web. When you get blacklisted, your website traffic may suddenly drop to zero and your prospects or customers may stop receiving your emails. This obviously has major business repercussions, and is a huge headache.

Your mail server and website are interconnected when it comes to blacklisting. If one gets blacklisted, the other might too. Similarly, if a single mail sender associated with your IP is blacklisted, all other mail servers associated with your domain may also be impacted.

How Does an IP or Domain Get Blacklisted?

Blacklists come in two types: public and private.

Public blacklists are usually non-commercial, nonprofit projects that provide databases of suspicious IPs or domains to corporations and security vendors. Examples of well-known public blacklists include Spamhaus, Barracuda, Project Honey Pot, and Spamcop. These are the most common types of blacklists.

Private blacklists are generated by a single organization. That organization limits access to its services and recipients. For example, Microsoft and your ISP both maintain blacklists.

As blacklist operators are most often public entities run by nonprofit organizations, it’s possible for volunteer investigators, subscribers, or email providers to report you. A spam trap is another way that senders with poor email hygiene may inadvertently become blacklisted.

How a spam trap works

Once blacklisted, all organizations that use this list will reject your emails. Here’s how it works:

How organizations source blacklist information

Check If You are Blacklisted

Problems with website traffic and email deliverability can arise for many reasons, not only because you are on a blacklist. So first of all, you need to check if you have actually been blacklisted, or if something else is causing your problem.

We at Gcore offer step-by-step instructions on how to check if your email server IP has been blacklisted against 100 public blacklists. If you don’t know your mail server IP, find that out first.

Common Blacklisting Reasons

Each blacklist operator has its own criteria for listing IPs and domains. Usually, they don’t openly publish them in detail, but there are some reasons that many of them employ in their process. Let’s take a look.

Misconfigured Email Server

SPF, DKIM, and DMARC are authentication protocols you should set up to appear credible for recipient email providers and protect yourself from spoofing. Spoofing is when someone illegitimately sends emails on your behalf (e.g., from your mail server IP) to look credible to email vendors, and then sends spam or other fraudulent content.

If you forgot to set up or update SPF, DKIM, and DMARC records when moving to a new email vendor, you are at risk of getting blacklisted.

Website Security Issues

Blacklist operators monitor the internet and list IPs that host malware-infected websites, participate in ransomware, or contain malicious content such as phishing scams. If your website is vulnerable to hackers and fraudsters, your domain may be flagged by blacklist operators. For example, if you don’t have security software to mitigate attacks, haven’t set up two-factor authentication, or haven’t installed SSL certificates, you’re putting yourself at risk.

Using a Shared IP for Your Domain and Email Server

Two kinds of IPs exist: shared and dedicated. Shared IP addresses are used by multiple users or websites simultaneously, while dedicated IPs are assigned exclusively to a single user or website. Shared IPs are typically free, or far cheaper than dedicated IPs.

While it does not always make financial sense to buy dedicated IP, a shared one puts you at risk of blacklisting. When one of the domains from the network is identified as a spammer, you suffer too.

Spam-Like Emailing Behavior

When running a mass email campaign, you should be careful about how and what you send. Sending legitimate and relevant emails can lead to blacklisting if they meet certain criteria. Here some activities that are considered suspicious and may lead to blacklisting:

  • A spike in the number of emails sent. If you suddenly extend your email list, the legality of their source is questionable. This is similar to payment systems—a sudden, unprecedented, large financial transfer is always going to arouse suspicion.
  • Going over sending limits. Large volumes of emails sent indicate that you may send many unwanted or phishing emails. Many email vendors set a daily limit on emails sent, and exceeding that number can result in blacklisting.
  • You have non-existent emails on your list. In this case, email providers also suspect you get the email addresses via “grey” means—such as purchasing email lists—and don’t care if recipients are interested in your message or will all actually receive it. If you try sending to invalid emails twice, your mail server IP may be blacklisted.
  • Blacklisted websites in your email body. For mailboxes and blacklist operators, this indicates that you have a connection to the suspicious website.

How to Get Your IP Address Off a Blacklist

Step 1. Understand the Reason You Were Blacklisted

Some blacklist operators require evidence that you have fixed the issue that caused blacklisting before they will take you off their list. If you have been blacklisted on multiple lists, this can damage your mail server IP and domain reputation, and the consequences of each subsequent ban can be more severe. You might face a long delisting procedure (3-4 months) or be blocked permanently.

To understand why you were blacklisted, check your mail server IP and domain against several blacklist testers. We suggest starting with MXToolbox, BlacklistAlert, Mail Genius, Mail Tester and IP tracker tool.

MXToolbox “Detail” button gives information on the reasons for blacklisting
Blacklist Alert lists all results for an IP or domain and gives their status, with a “See why” link to discover the reasons for blacklisting

The services will identify which blacklists you are listed in and, in some cases, give the most likely reason. Next, visit the aforementioned mentioned blacklists and look up your IP on their website too. Using several tools allows you to get the most accurate information.

Step 2. Fix the Blacklisting Problem

Once you’ve identified potential blacklisting reason(s), try to resolve them with your IT team or hire external experts to remedy the cause(s). There are additional steps you can take to reverse the blacklisting.

  • Check if the blacklist operator(s) offer(s) any recommendations to resolve the issue.
  • Review whether all senders that email from your domain follow emailing best practices and avoid spamming behaviors.
  • See if there were attempts or incidents of hijacking your domain or spoofing your IP. (If you host your domain on Gcore, you are protected against such incidents by default. Even with a free plan, you’ll receive minimum protection.)
  • If you are using a shared IP, contact the support team of your email vendor or hosting provider. Ask them if there are spamming issues with one of the IPs on the network and find out how they can help you with recovery.

Step 3. Request Delisting

Now that you’ve resolved the blacklisting causes and taken internal steps to improve your reputation, you are ready to request delisting from the relevant blacklisting agency.

The procedure for requesting and waiting for delisting depends on whether the blacklist in question is a self-service or automated blacklist.

  • Self-service blacklists, e.g. Spamhaus. Go to their website and request delisting manually. Fill out the form to request the removal of your IP or domain—keep in mind to remain polite and provide a detailed explanation of what has happened, what you already did to resolve the problem, and what you are planning to do in order to prevent such cases in the future.
  • Automated blacklists, e.g. Uceprotectl1. Follow the same procedure as above, and then wait for 1-2 weeks before they update their system and remove you from the list.

It’s important to know that trusted blacklists won’t ask you to pay for delisting, so beware of scams.

How Long Does It Take to Be Removed from a Blacklist?

Once you’ve requested delisting, it generally takes 1-2 weeks for the request to be actioned if the blacklist has an automatic delisting procedure. Blacklists with self-service removal may be quicker—several hours to days. In some extreme cases—like if you were previously blacklisted, were blacklisted for a severe issue, or have a poor IP or domain reputation—delisting may take up to 3-4 months.

How Can I Prevent My Website from Being Blacklisted?

As you can see, dealing with blacklists is a real headache. It is easier to prevent blacklisting issues upfront rather than experience downtime or even lose clients.

Some effective ways to avoid getting blacklisted include protecting your domain from DNS hijacking, regularly checking your IP and domain registration, having a dedicated IP address for email and domain, and following mass email best practices. Let’s check out each of these in depth.

Protect Your Domain from DNS Hijacking

Your domain might be blacklisted because your website was hacked—for example, through DNS hijacking—and is involved in malicious activities. This is a common problem; in 2022, 28% of 1000 surveyed organizations of different sizes experienced one or more DNS hijacking attacks. Robust security is important for avoiding blacklisting, but also for your reputation and downtime statistics.

Here’s how to get started:

  1. Use server protection software. In the event of an attack, a system blocks the IP address of the server so an attacker cannot continue with the invasion. Gcore offers free protection and enhanced paid options for its servers.
  2. Ensure you have strong passwords to access your DNS account.
  3. Implement two-factor authentication to access your website.
  4. Install SSL certificates so that data transmitted between the user’s browser and your website is encrypted, keeping sensitive information secure.
  5. Keep your CMS, plugins, and other web software updated.
  6. Regularly back up your website’s data in case of a security breach or data loss.

Regularly Check Your IP and Domain Reputation

Monitoring your blacklist situation is a key tactic because it allows you to take immediate action to get unlisted. Fortunately, there are tools that offer blacklist monitoring and instant alerts, including MXToolbox, Barracuda Networks, and Mailgun.

Have a Dedicated IP Address for Email and Domain

A thorough assessment of your specific needs and circumstances is essential before you make the final decision whether to use a dedicated or shared email or domain server. However, some general guidelines can help you make an initial assessment.

For an Email Server

With shared mail server IPs, you are at risk of having reputational and deliverability issues because of other senders. However, a dedicated server is more expensive than a shared option. We recommend going with dedicated mail server IP in the following cases:

  • You send a high volume of emails (say, over 10,000 per day.)
  • You have the human resources to manage your dedicated IP.
  • You can afford a dedicated IP. The price ranges from $2-200 per month.

For a Domain

If one of the domains on shared hosting is compromised, the performance and reputation of others will be damaged too. Some hosting providers (including Gcore) offer protection for shared IPs. If one of the domains experiences attacks, the IP is blocked and hackers can’t damage the reputation of any other domain that uses this IP.

Choose dedicated hosting if:

  • You have the resources to manage your dedicated IP.
  • Your website receives high traffic volumes of up to 100,000 visitors.
  • You manage resource-intensive applications such as databases, video streaming, and gaming platforms.
  • Your website deals with sensitive information and you need the highest level of security.

Follow Mass Email Best Practices

While mass email blacklisting can happen even to the most careful individual in unfortunate and unusual circumstances, some actions that trigger blacklisting are completely avoidable. When it comes to mass emails, blacklisting often happens to individuals who are new to mass emailing or fail to follow best practices. Here’s a checklist to get up to speed before your next campaign:

  • Set up or recheck your email authentication (DMARC, DKIM, and SPF) in your DNS account
  • Use double opt in when collecting emails to verify them and filter interested users
  • Regularly update your email list: watch for hard bounces, remove non-existent emails, and choose email providers that automatically stop sending to hard-bounced email addresses
  • Increase your email list gradually
  • Offer an unsubscribe option, so recipients are unlikely to flag your emails as spam if they no longer want to receive from you
  • Avoid spam-triggering words in your email body
  • Don’t overuse links
  • Avoid blacklisted websites and link shorteners in your email body
  • Segment your email list to send more relevant emails and avoid spam complaints
  • Choose trusted email providers

Conclusion

IP or domain blacklisting is a common problem when actively running mass email campaigns. You don’t need to be a spammer to end up on blacklists. Instead, you might unknowingly have spam-like behaviors or have poor website security.

Usually, you will be able to recover your mail server IP or domain within a week or two by following the simple delisting steps in this article. It’s then important to follow web security and email best practices to avoid future blacklisting occurrences.

If you need better security for your website and apps, check out our recent security blog posts:

Related articles

Pre-configure your dev environment with Gcore VM init scripts

Provisioning new cloud instances can be repetitive and time-consuming if you’re doing everything manually: installing packages, configuring environments, copying SSH keys, and more. With cloud-init, you can automate these tasks and launch development-ready instances from the start.Gcore Edge Cloud VMs support cloud-init out of the box. With a simple YAML script, you can automatically set up a development-ready instance at boot, whether you’re launching a single machine or spinning up a fleet.In this guide, we’ll walk through how to use cloud-init on Gcore Edge Cloud to:Set a passwordInstall packages and system updatesAdd users and SSH keysMount disks and write filesRegister services or install tooling like Docker or Node.jsLet’s get started.What is cloud-init?cloud-init is a widely used tool for customizing cloud instances during the first boot. It reads user-provided configuration data—usually YAML—and uses it to run commands, install packages, and configure the system. In this article, we will focus on Linux-based virtual machines.How to use cloud-init on GcoreFor Gcore Cloud VMs, cloud-init scripts are added during instance creation using the User data field in the UI or API.Step 1: Create a basic scriptStart with a simple YAML script. Here’s one that updates packages and installs htop:#cloud-config package_update: true packages: - htop Step 2: Launch a new VM with your scriptGo to the Gcore Customer Portal, navigate to VMs, and start creating a new instance (or just click here). When you reach the Additional options section, enable the User data option. Then, paste in your YAML cloud-init script.Once the VM boots, it will automatically run the script. This works the same way for all supported Linux distributions available through Gcore.3 real-world examplesLet’s look at three examples of how you can use this.Example 1: Add a password for a specific userThe below script sets the for the default user of the selected operating system:#cloud-config password: <password> chpasswd: {expire: False} ssh_pwauth: True Example 2: Dev environment with Docker and GitThe following script does the following:Installs Docker and GitAdds a new user devuser with sudo privilegesAuthorizes an SSH keyStarts Docker at boot#cloud-config package_update: true packages: - docker.io - git users: - default - name: devuser sudo: ALL=(ALL) NOPASSWD:ALL groups: docker shell: /bin/bash ssh-authorized-keys: - ssh-rsa AAAAB3Nza...your-key-here runcmd: - systemctl enable docker - systemctl start docker Example 3: Install Node.js and clone a repoThis script installs Node.js and clones a GitHub repo to your Gcore VM at launch:#cloud-config packages: - curl runcmd: - curl -fsSL https://deb.nodesource.com/setup_18.x | bash - - apt-get install -y nodejs - git clone https://github.com/example-user/dev-project.git /home/devuser/project Reusing and versioning your scriptsTo avoid reinventing the wheel, keep your cloud-init scripts:In version control (e.g., Git)Templated for different environments (e.g., dev vs staging)Modular so you can reuse base blocks across projectsYou can also use tools like Ansible or Terraform with cloud-init blocks to standardize provisioning across your team or multiple Gcore VM environments.Debugging cloud-initIf your script doesn’t behave as expected, SSH into the instance and check the cloud-init logs:sudo cat /var/log/cloud-init-output.log This file shows each command as it ran and any errors that occurred.Other helpful logs:/var/log/cloud-init.log /var/lib/cloud/instance/user-data.txt Pro tip: Echo commands or write log files in your script to help debug tricky setups—especially useful if you’re automating multi-node workflows across Gcore Cloud.Tips and best practicesIndentation matters! YAML is picky. Use spaces, not tabs.Always start the file with #cloud-config.runcmd is for commands that run at the end of boot.Use write_files to write configs, env variables, or secrets.Cloud-init scripts only run on the first boot. To re-run, you’ll need to manually trigger cloud-init or re-create the VM.Automate it all with GcoreIf you're provisioning manually, you're doing it wrong. Cloud-init lets you treat your VM setup as code: portable, repeatable, and testable. Whether you’re spinning up ephemeral dev boxes or preparing staging environments, Gcore’s support for cloud-init means you can automate it all.For more on managing virtual machines with Gcore, check out our product documentation.Explore Gcore VM product docs

How to cut egress costs and speed up delivery using Gcore CDN and Object Storage

If you’re serving static assets (images, videos, scripts, downloads) from object storage, you’re probably paying more than you need to, and your users may be waiting longer than they should.In this guide, we explain how to front your bucket with Gcore CDN to cache static assets, cut egress bandwidth costs, and get faster TTFB globally. We’ll walk through setup (public or private buckets), signed URL support, cache control best practices, debugging tips, and automation with the Gcore API or Terraform.Why bother?Serving directly from object storage hits your origin for every request and racks up egress charges. With a CDN in front, cached files are served from edge—faster for users, and cheaper for you.Lower TTFB, better UXWhen content is cached at the edge, it doesn’t have to travel across the planet to get to your user. Gcore CDN caches your assets at PoPs close to end users, so requests don’t hit origin unless necessary. Once cached, assets are delivered in a few milliseconds.Lower billsMost object storage providers charge $80–$120 per TB in egress fees. By fronting your storage with a CDN, you only pay egress once per edge location—then it’s all cache hits after that. If you’re using Gcore Storage and Gcore CDN, there’s zero egress fee between the two.Caching isn’t the only way you save. Gcore CDN can also compress eligible file types (like HTML, CSS, JavaScript, and JSON) on the fly, further shrinking bandwidth usage and speeding up file delivery—all without any changes to your storage setup.Less origin traffic and less data to transfer means smaller bills. And your storage bucket doesn’t get slammed under load during traffic spikes.Simple scaling, globallyThe CDN takes the hit, not your bucket. That means fewer rate-limit issues, smoother traffic spikes, and more reliable performance globally. Gcore CDN spans the globe, so you’re good whether your users are in Tokyo, Toronto, or Tel Aviv.Setup guide: Gcore CDN + Gcore Object StorageLet’s walk through configuring Gcore CDN to cache content from a storage bucket. This works with Gcore Object Storage and other S3-compatible services.Step 1: Prep your bucketPublic? Check files are publicly readable (via ACL or bucket policy).Private? Use Gcore’s AWS Signature V4 support—have your access key, secret, region, and bucket name ready.Gcore Object Storage URL format: https://<bucket-name>.<region>.cloud.gcore.lu/<object> Step 2: Create CDN resource (UI or API)In the Gcore Customer Portal:Go to CDN > Create CDN ResourceChoose "Accelerate and protect static assets"Set a CNAME (e.g. cdn.yoursite.com) if you want to use your domainConfigure origin:Public bucket: Choose None for authPrivate bucket: Choose AWS Signature V4, and enter credentialsChoose HTTPS as the origin protocolGcore will assign a *.gcdn.co domain. If you’re using a custom domain, add a CNAME: cdn.yoursite.com CNAME .gcdn.co Here’s how it works via Terraform: resource "gcore_cdn_resource" "cdn" { cname = "cdn.yoursite.com" origin_group_id = gcore_cdn_origingroup.origin.id origin_protocol = "HTTPS" } resource "gcore_cdn_origingroup" "origin" { name = "my-origin-group" origin { source = "mybucket.eu-west.cloud.gcore.lu" enabled = true } } Step 3: Set caching behaviorSet Cache-Control headers in your object metadata: Cache-Control: public, max-age=2592000 Too messy to handle in storage? Override cache logic in Gcore:Force TTLs by path or extensionIgnore or forward query strings in cache keyStrip cookies (if unnecessary for cache decisions)Pro tip: Use versioned file paths (/img/logo.v3.png) to bust cache safely.Secure access with signed URLsWant your assets to be private, but still edge-cacheable? Use Gcore’s Secure Token feature:Enable Secure Token in CDN settingsSet a secret keyGenerate time-limited tokens in your appPython example: import base64, hashlib, time secret = 'your_secret' path = '/videos/demo.mp4' expires = int(time.time()) + 3600 string = f"{expires}{path} {secret}" token = base64.urlsafe_b64encode(hashlib.md5(string.encode()).digest()).decode().strip('=') url = f"https://cdn.yoursite.com{path}?md5={token}&expires={expires}" Signed URLs are verified at the CDN edge. Invalid or expired? Blocked before origin is touched.Optional: Bind the token to an IP to prevent link sharing.Debug and cache tuneUse curl or browser devtools: curl -I https://cdn.yoursite.com/img/logo.png Look for:Cache: HIT or MISSCache-ControlX-Cached-SinceCache not working? Check for the following errors:Origin doesn’t return Cache-ControlCDN override TTL not appliedCache key includes query strings unintentionallyYou can trigger purges from the Gcore Customer Portal or automate them via the API using POST /cdn/purge. Choose one of three ways:Purge all: Clear the entire domain’s cache at once.Purge by URL: Target a specific full path (e.g., /images/logo.png).Purge by pattern: Target a set of files using a wildcard at the end of the pattern (e.g., /videos/*).Monitor and optimize at scaleAfter rollout:Watch origin bandwidth dropCheck hit ratio (aim for >90%)Audit latency (TTFB on HIT vs MISS)Consider logging using Gcore’s CDN logs uploader to analyze cache behavior, top requested paths, or cache churn rates.For maximum savings, combine Gcore Object Storage with Gcore CDN: egress traffic between them is 100% free. That means you can serve cached assets globally without paying a cent in bandwidth fees.Using external storage? You’ll still slash egress costs by caching at the edge and cutting direct origin traffic—but you’ll unlock the biggest savings when you stay inside the Gcore ecosystem.Save money and boost performance with GcoreStill serving assets direct from storage? You’re probably wasting money and compromising performance on the table. Front your bucket with Gcore CDN. Set smart cache headers or use overrides. Enable signed URLs if you need control. Monitor cache HITs and purge when needed. Automate the setup with Terraform. Done.Next steps:Create your CDN resourceUse private object storage with Signature V4Secure your CDN with signed URLsCreate a free CDN resource now

Bare metal vs. virtual machines: performance, cost, and use case comparison

Choosing the right type of server infrastructure is critical to how your application performs, scales, and fits your budget. For most workloads, the decision comes down to two core options: bare metal servers and virtual machines (VMs). Both can be deployed in the cloud, but they differ significantly in terms of performance, control, scalability, and cost.In this article, we break down the core differences between bare metal and virtual servers, highlight when to choose each, and explain how Gcore can help you deploy the right infrastructure for your needs. If you want to learn about either BM or VMs in detail, we’ve got articles for those: here’s the one for bare metal, and here’s a deep dive into virtual machines.Bare metal vs. virtual machines at a glanceWhen evaluating whether bare metal or virtual machines are right for your company, consider your specific workload requirements, performance priorities, and business objectives. Here’s a quick breakdown to help you decide what works best for you.FactorBare metal serversVirtual machinesPerformanceDedicated resources; ideal for high-performance workloadsShared resources; suitable for moderate or variable workloadsScalabilityOften requires manual scaling; less flexibleHighly elastic; easy to scale up or downCustomizationFull control over hardware, OS, and configurationLimited by hypervisor and provider’s environmentSecurityIsolated by default; no hypervisor layerShared environment with strong isolation protocolsCostHigher upfront cost; dedicated hardwarePay-as-you-go pricing; cost-effective for flexible workloadsBest forHPC, AI/ML, compliance-heavy workloadsStartups, dev/test, fast-scaling applicationsAll about bare metal serversA bare metal server is a single-tenant physical server rented from a cloud provider. Unlike virtual servers, the hardware is not shared with other users, giving you full access to all resources and deeper control over configurations. You get exclusive access and control over the hardware via the cloud provider, which offers the stability and security needed for high-demand applications.The benefits of bare metal serversHere are some of the business advantages of opting for a bare metal server:Maximized performance: Because they are dedicated resources, bare metal servers provide top-tier performance without sharing processing power, memory, or storage with other users. This makes them ideal for resource-intensive applications like high-performance computing (HPC), big data processing, and game hosting.Greater control: Since you have direct access to the hardware, you can customize the server to meet your specific requirements. This is especially important for businesses with complex, specialized needs that require fine-tuned configurations.High security: Bare metal servers offer a higher level of security than their alternatives due to the absence of virtualization. With no shared resources or hypervisor layer, there’s less risk of vulnerabilities that come with multi-tenant environments.Dedicated resources: Because you aren’t sharing the server with other users, all server resources are dedicated to your application so that you consistently get the performance you need.Who should use bare metal servers?Here are examples of instances where bare metal servers are the best option for a business:High-performance computing (HPC)Big data processing and analyticsResource-intensive applications, such as AI/ML workloadsGame and video streaming serversBusinesses requiring enhanced security and complianceAll about virtual machinesA virtual server (or virtual machine) runs on top of a physical server that’s been partitioned by a cloud provider using a hypervisor. This allows multiple VMs to share the same hardware while remaining isolated from each other.Unlike bare metal servers, virtual machines share the underlying hardware with other cloud provider customers. That means you’re using (and paying for) part of one server, providing cost efficiency and flexibility.The benefits of virtual machinesHere are some advantages of using a shared virtual machine:Scalability: Virtual machines are ideal for businesses that need to scale quickly and are starting at a small scale. With cloud-based virtualization, you can adjust your server resources (CPU, memory, storage) on demand to match changing workloads.Cost efficiency: You pay only for the resources you use with VMs, making them cost-effective for companies with fluctuating resource needs, as there is no need to pay for unused capacity.Faster deployment: VMs can be provisioned quickly and easily, which makes them ideal for anyone who wants to deploy new services or applications fast.Who should use virtual machines?VMs are a great fit for the following:Web hosting and application hostingDevelopment and testing environmentsRunning multiple apps with varying demandsStartups and growing businesses requiring scalabilityBusinesses seeking cost-effective, flexible solutionsWhich should you choose?There’s no one-size-fits-all answer. Your choice should depend on the needs of your workload:Choose bare metal if you need dedicated performance, low-latency access to hardware, or tighter control over security and compliance.Choose virtual servers if your priority is flexible scaling, faster deployment, and optimized cost.If your application uses GPU-based inference or AI training, check out our dedicated guide to VM vs. BM for AI workloads.Get started with Gcore BM or VMs todayAt Gcore, we provide both bare metal and virtual machine solutions, offering flexibility, performance, and reliability to meet your business needs. Gcore Bare Metal has the power and reliability needed for demanding workloads, while Gcore Virtual Machines offers customizable configurations, free egress traffic, and flexibility.Compare Gcore BM and VM pricing now

Optimize your workload: a guide to selecting the best virtual machine configuration

Virtual machines (VMs) offer the flexibility, scalability, and cost-efficiency that businesses need to optimize workloads. However, choosing the wrong setup can lead to poor performance, wasted resources, and unnecessary costs.In this guide, we’ll walk you through the essential factors to consider when selecting the best virtual machine configuration for your specific workload needs.﹟1 Understand your workload requirementsThe first step in choosing the right virtual machine configuration is understanding the nature of your workload. Workloads can range from light, everyday tasks to resource-intensive applications. When making your decision, consider the following:Compute-intensive workloads: Applications like video rendering, scientific simulations, and data analysis require a higher number of CPU cores. Opt for VMs with multiple processors or CPUs for smoother performance.Memory-intensive workloads: Databases, big data analytics, and high-performance computing (HPC) jobs often need more RAM. Choose a VM configuration that provides sufficient memory to avoid memory bottlenecks.Storage-intensive workloads: If your workload relies heavily on storage, such as file servers or applications requiring frequent read/write operations, prioritize VM configurations that offer high-speed storage options, such as SSDs or NVMe.I/O-intensive workloads: Applications that require frequent network or disk I/O, such as cloud services and distributed applications, benefit from VMs with high-bandwidth and low-latency network interfaces.﹟2 Consider VM size and scalabilityOnce you understand your workload’s requirements, the next step is to choose the right VM size. VM sizes are typically categorized by the amount of CPU, memory, and storage they offer.Start with a baseline: Select a VM configuration that offers a balanced ratio of CPU, RAM, and storage based on your workload type.Scalability: Choose a VM size that allows you to easily scale up or down as your needs change. Many cloud providers offer auto-scaling capabilities that adjust your VM’s resources based on real-time demand, providing flexibility and cost savings.Overprovisioning vs. underprovisioning: Avoid overprovisioning (allocating excessive resources) unless your workload demands peak capacity at all times, as this can lead to unnecessary costs. Similarly, underprovisioning can affect performance, so finding the right balance is essential.﹟3 Evaluate CPU and memory considerationsThe central processing unit (CPU) and memory (RAM) are the heart of a virtual machine. The configuration of both plays a significant role in performance. Workloads that need high processing power, such as video encoding, machine learning, or simulations, will benefit from VMs with multiple CPU cores. However, be mindful of CPU architecture—look for VMs that offer the latest processors (e.g., Intel Xeon, AMD EPYC) for better performance per core.It’s also important that the VM has enough memory to avoid paging, which occurs when the system uses disk space as virtual memory, significantly slowing down performance. Consider a configuration with more RAM and support for faster memory types like DDR4 for memory-heavy applications.﹟4 Assess storage performance and capacityStorage performance and capacity can significantly impact the performance of your virtual machine, especially for applications requiring large data volumes. Key considerations include:Disk type: For faster read/write operations, opt for solid-state drives (SSDs) over traditional hard disk drives (HDDs). Some cloud providers also offer NVMe storage, which can provide even greater speed for highly demanding workloads.Disk size: Choose the right size based on the amount of data you need to store and process. Over-allocating storage space might seem like a safe bet, but it can also increase costs unnecessarily. You can always resize disks later, so avoid over-allocating them upfront.IOPS and throughput: Some workloads require high input/output operations per second (IOPS). If this is a priority for your workload (e.g., databases), make sure that your VM configuration includes high IOPS storage options.﹟5 Weigh up your network requirementsWhen working with cloud-based VMs, network performance is a critical consideration. High-speed and low-latency networking can make a difference for applications such as online gaming, video conferencing, and real-time analytics.Bandwidth: Check whether the VM configuration offers the necessary bandwidth for your workload. For applications that handle large data transfers, such as cloud backup or file servers, make sure that the network interface provides high throughput.Network latency: Low latency is crucial for applications where real-time performance is key (e.g., trading systems, gaming). Choose VMs with low-latency networking options to minimize delays and improve the user experience.Network isolation and security: Check if your VM configuration provides the necessary network isolation and security features, especially when handling sensitive data or operating in multi-tenant environments.﹟6 Factor in cost considerationsWhile it’s essential that your VM has the right configuration, cost is always an important factor to consider. Cloud providers typically charge based on the resources allocated, so optimizing for cost efficiency can significantly impact your budget.Consider whether a pay-as-you-go or reserved model (which offers discounted rates in exchange for a long-term commitment) fits your usage pattern. The reserved option can provide significant savings if your workload runs continuously. You can also use monitoring tools to track your VM’s performance and resource usage over time. This data will help you make informed decisions about scaling up or down so you’re not paying for unused resources.﹟7 Evaluate security featuresSecurity is a primary concern when selecting a VM configuration, especially for workloads handling sensitive data. Consider the following:Built-in security: Look for VMs that offer integrated security features such as DDoS protection, web application firewall (WAF), and encryption.Compliance: Check that the VM configuration meets industry standards and regulations, such as GDPR, ISO 27001, and PCI DSS.Network security: Evaluate the VM's network isolation capabilities and the availability of cloud firewalls to manage incoming and outgoing traffic.﹟8 Consider geographic locationThe geographic location of your VM can impact latency and compliance. Therefore, it’s a good idea to choose VM locations that are geographically close to your end users to minimize latency and improve performance. In addition, it’s essential to select VM locations that comply with local data sovereignty laws and regulations.﹟9 Assess backup and recovery optionsBackup and recovery are critical for maintaining data integrity and availability. Look for VMs that offer automated backup solutions so that data is regularly saved. You should also evaluate disaster recovery capabilities, including the ability to quickly restore data and applications in case of failure.﹟10 Test and iterateFinally, once you've chosen a VM configuration, testing its performance under real-world conditions is essential. Most cloud providers offer performance monitoring tools that allow you to assess how well your VM is meeting your workload requirements.If you notice any performance bottlenecks, be prepared to adjust the configuration. This could involve increasing CPU cores, adding more memory, or upgrading storage. Regular testing and fine-tuning means that your VM is always optimized.Choosing a virtual machine that suits your requirementsSelecting the best virtual machine configuration is a key step toward optimizing your workloads efficiently, cost-effectively, and without unnecessary performance bottlenecks. By understanding your workload’s needs, considering factors like CPU, memory, storage, and network performance, and continuously monitoring resource usage, you can make informed decisions that lead to better outcomes and savings.Whether you're running a small application or large-scale enterprise software, the right VM configuration can significantly improve performance and cost. Gcore offers a wide range of virtual machine options that can meet your unique requirements. Our virtual machines are designed to meet diverse workload requirements, providing dedicated vCPUs, high-speed storage, and low-latency networking across 30+ global regions. You can scale compute resources on demand, benefit from free egress traffic, and enjoy flexible pricing models by paying only for the resources in use, maximizing the value of your cloud investments.Contact us to discuss your VM needs

How to get the size of a directory in Linux

Understanding how to check directory size in Linux is critical for managing storage space efficiently. Understanding this process is essential whether you’re assessing specific folder space or preventing storage issues.This comprehensive guide covers commands and tools so you can easily calculate and analyze directory sizes in a Linux environment. We will guide you step-by-step through three methods: du, ncdu, and ls -la. They’re all effective and each offers different benefits.What is a Linux directory?A Linux directory is a special type of file that functions as a container for storing files and subdirectories. It plays a key role in organizing the Linux file system by creating a hierarchical structure. This arrangement simplifies file management, making it easier to locate, access, and organize related files. Directories are fundamental components that help ensure smooth system operations by maintaining order and facilitating seamless file access in Linux environments.#1 Get Linux directory size using the du commandUsing the du command, you can easily determine a directory’s size by displaying the disk space used by files and directories. The output can be customized to be presented in human-readable formats like kilobytes (KB), megabytes (MB), or gigabytes (GB).Check the size of a specific directory in LinuxTo get the size of a specific directory, open your terminal and type the following command:du -sh /path/to/directoryIn this command, replace /path/to/directory with the actual path of the directory you want to assess. The -s flag stands for “summary” and will only display the total size of the specified directory. The -h flag makes the output human-readable, showing sizes in a more understandable format.Example: Here, we used the path /home/ubuntu/, where ubuntu is the name of our username directory. We used the du command to retrieve an output of 32K for this directory, indicating a size of 32 KB.Check the size of all directories in LinuxTo get the size of all files and directories within the current directory, use the following command:sudo du -h /path/to/directoryExample: In this instance, we again used the path /home/ubuntu/, with ubuntu representing our username directory. Using the command du -h, we obtained an output listing all files and directories within that particular path.#2 Get Linux directory size using ncduIf you’re looking for a more interactive and feature-rich approach to exploring directory sizes, consider using the ncdu (NCurses Disk Usage) tool. ncdu provides a visual representation of disk usage and allows you to navigate through directories, view size details, and identify large files with ease.For Debian or Ubuntu, use this command:sudo apt-get install ncduOnce installed, run ncdu followed by the path to the directory you want to analyze:ncdu /path/to/directoryThis will launch the ncdu interface, which shows a breakdown of file and subdirectory sizes. Use the arrow keys to navigate and explore various folders, and press q to exit the tool.Example: Here’s a sample output of using the ncdu command to analyze the home directory. Simply enter the ncdu command and press Enter. The displayed output will look something like this:#3 Get Linux directory size using 1s -1aYou can alternatively opt to use the ls command to list the files and directories within a directory. The options -l and -a modify the default behavior of ls as follows:-l (long listing format)Displays the detailed information for each file and directoryShows file permissions, the number of links, owner, group, file size, the timestamp of the last modification, and the file/directory name-a (all files)Instructs ls to include all files, including hidden files and directoriesIncludes hidden files on Linux that typically have names beginning with a . (dot)ls -la lists all files (including hidden ones) in long format, providing detailed information such as permissions, owner, group, size, and last modification time. This command is especially useful when you want to inspect file attributes or see hidden files and directories.Example: When you enter ls -la command and press Enter, you will see an output similar to this:Each line includes:File type and permissions (e.g., drwxr-xr-x):The first character indicates the file type- for a regular filed for a directoryl for a symbolic linkThe next nine characters are permissions in groups of three (rwx):r = readw = writex = executePermissions are shown for three classes of users: owner, group, and others.Number of links (e.g., 2):For regular files, this usually indicates the number of hard linksFor directories, it often reflects subdirectory links (e.g., the . and .. entries)Owner and group (e.g., user group)File size (e.g., 4096 or 1045 bytes)Modification date and time (e.g., Jan 7 09:34)File name (e.g., .bashrc, notes.txt, Documents):Files or directories that begin with a dot (.) are hidden (e.g., .bashrc)ConclusionThat’s it! You can now determine the size of a directory in Linux. Measuring directory sizes is a crucial skill for efficient storage management. Whether you choose the straightforward du command, use the visual advantages of the ncdu tool, or opt for the versatility of ls -la, this expertise enhances your ability to uphold an organized and efficient Linux environment.Looking to deploy Linux in the cloud? With Gcore Edge Cloud, you can choose from a wide range of pre-configured virtual machines suitable for Linux:Affordable shared compute resources starting from €3.2 per monthDeploy across 50+ cloud regions with dedicated servers for low-latency applicationsSecure apps and data with DDoS protection, WAF, and encryption at no additional costGet started today

How to Run Hugging Face Spaces on Gcore Inference at the Edge

Running machine learning models, especially large-scale models like GPT 3 or BERT, requires a lot of computing power and comes with a lot of latency. This makes real-time applications resource-intensive and challenging to deliver. Running ML models at the edge is a lightweight approach offering significant advantages for latency, privacy, and resource optimization.  Gcore Inference at the Edge makes it simple to deploy and manage custom models efficiently, giving you the ability to deploy and scale your favorite Hugging Face models globally in just a few clicks. In this guide, we’ll walk you through how easy it is to harness the power of Gcore’s edge AI infrastructure to deploy a Hugging Face Space model. Whether you’re developing NLP solutions or cutting-edge computer vision applications, deploying at the edge has never been simpler—or more powerful. Step 1: Log In to the Gcore Customer PortalGo to gcore.com and log in to the Gcore Customer Portal. If you don’t yet have an account, go ahead and create one—it’s free. Step 2: Go to Inference at the EdgeIn the Gcore Customer Portal, click Inference at the Edge from the left navigation menu. Then click Deploy custom model. Step 3: Choose a Hugging Face ModelOpen huggingface.com and browse the available models. Select the model you want to deploy. Navigate to the corresponding Hugging Face Space for the model. Click on Files in the Space and locate the Docker option. Copy the Docker image link and startup command from Hugging Face Space. Step 4: Deploy the Model on GcoreReturn to the Gcore Customer Portal deployment page and enter the following details: Model image URL: registry.hf.space/ethux-mistral-pixtral-demo:latest Startup command: python app.py Container port: 7860 Configure the pod as follows: GPU-optimized: 1x L40S vCPUs: 16 RAM: 232GiB For optimal performance, choose any available region for routing placement. Name your deployment and click Deploy.Step 5: Interact with Your ModelOnce the model is up and running, you’ll be provided with an endpoint. You can now interact with the model via this endpoint to test and use your deployed model at the edge.Powerful, Simple AI Deployment with GcoreGcore Inference at the Edge is the future of AI deployment, combining the ease of Hugging Face integration with the robust infrastructure needed for real-time, scalable, and global solutions. By leveraging edge computing, you can optimize model performance and simultaneously futureproof your business in a world that increasingly demands fast, secure, and localized AI applications. Deploying models to the edge allows you to capitalize on real-time insights, improve customer experiences, and outpace your competitors. Whether you’re leading a team of developers or spearheading a new AI initiative, Gcore Inference at the Edge offers the tools you need to innovate at the speed of tomorrow. Explore Gcore Inference at the Edge

Subscribe to our newsletter

Get the latest industry trends, exclusive insights, and Gcore updates delivered straight to your inbox.