From f481a91805e8e874dcdfd137e4625f5f59ed1c29 Mon Sep 17 00:00:00 2001
From: hanran-y <hanran@vast.ai>
Date: Mon, 3 Nov 2025 18:36:20 -0800
Subject: [PATCH 1/5] update host verification stages doc and add a new
 understanding verification page

---
 docs.json                                     |   5 +
 .../host/understanding-verification.mdx       | 171 ++++++++++++++++++
 documentation/host/verification-stages.mdx    | 153 ++++++++++------
 3 files changed, 278 insertions(+), 51 deletions(-)
 create mode 100644 documentation/host/understanding-verification.mdx

diff --git a/docs.json b/docs.json
index 385ed3e..fcaa464 100644
--- a/docs.json
+++ b/docs.json
@@ -150,6 +150,7 @@
                 "pages": [
                   "documentation/host/hosting-overview",
                   "documentation/host/verification-stages",
+                  "documentation/host/understanding-verification",
                   "documentation/host/datacenter-status",
                   "documentation/host/earning",
                   "documentation/host/payment",
@@ -429,6 +430,10 @@
       "source": "/verification-stages",
       "destination": "/documentation/host/verification-stages"
     },
+    {
+      "source": "/understanding-verification",
+      "destination": "/documentation/host/understanding-verification"
+    },
     {
       "source": "/data-movement",
       "destination": "/documentation/instances/storage/data-movement"
diff --git a/documentation/host/understanding-verification.mdx b/documentation/host/understanding-verification.mdx
new file mode 100644
index 0000000..9d55dce
--- /dev/null
+++ b/documentation/host/understanding-verification.mdx
@@ -0,0 +1,171 @@
+---
+title: Understanding Verification
+createdAt: Mon Nov 03 2025 17:30:00 GMT+0000 (Coordinated Universal Time)
+updatedAt: Mon Nov 03 2025 17:30:00 GMT+0000 (Coordinated Universal Time)
+"canonical": "/documentation/host/understanding-verification"
+---
+
+<script type="application/ld+json" dangerouslySetInnerHTML={{
+  __html: JSON.stringify({
+    "@context": "https://schema.org",
+    "@type": "HowTo",
+    "name": "Understanding Verification on Vast.ai",
+    "description": "A comprehensive guide to understanding how machine verification works on Vast.ai platform and how to optimize your machine for verification.",
+    "step": [
+      {
+        "@type": "HowToStep",
+        "name": "Ensure Reliability",
+        "text": "Maintain consistent uptime with minimal downtime. Keep network connectivity stable, manage thermals and power to prevent throttling, and proactively monitor hardware health. Aim for sustained ≥99.99% uptime to improve verification likelihood."
+      },
+      {
+        "@type": "HowToStep",
+        "name": "Optimize Infrastructure Configuration",
+        "text": "Use modern datacenter/workstation GPUs with adequate VRAM and GPU count. Ensure proper PCIe bandwidth, strong server-grade CPUs, and NVMe storage. Enable VM support in BIOS and maintain high-speed, symmetric, stable network bandwidth with open ports."
+      },
+      {
+        "@type": "HowToStep",
+        "name": "Maximize DLPerf Score",
+        "text": "Install the latest compatible drivers and CUDA versions. Eliminate PCIe, thermal, and power bottlenecks to maintain sustained GPU clocks. Ensure proper system configuration to achieve high real-world deep learning performance."
+      },
+      {
+        "@type": "HowToStep",
+        "name": "Align with Supply & Demand",
+        "text": "Offer in-demand GPU models with adequate VRAM and balanced resources. Choose popular GPUs that align with renter preferences and maintain strong reliability to remain attractive in the marketplace."
+      },
+      {
+        "@type": "HowToStep",
+        "name": "Maintain Software Excellence",
+        "text": "Keep drivers and CUDA correctly installed and compatible using stable latest releases. Keep systems clean by running workloads via Create Job only. Avoid background services that consume resources."
+      },
+      {
+        "@type": "HowToStep",
+        "name": "Monitor and Upgrade Responsibly",
+        "text": "Scale up by adding GPUs or RAM when needed, but never reduce hardware after machine creation as this triggers deverification. Monitor system health proactively and address issues promptly to maintain verification status."
+      }
+    ]
+  })
+}} />
+
+## How Verification Works
+
+Verification is **fully automated and powered by proprietary algorithms** that continuously evaluate each machine’s operational health and performance.
+
+Only machines that meet the platform’s defined reliability and performance thresholds are marked as **Verified**.  
+
+This process involves **no manual intervention**, ensuring consistent, scalable, and objective verification across all systems.
+
+---
+
+To qualify, a machine must pass minimum baseline, and health/stability checks. Beyond that, the system evaluates four primary criteria (order not indicative of priority):
+
+## 1) Reliability
+
+**Definition:** Stable, uninterrupted operation over time (uptime, resilience under continuous workloads).
+
+**Do**
+
+- Maintain consistent uptime with minimal downtime.  
+- Keep network connectivity stable; avoid jitter and drops.  
+- Manage thermals and power to prevent throttling.  
+- Proactively monitor hardware health and perform maintenance.  
+
+**Avoid**
+
+- Frequent restarts or unplanned outages.  
+- Overheating, undervolting, or unstable power delivery.  
+
+> **Note:** Higher reliability greatly improves verification likelihood. Sustained ≥99.99% (up to 99.9999%+) uptime is typically favored.
+
+---
+
+## 2) Infrastructure Configuration
+
+**Definition:** Hardware, network, and software readiness to meet operational standards.
+
+### Hardware
+
+- **GPU:** Type, memory, and count matter. Newer datacenter/workstation GPUs are prioritized (e.g., B200 > H200 >> 5090 > 4070).  
+- **VRAM:** More VRAM improves performance profiles.  
+- **GPU Count:** For the same GPU type, more GPUs increase verification likelihood (e.g., 8×5090 >> 2×5090 > 1×5090).  
+- **PCIe Bandwidth:** Adequate throughput is essential; bottlenecks depress DLPerf and overall performance.  
+- **CPU:** Favor strong, server-grade CPUs; actual measured performance matters.  
+- **Storage:** Both capacity and bandwidth (e.g., NVMe) impact responsiveness and reliability.  
+
+### Network
+
+- High-speed, symmetric, stable bandwidth is favored.  
+- Ensure required ports are open and accessible; a static IP helps.  
+
+### Virtualization
+
+- Enabling VM support significantly improves verification likelihood.  
+
+### Software
+
+- Drivers/CUDA must be correctly installed and compatible (use stable **latest** releases).  
+- Keep systems clean; run workloads via Create Job only.  
+
+### System Optimization & Upgrades
+
+- Balanced scaling matters (CPU/RAM/PCIe/bandwidth commensurate with GPU tier).  
+- Do not reduce hardware after creation (e.g., fewer GPUs/RAM) – this will trigger Deverified.  
+- Upgrades (adding GPUs/RAM) are allowed but may take time to reflect across the platform.  
+
+**Do**
+
+- Verify GPU PCIe connections provide full bandwidth and are not throttled.  
+- Keep the latest drivers/CUDA aligned with workloads.  
+- Confirm required ports and end-to-end reachability.  
+
+**Avoid**
+
+- Pairing high-end GPUs with under-provisioned CPU/RAM.  
+- Letting hidden background services consume resources.
+
+---
+
+## 3) DLPerf Score
+
+**Definition:** Estimated GPU performance on typical deep-learning tasks (e.g., CNN/Transformer training) for cross-hardware comparison. Higher DLPerf improves verification odds. [Read more](https://docs.vast.ai/documentation/reference/faq/rental-types#dlperf-scoring)
+
+**Do**
+
+- Use the **latest** compatible drivers/CUDA.  
+- Eliminate PCIe, thermal, and power bottlenecks to maintain sustained clocks.  
+
+**Avoid**
+
+- Misconfigurations that suppress benchmark performance.  
+
+---
+
+## 4) Supply & Demand Analysis
+
+**Definition:** Ongoing evaluation of market trends and renter behavior to surface configurations most likely to be rented.
+
+**Implication:** Machines aligned with active renter preferences—popular GPUs, sufficient VRAM, strong reliability, fast internet—are prioritized for verification to maximize utilization and profitability.
+
+**Do**
+
+- Offer in-demand GPU models with adequate VRAM and balanced resources.  
+- Maintain strong reliability to remain attractive once listed.  
+
+**Avoid**
+
+- Niche/mismatched configurations with low renter interest.  
+
+---
+
+## Quick Reference
+
+| **Category** | **What Matters Most** | **How to Improve** |
+|---------------|------------------------|--------------------|
+| Reliability | Stable, uninterrupted uptime | Proactive monitoring; steady power/thermals; minimize restarts |
+| Network | Symmetric, stable bandwidth; open ports | Upgrade links; verify routing/ports; monitor jitter/loss |
+| Hardware | Modern GPUs/CPUs; adequate PCIe & RAM | Favor DC/workstation GPUs; ensure PCIe lanes; match CPU/RAM to GPU tier |
+| Storage | Throughput and reliability | Prefer NVMe; monitor SMART; ensure sustained bandwidth |
+| Virtualization | VM capability enabled | Enable in BIOS, enable IOMMU. |
+| Software | Correct drivers/CUDA; clean system | Install latest, stable, compatible versions; use Create Job only |
+| DLPerf | High real-world throughput | Fix PCIe/thermal bottlenecks; maintain clocks; correct drivers |
+| Supply & Demand | Alignment with renter needs | Choose popular GPUs/VRAM; balance specs; maintain reliability |
+| Upgrades | Changes reflected by platform | Scale up (add GPUs/RAM); avoid reductions that cause Deverified |
diff --git a/documentation/host/verification-stages.mdx b/documentation/host/verification-stages.mdx
index 16f067a..f5d8075 100644
--- a/documentation/host/verification-stages.mdx
+++ b/documentation/host/verification-stages.mdx
@@ -1,7 +1,7 @@
 ---
 title: Verification Stages
 createdAt: Mon Jan 13 2025 21:20:40 GMT+0000 (Coordinated Universal Time)
-updatedAt: Tue Feb 18 2025 17:46:03 GMT+0000 (Coordinated Universal Time)
+updatedAt: Mon Nov 03 2025 12:50:03 GMT+0000 (Coordinated Universal Time)
 "canonical": "/documentation/host/verification-stages"
 ---
 
@@ -9,102 +9,153 @@ updatedAt: Tue Feb 18 2025 17:46:03 GMT+0000 (Coordinated Universal Time)
   __html: JSON.stringify({
     "@context": "https://schema.org",
     "@type": "HowTo",
-    "name": "How to Get Your Machine Verified on Vast.ai",
-    "description": "Understanding the verification stages and requirements for getting your machine verified on Vast.ai.",
+    "name": "How to Navigate Machine Verification Stages on Vast.ai",
+    "description": "Complete guide to understanding verification stages (Unverified → Verified → Deverified) and requirements for getting your machine verified on Vast.ai platform.",
     "step": [
       {
         "@type": "HowToStep",
-        "name": "Meet Minimum Hardware Requirements",
-        "text": "Ensure your machine meets minimum guidelines: Ubuntu 18.04 or newer, dedicated machine only, fast reliable internet (at least 10Mbps per machine), 10-series Nvidia GPU or newer supported AMD GPU, at least 1 physical CPU core (2 hyperthreads) per GPU with AVX instruction set support, at least 4GB of system RAM per GPU, fast SSD storage with at least 128GB per GPU, at least 1X PCIE for every 2.5 TFLOPS of GPU performance, all GPUs on the machine must be of the same type, and an open port range mapped to each machine."
+        "name": "Meet Basic Listing Requirements",
+        "text": "Ensure your machine meets minimum guidelines for listing: Ubuntu 18.04 or newer, dedicated machine only, fast reliable internet (at least 10Mbps), 10-series Nvidia GPU or newer supported AMD GPU, at least 1 physical CPU core per GPU with AVX support, at least 4GB system RAM per GPU, fast SSD storage with 128GB+ per GPU, adequate PCIe bandwidth, same GPU types only, and open port range."
       },
       {
         "@type": "HowToStep",
         "name": "Meet Verification Requirements",
-        "text": "Ensure your machine meets verification requirements: CUDA version greater than or equal to 12.0, reliability of 90%, at least 3 open ports per GPU (100 recommended), internet download speed of 500 Mb/s, internet upload speed of 500 Mb/s, and GPU RAM of 7 GB."
+        "text": "Satisfy additional verification requirements: CUDA version 12.0 or higher, maintain 90%+ reliability, provide at least 3 open ports per GPU (100 recommended), achieve 500+ Mb/s internet speeds (both download and upload), and ensure GPUs have at least 7GB VRAM."
       },
       {
         "@type": "HowToStep",
-        "name": "Run Self-Test",
-        "text": "Use the vast cli self-test machine command to see if a machine meets all of the requirements and resolve any issues. This will give you a better chance of getting verified."
+        "name": "Maintain Host Responsibilities",
+        "text": "Keep systems stable, well-cooled, and correctly configured. Maintain compatible drivers/CUDA and dependable symmetric networking. Run only platform jobs via Create Job. When issues arise, fix them promptly as the automation will update verification status accordingly."
       },
       {
         "@type": "HowToStep",
-        "name": "Wait for Verification",
-        "text": "Verification is mostly for higher end machines. High-end machines ($10k+) like H100 or A100 80GB should be tested quickly in a day or so. 8x4090, 4xA6000 should be tested in less than a week. For other machines, verification is relatively random and runs roughly about once a week. The only manual verification tests are for datacenters and high end machines."
+        "name": "Optimize During Unverified Stage",
+        "text": "While unverified, maintain steady uptime during evaluation. Ensure drivers/CUDA and networking are correctly installed and reachable. Keep environment clean by scheduling work via Create Job only. Avoid reboots, configuration changes, and unrelated background workloads."
       },
       {
         "@type": "HowToStep",
-        "name": "Maintain Verification Status",
-        "text": "Once verified, continue to meet requirements and prevent issues that could get you deverified. Watch for red errors on your machine card and investigate and resolve them. Issues with container starting, nvidia-smi related errors, nvml errors, nvidia-container-cli device errors, or bandwidth verification issues could get your machine deverified. If deverified and the issue is resolved, your machine will go from deverified back to unverified."
+        "name": "Maintain Verified Status",
+        "text": "Once verified, monitor health including uptime, thermals, and power, responding to alerts promptly. Keep drivers/CUDA on compatible latest stable versions. Maintain stable symmetric bandwidth. Avoid downgrading hardware capacity or allowing thermal, power, or bandwidth instability."
+      },
+      {
+        "@type": "HowToStep",
+        "name": "Recover From Deverification",
+        "text": "If deverified, investigate red error indicators quickly and review logs/metrics. Common causes include network instability, hardware/system errors, GPU issues, container failures, or policy violations. Fix the underlying issue and restore stability - the system will automatically transition back to Verified status."
       }
     ]
   })
 }} />
 
