This optional research check is not the main feedback path.
For maintainer observations, use page feedback instead.
Founder or repeat-reader observations are qualitative, not unbiased first-time-reader results.
Read the briefing, then answer from memory: what changed most, where, and what does the evidence prove?
This measures comprehension, not whether you liked the design.
Privacy: answers and timing stay in this page's memory.
No analytics, cookies, background submissions, or browser storage.
Ordinary page/evidence requests still reach the static host.
Opening a GitHub draft sends its summary to GitHub, but does not submit an issue.
You review it and choose the final Submit on GitHub.
Public feedback: submitted issues and attachments in this repository are public.
Do not share secrets or private information. The dashboard needs no backend or authentication token.
Use one attempt. Switching away from this tab marks it interrupted; it does not silently pause the clock.
You may stop or skip at any time. Do not enter names, email addresses, subscription IDs, or private workload details.
No screenshot capture is offered in this timed check. Use normal page feedback for optional screenshots.
Case: 2026-09-09. The timer limits reading, not answering.
This is a self-selected check, not a controlled experiment.
Choose your perspective and prior familiarity to begin.
15 seconds
Since the previous scan Scan-wide briefing
54 VM sizes gained listings across 2 regions
2026-09-08 to 2026-09-09
New changes across services: East US, South East Asia
108New listings
0New delistings
0Known restorations
0Tracked absences
0Evidence 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.
VM SKUs
54VM sizes
108 feature-region records
New listings
108 feature-region records
East US, South East Asia
Example: Standard D128nds V6 VM size. Listing coverage: 49 → 51 regions.
New regional listing of an already observed feature.
Documented feature
Standard_D128nds_v6 - network-optimized general-purpose VM
Dndsv6 is a network-optimized general-purpose VM series using Intel Xeon Platinum 8573C processors.
128 vCPUs and 512 GiB RAM, from the documented size table.
General-purpose configuration with 4 GiB per vCPU.
A regional SKU listing does not establish quota, capacity, price, successful deployment, or measured performance. Temporary disks are not durable application storage.
Planning compute here? Compare the listed sizes with your workload requirements.
No matching change or evidence-gap records. This is not a deployment-health assessment.
Observation history and comparison coverage
0 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-09-08T08:21:39.929634+00:00 Current snapshot: 2026-09-09T03:48:53.553965+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.
This is not submitted. Open a GitHub draft to review a human-readable summary
of your answers, case/view IDs, timing, and eligibility. No raw JSON packet goes in the URL.
Only your final Submit on GitHub creates the public issue.
The full local record includes your answers, timing, role, case ID, and presentation version,
with no expected answers or automatic grade. You may download JSON and manually attach it
to the draft. Review it first: attachments upload immediately when pasted or attached on GitHub,
even before you submit the issue.
GitHub may log the draft URL and requires its own sign-in to submit. The dashboard never asks for a token.
If the summary exceeds the draft URL limit, the full local result and JSON download remain available;
nothing is truncated or automatically sent.