At a glance — since 2026-11-01Daily regional evidence
What this proves: read-only catalog/list or measurement evidence; not quota, capacity, successful deployment, outage, or confirmed retirement. Methodology
Returned in: ↩ North Central US
Australia East, Brazil South, Canada Central, Central India, Central US, Central US EUAP, Chile Central, East US, East US 2, East US 2 EUAP, France Central, Germany West Central, India South Central, Italy North, Korea Central, North Central US, North Europe, Norway East, Norway West, Poland Central, South Africa North, South Central US, South East Asia, Spain Central, Sweden Central, Switzerland North, UAE North, UK South, West Europe, West US, West US 2, West US 3
Absence tracking starts at 2026-09-05; older disappearances may not be included.
All regions and services. Groups below separate new changes from continuing observations.
2,425 feature-region records
2 feature-region records
North Central US
Example: Standard E160ads V7 VM size. Listing coverage: 20 → 21 regions.
Documented family
Standard_E160ads_v7 - Memory optimized VM size
Standard_E160ads_v7 is a memory optimized VM size decoded from Azure's naming convention.
Naming-convention decoding does not verify memory, CPU model, GPU model, disk throughput, network bandwidth, quota, capacity, price, successful deployment, or measured performance.
Read more: Azure VM sizes naming conventions · Memory optimized family overview
Catalog/list evidence only; verify exact requirements before changing regional plans.
2,423 feature-region records
Australia East, Brazil South, Canada Central, Central India, Central US, Central US EUAP, Chile Central, East US, East US 2, East US 2 EUAP, France Central, Germany West Central, India South Central, Italy North, Korea Central, North Central US, North Europe, Norway East, Norway West, Poland Central, South Africa North, South Central US, South East Asia, Spain Central, Sweden Central, Switzerland North, UAE North, UK South, West Europe, West US, West US 2, West US 3
Example: Standard Nv16as V4 VM size. Listing coverage: 10 → 10 regions.
Documented family
Standard_NV16as_v4 - GPU visualization optimized VM size
Standard_NV16as_v4 is a gpu visualization optimized VM size decoded from Azure's naming convention.
Naming-convention decoding does not verify memory, CPU model, GPU model, disk throughput, network bandwidth, quota, capacity, price, successful deployment, or measured performance.
Read more: Azure VM sizes naming conventions · GPU visualization optimized family overview
Previously tracked delistings remain absent. No new delistings does not mean recovery.
672 feature-region records
672 feature-region records
Australia East, Brazil South, Canada Central, Canada East, Central India, Central US, East Asia, East US, East US 2, France Central, Germany West Central, Italy North, Japan East, Japan West, Korea Central, North Central US, North Europe, Norway East, Poland Central, South Africa North, South Central US, South East Asia, South India, Spain Central, Sweden Central, Switzerland North, Switzerland West, UAE North, UK South, UK West, West Central US, West Europe, West US, West US 2, West US 3
Example: deepseek r1 0528 model from deepseek (version 1). Listing coverage: 0 → 0 regions.
Category context
deepseek r1 0528 (catalog version 1) - deepseek
A model identifier observed by this modality; exact capabilities are not verified.
No exact model capability or version is verified. The source provides category context only. Regional model-catalog evidence does not establish quota, account approval, deployment type, inference access, content filtering, performance, or data residency.
Read more: deepseek model catalog (category only) · Search Microsoft Learn for this exact identifier (not verified)
Previously tracked delistings remain absent. No new delistings does not mean recovery.
No matching change or evidence-gap records. This is not a deployment-health assessment.
3,095 tracked listings remain absent. Zero new delistings does not mean previous absences recovered. Absence tracking starts at 2026-09-05; older disappearances may not be included.
Previous snapshot: 2026-11-01T03:44:20.404189+00:00
Current snapshot: 2026-11-02T03:43:26.432675+00:00
Snapshot timestamps do not establish freshness of every carried-forward modality. The monitor does not assess your running workloads.
Added check records: 0; removed check records: 0. Changes to the observation set do not establish provider intent.
Grouped by feature. Coverage counts are scan-wide; region and service filters limit the listed records.
Open to load the complete records, without rerunning probes.
Optional: take a 15-second reading check For deliberate reader testing. For everyday feedback, use the floating feedback buttons.