-Verification follows a transition flow like this: unverified -> verified -> deverified -> unverified -> ....
+## States & Lifecycle
 
-Verification is mostly for higher end machines, mining rigs may never be verified.
+**States:** Unverified → Verified → (potentially) Deverified → Unverified  → ...
 
-Right now the only machines which can expect fast verification are $10k+: H100 or A100 80GB
+**Lifecycle:** Machines automatically move between these states based on performance and reliability factors. Once verified, a machine will remain verified unless issues arise — such as failing health checks or reliability standards — which could lead to deverification.
 
-If you have a higher end machine that is not tested quickly in a day or so let us know.
+---
 
-8x4090, 4xA6000 - should be tested in less than a week, especially if you have a number of them.
+## How It Works
 
-For machines that are not high-end machines or machines from datacenters, verification is relatively random even if your unverified machine is meeting these requirements.
+Verification is entirely automated by proprietary algorithms that assess each machine’s operational health and performance. Only machines meeting platform reliability and performance thresholds are marked Verified. There is no manual intervention, ensuring consistency, scalability, and objectivity.
 
-We run more random auto verification roughly about once a week.
+---
 
-The only manual verification tests are for datacenters and high end machines.
+## Host Responsibilities (Always)
 
-For datacenter partner inquiries email us at [contact@vast.ai](mailto\:contact@vast.ai) directly.
+- Keep systems stable, well-cooled, and correctly configured.  
+- Maintain compatible drivers/CUDA and dependable, symmetric networking.  
+- Run only platform jobs (schedule work via Create Job).  
+- When issues arise, fix them promptly—the automation will update status.
 
