Evidence gaps need attention before interpreting regional changes
2026-10-03 to 2026-10-04
23 regions with new changes or gaps
Brazil South, Central India, East Asia, East US 2, East US 2 EUAP, France Central, India South Central, Italy North, Japan East, North Central US, North Europe, Norway East, Norway West, South Africa North, South Central US, South East Asia, Switzerland North, UK South, West Europe, West US, West US 2, West US 3, github-global
26New listings
0New delistings
10Known restorations
1,745Tracked absences
13Evidence gaps
Absence tracking starts at 2026-09-05; older disappearances may not be included.
What this proves: read-only catalog/list or measurement evidence.
Not quota, capacity, successful deployment, an outage, or confirmed retirement.
Methodology
Changes relevant to you
One listing = one feature in one region
All regions and services. Groups below separate new changes from continuing observations.
A GitHub Models endpoint inference-latency observation, not an Azure regional model-catalog result. A model identifier observed by this modality; exact capabilities are not verified.
This records an inference request to the configured GitHub Models endpoint.
Context limits, input/output modalities, licensing, and tool support need exact-model review.
Timing describes the configured request and runner-to-endpoint path, not universal model speed or an Azure region. GitHub documents GitHub Models as retired on July 30, 2026; retained observations do not prove the service is currently available. 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.
No trustworthy current result. Do not treat this as an unavailable service.
VM SKUs
797VM sizes
1,269 feature-region records
New listings
26 feature-region records
Brazil South, East Asia, North Central US
Example: Standard D248ds V7 VM size. Listing coverage: 9 → 10 regions.
New regional listing of an already observed feature.
Exact capability unverified
Standard D248ds V7 VM size
VM catalog entry with unverified exact specifications.
This signal represents a name in the regional VM size catalog, not a running VM.
Exact CPU, memory, disk, and network specifications are not verified for this identifier.
Exact SKU specifications have not been verified. A regional SKU listing does not establish quota, capacity, price, successful deployment, or measured performance. Temporary disks are not durable application storage.
Catalog/list evidence only; verify exact requirements before changing regional plans.
Known restorations
10 feature-region records
North Central US
Example: Standard E128ds V7 VM size. Listing coverage: 10 → 11 regions.
Exact capability unverified
Standard E128ds V7 VM size
VM catalog entry with unverified exact specifications.
This signal represents a name in the regional VM size catalog, not a running VM.
Exact CPU, memory, disk, and network specifications are not verified for this identifier.
Exact SKU specifications have not been verified. A regional SKU listing does not establish quota, capacity, price, successful deployment, or measured performance. Temporary disks are not durable application storage.
Catalog/list evidence only; verify exact requirements before changing regional plans.
Tracked absences
1,233 feature-region records
Brazil South, Central India, East US 2, East US 2 EUAP, France Central, India South Central, Italy North, Japan East, North Europe, Norway East, Norway West, South Africa North, South Central US, South East Asia, Switzerland North, UK South, West Europe, West US, West US 2, West US 3
Example: Standard Nv12s V2 VM size. Listing coverage: 6 → 6 regions.
Exact capability unverified
Standard Nv12s V2 VM size
VM catalog entry with unverified exact specifications.
This signal represents a name in the regional VM size catalog, not a running VM.
Exact CPU, memory, disk, and network specifications are not verified for this identifier.
Exact SKU specifications have not been verified. A regional SKU listing does not establish quota, capacity, price, successful deployment, or measured performance. Temporary disks are not durable application storage.
Previously tracked delistings remain absent. No new delistings does not mean recovery.
Azure AI models
18AI models
512 feature-region records
Tracked absences
512 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: llama 3 2 11b vision instruct model from Meta (version 1). Listing coverage: 0 → 0 regions.
Category context
llama 3 2 11b vision instruct.1 - meta
A model identifier observed by this modality; exact capabilities are not verified.
Catalog presence identifies a provider/model/version candidate, not its tested abilities.
Context limits, input/output modalities, licensing, and tool support need exact-model review.
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.
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.
Observation history and comparison coverage
1,745 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-10-03T09:23:19.985772+00:00 Current snapshot: 2026-10-04T10:06:20.538738+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.
Exact changes and supporting evidence
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.