Connected evidence
Follow a shared identifier, source page or planning group across source records. Dates show chronology; a connection does not establish cause, a shared rollout or applicability to your environment.
AzureMonitor.EastUS
Lead record- Why these records are connected
- Records sharing a curated source identity or subject key; inspect each source before treating them as one change.
- Connection key
azure-tag:AzureMonitor.EastUS- Public snapshot refreshed
- today 00:39 UTC
- Distinct source events
- 2
- Source records represented
- 2
Current snapshot membership is shown here. Source histories and cited revisions remain on each record. Future source targets are labelled separately from observed changes. Browse connections.
Evidence in chronological order
- Wed 7 Oct · Dated source evidence · Azure service tag changed AzureMonitor.EastUSChanged tag: 128 IPv4 addresses newly covered (1 prefix added, 0 removed). Observed publication 420 → 421. Source: Derived from the linked evidence · source check: not recorded hereYour review: not selected in your watchlist or stack; no review is inferred.Changed tag: 128 IPv4 addresses newly covered (1 prefix added, 0 removed). Observed publication 420 → 421.
- Thu 29 Oct · Dated source evidence · Azure service tag changed AzureMonitor.EastUSChanged tag: 352 IPv4 addresses and 2 IPv6 ranges newly covered (7 prefixes added, 0 removed). Observed publication 423 → 424. Source: Derived from the linked evidence · source check: not recorded hereYour review: not selected in your watchlist or stack; no review is inferred.Changed tag: 352 IPv4 addresses and 2 IPv6 ranges newly covered (7 prefixes added, 0 removed). Observed publication 423 → 424.