-You can use the [vast cli](https://github.com/vast-ai/vast-cli) "self-test machine" command to see if a machine meets all of the requirements, resolve any issues, and have a better chance of getting verified.
+---
 
-## Unverified
+## State Details & Guidance
 
-These are typically new machines that have not been tested by Vast's team/software.
+### Unverified
+
+**What it means:** Newly added machines or machines under evaluation. The system hasn't yet completed enough testing to confirm platform standards. This is not a judgment of quality—only that no platform guarantee exists yet.
+
+**Do**
+- Maintain steady uptime during evaluation.  
+- Ensure drivers/CUDA and networking are correctly installed and reachable.  
+- Keep the environment clean; schedule work via Create Job only.
+
+**Avoid**
+- Reboots or configuration changes.  
+- Unrelated background workloads that consume GPU/CPU/IO.
+
+---
 
-In order for your unverified machine to be verified, it must follow these minimum guidelines:
+### Minimum Guidelines for Listing on Vast.ai
+
+In order to be listed on Vast.ai, the machine must follow these minimum guidelines:
 
 ```text Text
-Ubuntu 18.04 or newer (required)
-Dedicated machines only - the machine shouldn't be doing other stuff while rented
-Fast, reliable internet: at least 10Mbps per machine.
-10-series Nvidia GPU or MI25 or newer Radeon Instinct series GPU or Radeon VII or Radeon Pro VII or Radeon RX 7900 (GRE/XT/XTX); or Radeon Pro W7900/W7800. Other 6000 series or newer Radeon RX/Pro W series GPUs may be supported; but may not be searchable using standard filters for AMD ROCm.
-At least 1 physical CPU core (2 hyperthreads) per GPU.
-Your CPU must support AVX instruction set (not all lower end CPUs support this).
-At least 4GBM of system RAM per GPU.
-Fast SSD storage with at least 128GB per GPU.
-at least 1X PCIE for every 2.5 TFLOPS of GPU performance.
-All GPUs on the machine must be of the same type.
-An open port range mapped to each machine.
+- Ubuntu 18.04 or newer (required)  
+- Dedicated machines only - the machine shouldn't be doing other stuff while rented  
+- Fast, reliable internet: at least 10Mbps per machine.  
+- 10-series Nvidia GPU or MI25 or newer Radeon Instinct series GPU or Radeon VII or Radeon Pro VII or Radeon RX 7900 (GRE/XT/XTX); or Radeon Pro W7900/W7800. Other 6000 series or newer Radeon RX/Pro W series GPUs may be supported; but may not be searchable using standard filters for AMD ROCm.  
+- At least 1 physical CPU core (2 hyperthreads) per GPU.  
+- Your CPU must support AVX instruction set (not all lower end CPUs support this).  
+- At least 4GB of system RAM per GPU.  
+- Fast SSD storage with at least 128GB per GPU.  
+- At least 1X PCIe for every 2.5 TFLOPS of GPU performance.  
+- All GPUs on the machine must be of the same type.  
+- An open port range mapped to each machine.
 ```
+---
 
-The ideal machine will exceed these minimum guidelines, as some workloads require even more CPU, RAM, disk, and PCIE performance. Also keep in mind that everything scales with GPU power, so a 3090 will need more ram, a better cpu, etc, than a 3060.
-Note that changing components that degrade machine performance (e.g, decreasing the number of GPUs, RAM capacity, etc) is not supported after the machine is created, and will result in the machine being deverified. Upgrading the machine is ok (e.g, increasing the number of GPUs, RAM capacity, etc), but it will take some time before the change is reflected in search.
+### Additional Requirements for Verification
 
 In order for your unverified machine to be verified, it must also meet the following minimum requirements:
 
 ```text Text
-CUDA version greater than or equal to 12.0
-Reliability of 90%
-At least 3 open ports per GPU (100 recommended)
-Internet download speed of 500 Mb/s
-Internet upload speed of 500 Mb/s
-GPU RAM of 7 GB
+- CUDA version greater than or equal to 12.0  
+- Reliability of 90%  
+- At least 3 open ports per GPU (100 recommended)  
+- Internet download speed of 500 Mb/s  
+- Internet upload speed of 500 Mb/s  
+- GPU RAM of 7 GB
 ```
+**Note:** High-end GPUs are more likely to be verified. Machines with datacenter GPUs such as B200, H200, H100, A100, etc., and those with premium GPUs such as RTX PRO 6000 WS, 8xRTX 5090, 8xRTX 4090, etc., **automatically** receive prioritized verification processing due to their high demand and performance capabilities.
+
+---
+
 
-## Verified
+### Verified
+
+**What it means:** The machine passed automated checks for reliability, network stability, operational health, and performance. A Verified machine consistently delivers server services to platform standards.
+
+**Do**
+- Monitor health (uptime, thermals, power) and respond to alerts.  
+- Keep drivers/CUDA on compatible, **latest** stable versions.  
+- Maintain stable, symmetric bandwidth.
+
+**Avoid**
+- Downgrading hardware capacity (e.g., reducing GPU count, disk or RAM).  
+- Allowing thermal, power, or bandwidth instability under load.
+
+---
 
-If you've been verified by meeting those minimum requirements and having your machine being randomly selected or having higher end machine(s) or datacenter(s), continue to meet these requirements and try to prevent the issues listed in the Deverified section of this guide.
+### Deverified
 
-## Deverified
+**What it means:** A previously Verified machine no longer meets requirements. Continuous monitoring detects sustained degradation.
 
-Your machine could go from verified -> deverified if an error in your machine is autodetected.
+**Common causes**
+- Network instability, closed ports or low bandwidth.  
+- Hardware/system errors (e.g., failing storage, insufficient PCIe bandwidth).  
+- GPU issues (e.g., nvidia-smi/NVML failures, container device init errors).  
+- Container launch failures or repeated runtime exceptions.  
+- Detected abuse or policy violations.
 
-If you see a red error on your machine card, you should try to investigate and resolve that because it could get you deverified.
+**Recovery:** Fix the issue and restore stability; the system will automatically transition back to Verified.
 
-Some issues that could get your machine deverified are issues with a container starting in your machine, nvidia-smi related errors, nvml errors, nvidia-container-cli device errors, or issues with verifying the bandwidth of your machine.
+**Do**
+- Investigate red error indicators quickly; review logs/metrics.  
+- Validate thermal/power headroom and bandwidth under load.  
+- Re-check health after changes to confirm resolution.
 
-If the issue is resolved, then your machine will go from deverified -> unverified.
+**Avoid**
+- Ignoring warnings or allowing instability to persist.  
+- Reducing hardware below the created specification.
+---
\ No newline at end of file

From 743c790d18db1c8962fda5dd5c3c45b4138ae604 Mon Sep 17 00:00:00 2001
From: hanran-y <hanran@vast.ai>
Date: Tue, 4 Nov 2025 17:36:09 -0800
Subject: [PATCH 2/5] update deverified section and other fix

---
 .../host/understanding-verification.mdx       | 66 +++++++-------
 documentation/host/verification-stages.mdx    | 90 ++++++++++---------
 2 files changed, 84 insertions(+), 72 deletions(-)

diff --git a/documentation/host/understanding-verification.mdx b/documentation/host/understanding-verification.mdx
index 9d55dce..ca386ce 100644
--- a/documentation/host/understanding-verification.mdx
+++ b/documentation/host/understanding-verification.mdx
@@ -46,11 +46,13 @@ updatedAt: Mon Nov 03 2025 17:30:00 GMT+0000 (Coordinated Universal Time)
   })
 }} />
 
+# Understanding Verification
+
 ## How Verification Works
 
 Verification is **fully automated and powered by proprietary algorithms** that continuously evaluate each machine’s operational health and performance.
 
-Only machines that meet the platform’s defined reliability and performance thresholds are marked as **Verified**.  
+Only machines that meet the platform's defined reliability and performance thresholds are marked as **Verified**.
 
 This process involves **no manual intervention**, ensuring consistent, scalable, and objective verification across all systems.
 
@@ -64,15 +66,15 @@ To qualify, a machine must pass minimum baseline, and health/stability checks. B
 
 **Do**
 
-- Maintain consistent uptime with minimal downtime.  
-- Keep network connectivity stable; avoid jitter and drops.  
-- Manage thermals and power to prevent throttling.  
-- Proactively monitor hardware health and perform maintenance.  
+- Maintain consistent uptime with minimal downtime.
+- Keep network connectivity stable; avoid jitter and drops.
+- Manage thermals and power to prevent throttling.
+- Proactively monitor hardware health and perform maintenance.
 
 **Avoid**
 
-- Frequent restarts or unplanned outages.  
-- Overheating, undervolting, or unstable power delivery.  
+- Frequent restarts or unplanned outages.
+- Overheating, undervolting, or unstable power delivery.
 
 > **Note:** Higher reliability greatly improves verification likelihood. Sustained ≥99.99% (up to 99.9999%+) uptime is typically favored.
 
@@ -84,42 +86,42 @@ To qualify, a machine must pass minimum baseline, and health/stability checks. B
 
 ### Hardware
 
-- **GPU:** Type, memory, and count matter. Newer datacenter/workstation GPUs are prioritized (e.g., B200 > H200 >> 5090 > 4070).  
-- **VRAM:** More VRAM improves performance profiles.  
-- **GPU Count:** For the same GPU type, more GPUs increase verification likelihood (e.g., 8×5090 >> 2×5090 > 1×5090).  
-- **PCIe Bandwidth:** Adequate throughput is essential; bottlenecks depress DLPerf and overall performance.  
-- **CPU:** Favor strong, server-grade CPUs; actual measured performance matters.  
-- **Storage:** Both capacity and bandwidth (e.g., NVMe) impact responsiveness and reliability.  
+- **GPU:** Type, memory, and count matter. Newer datacenter/workstation GPUs are prioritized (e.g., B200 > H200 >> 5090 > 4070).
+- **VRAM:** More VRAM improves performance profiles.
+- **GPU Count:** For the same GPU type, more GPUs increase verification likelihood (e.g., 8×5090 >> 2×5090 > 1×5090).
+- **PCIe Bandwidth:** Adequate throughput is essential; bottlenecks depress DLPerf and overall performance.
+- **CPU:** Favor strong, server-grade CPUs; actual measured performance matters.
+- **Storage:** Both capacity and bandwidth (e.g., NVMe) impact responsiveness and reliability.
 
 ### Network
 
-- High-speed, symmetric, stable bandwidth is favored.  
-- Ensure required ports are open and accessible; a static IP helps.  
+- High-speed, symmetric, stable bandwidth is favored.
+- Ensure required ports are open and accessible; a static IP helps.
 
 ### Virtualization
 
-- Enabling VM support significantly improves verification likelihood.  
+- Enabling VM support significantly improves verification likelihood.
 
 ### Software
 
-- Drivers/CUDA must be correctly installed and compatible (use stable **latest** releases).  
-- Keep systems clean; run workloads via Create Job only.  
+- Drivers/CUDA must be correctly installed and compatible (use stable **latest** releases).
+- Keep systems clean; run workloads via Create Job only.
 
 ### System Optimization & Upgrades
 
-- Balanced scaling matters (CPU/RAM/PCIe/bandwidth commensurate with GPU tier).  
-- Do not reduce hardware after creation (e.g., fewer GPUs/RAM) – this will trigger Deverified.  
-- Upgrades (adding GPUs/RAM) are allowed but may take time to reflect across the platform.  
+- Balanced scaling matters (CPU/RAM/PCIe/bandwidth commensurate with GPU tier).
+- Do not reduce hardware after creation (e.g., fewer GPUs/RAM) – this will trigger Deverified.
+- Upgrades (adding GPUs/RAM) are allowed but may take time to reflect across the platform.
 
 **Do**
 
-- Verify GPU PCIe connections provide full bandwidth and are not throttled.  
-- Keep the latest drivers/CUDA aligned with workloads.  
-- Confirm required ports and end-to-end reachability.  
+- Verify GPU PCIe connections provide full bandwidth and are not throttled.
+- Keep the latest drivers/CUDA aligned with workloads.
+- Confirm required ports and end-to-end reachability.
 
 **Avoid**
 
-- Pairing high-end GPUs with under-provisioned CPU/RAM.  
+- Pairing high-end GPUs with under-provisioned CPU/RAM.
 - Letting hidden background services consume resources.
 
 ---
@@ -130,12 +132,12 @@ To qualify, a machine must pass minimum baseline, and health/stability checks. B
 
 **Do**
 
-- Use the **latest** compatible drivers/CUDA.  
-- Eliminate PCIe, thermal, and power bottlenecks to maintain sustained clocks.  
+- Use the **latest** compatible drivers/CUDA.
+- Eliminate PCIe, thermal, and power bottlenecks to maintain sustained clocks.
 
 **Avoid**
 
-- Misconfigurations that suppress benchmark performance.  
+- Misconfigurations that suppress benchmark performance.
 
 ---
 
@@ -147,12 +149,12 @@ To qualify, a machine must pass minimum baseline, and health/stability checks. B
 
 **Do**
 
-- Offer in-demand GPU models with adequate VRAM and balanced resources.  
-- Maintain strong reliability to remain attractive once listed.  
+- Offer in-demand GPU models with adequate VRAM and balanced resources.
+- Maintain strong reliability to remain attractive once listed.
 
 **Avoid**
 
-- Niche/mismatched configurations with low renter interest.  
+- Niche/mismatched configurations with low renter interest.
 
 ---
 
@@ -164,7 +166,7 @@ To qualify, a machine must pass minimum baseline, and health/stability checks. B
 | Network | Symmetric, stable bandwidth; open ports | Upgrade links; verify routing/ports; monitor jitter/loss |
 | Hardware | Modern GPUs/CPUs; adequate PCIe & RAM | Favor DC/workstation GPUs; ensure PCIe lanes; match CPU/RAM to GPU tier |
 | Storage | Throughput and reliability | Prefer NVMe; monitor SMART; ensure sustained bandwidth |
-| Virtualization | VM capability enabled | Enable in BIOS, enable IOMMU. |
+| Virtualization | VM capability enabled | Enable in BIOS; enable IOMMU. |
 | Software | Correct drivers/CUDA; clean system | Install latest, stable, compatible versions; use Create Job only |
 | DLPerf | High real-world throughput | Fix PCIe/thermal bottlenecks; maintain clocks; correct drivers |
 | Supply & Demand | Alignment with renter needs | Choose popular GPUs/VRAM; balance specs; maintain reliability |
diff --git a/documentation/host/verification-stages.mdx b/documentation/host/verification-stages.mdx
index f5d8075..53701c4 100644
--- a/documentation/host/verification-stages.mdx
+++ b/documentation/host/verification-stages.mdx
@@ -25,22 +25,22 @@ updatedAt: Mon Nov 03 2025 12:50:03 GMT+0000 (Coordinated Universal Time)
       {
         "@type": "HowToStep",
         "name": "Maintain Host Responsibilities",
-        "text": "Keep systems stable, well-cooled, and correctly configured. Maintain compatible drivers/CUDA and dependable symmetric networking. Run only platform jobs via Create Job. When issues arise, fix them promptly as the automation will update verification status accordingly."
+        "text": "Keep systems stable, well-cooled, and correctly configured. Maintain compatible drivers/CUDA and dependable symmetric networking. When running jobs on your machines on the platform, only do so via the jobs tab or the Create Job command in the CLI. When issues arise, fix them promptly as the automation will update verification status accordingly."
       },
       {
         "@type": "HowToStep",
         "name": "Optimize During Unverified Stage",
-        "text": "While unverified, maintain steady uptime during evaluation. Ensure drivers/CUDA and networking are correctly installed and reachable. Keep environment clean by scheduling work via Create Job only. Avoid reboots, configuration changes, and unrelated background workloads."
+        "text": "While unverified, maintain steady uptime during evaluation. Ensure drivers/CUDA and networking are correctly installed and reachable. Keep environment clean by running jobs only through the Jobs tab or the create job CLI command. Avoid unnecessary reboots, configuration changes, and unrelated background workloads."
       },
       {
         "@type": "HowToStep",
         "name": "Maintain Verified Status",
-        "text": "Once verified, monitor health including uptime, thermals, and power, responding to alerts promptly. Keep drivers/CUDA on compatible latest stable versions. Maintain stable symmetric bandwidth. Avoid downgrading hardware capacity or allowing thermal, power, or bandwidth instability."
+        "text": "Once verified, be sure to continue monitoring the health of your machine, including uptime, thermals, and power. You should respond to any alerts promptly. Keep drivers/CUDA on compatible latest stable versions. Maintain stable symmetric bandwidth. Avoid downgrading hardware capacity or allowing thermal, power, or bandwidth instability."
       },
       {
         "@type": "HowToStep",
         "name": "Recover From Deverification",
-        "text": "If deverified, investigate red error indicators quickly and review logs/metrics. Common causes include network instability, hardware/system errors, GPU issues, container failures, or policy violations. Fix the underlying issue and restore stability - the system will automatically transition back to Verified status."
+        "text": "When a previously Verified machine no longer meets system requirements, it becomes temporarily deverified. A red error indicator will appear in the Machines tab—use it to identify and investigate the issue through your logs or metrics. Common causes include network instability, hardware or GPU errors, container launch failures, or detected policy violations. Fix the underlying problem and restore stability; once continuous monitoring confirms healthy operation, the system will automatically return your machine to Verified status. If the issue is fixed but not automatically cleared, a Vast.ai team member may manually verify your machine"
       }
     ]
   })
@@ -62,9 +62,9 @@ Verification is entirely automated by proprietary algorithms that assess each ma
 
 ## Host Responsibilities (Always)
 
-- Keep systems stable, well-cooled, and correctly configured.  
-- Maintain compatible drivers/CUDA and dependable, symmetric networking.  
-- Run only platform jobs (schedule work via Create Job).  
+- Keep systems stable, well-cooled, and correctly configured.
+- Maintain compatible drivers/CUDA and dependable, symmetric networking.
+- Run jobs only through the Jobs tab or the `create job` CLI command.
 - When issues arise, fix them promptly—the automation will update status.
 
 ---
@@ -76,12 +76,12 @@ Verification is entirely automated by proprietary algorithms that assess each ma
 **What it means:** Newly added machines or machines under evaluation. The system hasn't yet completed enough testing to confirm platform standards. This is not a judgment of quality—only that no platform guarantee exists yet.
 
 **Do**
-- Maintain steady uptime during evaluation.  
-- Ensure drivers/CUDA and networking are correctly installed and reachable.  
+- Maintain steady uptime during evaluation.
+- Ensure drivers/CUDA and networking are correctly installed and reachable.
 - Keep the environment clean; schedule work via Create Job only.
 
 **Avoid**
-- Reboots or configuration changes.  
+- Unnecessary reboots or configuration changes.
 - Unrelated background workloads that consume GPU/CPU/IO.
 
 ---
@@ -91,16 +91,16 @@ Verification is entirely automated by proprietary algorithms that assess each ma
 In order to be listed on Vast.ai, the machine must follow these minimum guidelines:
 
 ```text Text
-- Ubuntu 18.04 or newer (required)  
-- Dedicated machines only - the machine shouldn't be doing other stuff while rented  
-- Fast, reliable internet: at least 10Mbps per machine.  
-- 10-series Nvidia GPU or MI25 or newer Radeon Instinct series GPU or Radeon VII or Radeon Pro VII or Radeon RX 7900 (GRE/XT/XTX); or Radeon Pro W7900/W7800. Other 6000 series or newer Radeon RX/Pro W series GPUs may be supported; but may not be searchable using standard filters for AMD ROCm.  
-- At least 1 physical CPU core (2 hyperthreads) per GPU.  
-- Your CPU must support AVX instruction set (not all lower end CPUs support this).  
-- At least 4GB of system RAM per GPU.  
-- Fast SSD storage with at least 128GB per GPU.  
-- At least 1X PCIe for every 2.5 TFLOPS of GPU performance.  
-- All GPUs on the machine must be of the same type.  
+- Ubuntu 18.04 or newer (required)
+- Dedicated machines only - the machine shouldn't be doing other stuff while rented
+- Fast, reliable internet: at least 10Mbps per machine.
+- 10-series Nvidia GPU or MI25 or newer Radeon Instinct series GPU or Radeon VII or Radeon Pro VII or Radeon RX 7900 (GRE/XT/XTX); or Radeon Pro W7900/W7800. Other 6000 series or newer Radeon RX/Pro W series GPUs may be supported; but may not be searchable using standard filters for AMD ROCm.
+- At least 1 physical CPU core (2 hyperthreads) per GPU.
+- Your CPU must support AVX instruction set (not all lower end CPUs support this).
+- At least 4 GB of system RAM per GPU.
+- Fast SSD storage with at least 128GB per GPU.
+- At least 1X PCIe for every 2.5 TFLOPS of GPU performance.
+- All GPUs on the machine must be of the same type.
 - An open port range mapped to each machine.
 ```
 ---
@@ -110,14 +110,14 @@ In order to be listed on Vast.ai, the machine must follow these minimum guidelin
 In order for your unverified machine to be verified, it must also meet the following minimum requirements:
 
 ```text Text
-- CUDA version greater than or equal to 12.0  
-- Reliability of 90%  
-- At least 3 open ports per GPU (100 recommended)  
-- Internet download speed of 500 Mb/s  
-- Internet upload speed of 500 Mb/s  
+- CUDA version greater than or equal to 12.0
+- Reliability of 90%
+- At least 3 open ports per GPU (100 recommended)
+- Internet download speed of 500 Mb/s
+- Internet upload speed of 500 Mb/s
 - GPU RAM of 7 GB
 ```
-**Note:** High-end GPUs are more likely to be verified. Machines with datacenter GPUs such as B200, H200, H100, A100, etc., and those with premium GPUs such as RTX PRO 6000 WS, 8xRTX 5090, 8xRTX 4090, etc., **automatically** receive prioritized verification processing due to their high demand and performance capabilities.
+> **Note:** High-end GPUs are more likely to be verified. Machines with datacenter GPUs such as B200, H200, H100, A100, etc., and those with premium GPUs such as RTX PRO 6000 WS, 8xRTX 5090, 8xRTX 4090, etc., receive prioritized verification processing due to their high demand and performance capabilities.
 
 ---
 
@@ -127,35 +127,45 @@ In order for your unverified machine to be verified, it must also meet the follo
 **What it means:** The machine passed automated checks for reliability, network stability, operational health, and performance. A Verified machine consistently delivers server services to platform standards.
 
 **Do**
-- Monitor health (uptime, thermals, power) and respond to alerts.  
-- Keep drivers/CUDA on compatible, **latest** stable versions.  
+- Monitor health (uptime, thermals, power) and respond to alerts.
+- Keep drivers/CUDA on compatible, **latest** stable versions.
 - Maintain stable, symmetric bandwidth.
 
 **Avoid**
-- Downgrading hardware capacity (e.g., reducing GPU count, disk or RAM).  
+- Downgrading hardware capacity (e.g., reducing GPU count, disk or RAM).
 - Allowing thermal, power, or bandwidth instability under load.
 
 ---
 
 ### Deverified
 
-**What it means:** A previously Verified machine no longer meets requirements. Continuous monitoring detects sustained degradation.
+**What it means:**
+A previously Verified machine no longer meets requirements. System continuous monitoring detects sustained degradation.
+
+**When will deverification happen?**
+- When the hosting software detects an error, your machine is automatically — but **temporarily** — deverified. It will appear as *Unverified* in search results until the underlying issue is resolved.
+
+**How should I begin fixing it?**
+- A **red error indicator** will appear on your machine in the Machines tab. Use this message to identify and investigate the issue in your logs or metrics.
+
+**Recovery:**
+Fix the issue and restore stability; the system will **automatically** transition back to Verified once system confirms healthy operation.
+This process may take some time, as the system ensures that the issue is fully resolved before restoring verification.
 
 **Common causes**
-- Network instability, closed ports or low bandwidth.  
-- Hardware/system errors (e.g., failing storage, insufficient PCIe bandwidth).  
-- GPU issues (e.g., nvidia-smi/NVML failures, container device init errors).  
-- Container launch failures or repeated runtime exceptions.  
+- Network instability, closed ports, or low bandwidth.
+- Hardware/system errors (e.g., failing storage, insufficient PCIe bandwidth).
+- GPU issues (e.g., nvidia-smi/NVML failures, container device init errors).
+- Container launch failures or repeated runtime exceptions.
 - Detected abuse or policy violations.
 
-**Recovery:** Fix the issue and restore stability; the system will automatically transition back to Verified.
-
 **Do**
-- Investigate red error indicators quickly; review logs/metrics.  
-- Validate thermal/power headroom and bandwidth under load.  
+- Investigate red error indicators quickly; review logs and metrics.
+- Validate thermal/power headroom and bandwidth under load.
 - Re-check health after changes to confirm resolution.
 
 **Avoid**
-- Ignoring warnings or allowing instability to persist.  
+- Ignoring warnings or allowing instability to persist.
 - Reducing hardware below the created specification.
----
\ No newline at end of file
+
+> **Note:** If you’ve fixed the issue but the system doesn’t automatically detect the resolution, a Vast.ai team member may need to manually verify that your machine is functioning correctly and clear the error.

From ba4e4227d3a1ce7aefe4ff4b6759cac7da7a4cdd Mon Sep 17 00:00:00 2001
From: hanran-y <hanran@vast.ai>
Date: Tue, 4 Nov 2025 17:42:46 -0800
Subject: [PATCH 3/5] change verify to check

---
 documentation/host/verification-stages.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/documentation/host/verification-stages.mdx b/documentation/host/verification-stages.mdx
index 53701c4..da2393a 100644
--- a/documentation/host/verification-stages.mdx
+++ b/documentation/host/verification-stages.mdx
@@ -168,4 +168,4 @@ This process may take some time, as the system ensures that the issue is fully r
 - Ignoring warnings or allowing instability to persist.
 - Reducing hardware below the created specification.
 
-> **Note:** If you’ve fixed the issue but the system doesn’t automatically detect the resolution, a Vast.ai team member may need to manually verify that your machine is functioning correctly and clear the error.
+> **Note:** If you’ve fixed the issue but the system doesn’t automatically detect the resolution, a Vast.ai team member may need to manually check that your machine is functioning correctly and clear the error.

From dd8ac26076d09c2b65b72456cd22f90ca9324c6f Mon Sep 17 00:00:00 2001
From: hanran-y <hanran@vast.ai>
Date: Tue, 4 Nov 2025 17:59:11 -0800
Subject: [PATCH 4/5] delete double title

---
 documentation/host/understanding-verification.mdx | 2 --
 1 file changed, 2 deletions(-)

diff --git a/documentation/host/understanding-verification.mdx b/documentation/host/understanding-verification.mdx
index ca386ce..2f16181 100644
--- a/documentation/host/understanding-verification.mdx
+++ b/documentation/host/understanding-verification.mdx
@@ -46,8 +46,6 @@ updatedAt: Mon Nov 03 2025 17:30:00 GMT+0000 (Coordinated Universal Time)
   })
 }} />
 
-# Understanding Verification
-
 ## How Verification Works
 
 Verification is **fully automated and powered by proprietary algorithms** that continuously evaluate each machine’s operational health and performance.

From de2a4931a43464df61d3c7c6d72eb48afc7e0290 Mon Sep 17 00:00:00 2001
From: hanran-y <hanran@vast.ai>
Date: Tue, 4 Nov 2025 18:02:56 -0800
Subject: [PATCH 5/5] small fix

---
 documentation/host/verification-stages.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/documentation/host/verification-stages.mdx b/documentation/host/verification-stages.mdx
index da2393a..0fca101 100644
--- a/documentation/host/verification-stages.mdx
+++ b/documentation/host/verification-stages.mdx
@@ -56,7 +56,7 @@ updatedAt: Mon Nov 03 2025 12:50:03 GMT+0000 (Coordinated Universal Time)
 
 ## How It Works
 
-Verification is entirely automated by proprietary algorithms that assess each machine’s operational health and performance. Only machines meeting platform reliability and performance thresholds are marked Verified. There is no manual intervention, ensuring consistency, scalability, and objectivity.
+Verification is **entirely automated by proprietary algorithms** that assess each machine’s operational health and performance. Only machines meeting platform reliability and performance thresholds are marked Verified. There is **no manual intervention**, ensuring consistency, scalability, and objectivity.
 
 ---