Skip to content
DoctorDODemo data
Signed in as Alex Morgan, alex.morgan@contosoai.example, Admin.

Demo data: ContosoAI (fictitious). Nothing here is a real company, device or person.

← Overview

Estate · demo data

Estate topology

All 42 sites, and the path their bytes take through the internet breakout at Dublin HQ.

Every site

Estate topology: every site, the path its bytes take, and where they came fromEurope15 sites · 20,380 devices · 57% efficiencyIRELAND · 2FRANCE · 3UNITED KINGDOM · 4NETHERLANDS · 1GERMANY · 4SPAIN · 1North America11 sites · 10,995 devices · 41% efficiencyUNITED STATES (1 OF 2) · 4UNITED STATES (2 OF 2) · 4CANADA · 3Asia Pacific11 sites · 9,325 devices · 35% efficiencyINDIA · 4SINGAPORE · 1JAPAN · 3AUSTRALIA · 3Nordics4 sites · 4,000 devices · 81% efficiencySWEDEN · 1DENMARK · 1NORWAY · 1FINLAND · 1Remote workers1 site · 1,300 devices · 0% efficiencyMicrosoft CDN336 TBHTTP sourceInternet breakout320 TBat Dublin HQWide area networkevery site reaches the Microsoft CDN through the breakoutDublin HQ5,600 devices69%431 issues · 38 criticalCache47.9 TBServingPeers9.1 TBGroup (2) modeDublin HQ5,600 devices · 69%Isolation? · BreakoutCork1,000 devices70%60 issues · 1 criticalCache8.7 TBServingPeers1.6 TBGroup (2) modeCork1,000 devices · 70%Isolation?Paris1,900 devices69%133 issues · 5 criticalCache16.3 TBServingPeers2.9 TBGroup (2) modeParis1,900 devices · 69%Isolation?Lyon610 devices36%381 issues · 281 criticalCache1.6 TBPart-wayPeers1.6 TBGroup (2) modeLyon610 devices · 36%Isolation?Toulouse120 devices28%22 issuesDPNo cachePeers558 GBGroup (2) modeToulouse120 devices · 28%4 flagsLondon3,000 devices68%246 issues · 19 criticalCache25.0 TBServingPeers4.0 TBGroup (2) modeLondon3,000 devices · 68%Isolation?Manchester1,300 devices36%860 issues · 618 criticalCache3.4 TBPart-wayPeers3.4 TBGroup (2) modeManchester1,300 devices · 36%Isolation? · Autopilot…Edinburgh520 devices25%38 issuesDPNo cachePeers1.9 TBGroup (2) modeEdinburgh520 devices · 25%Isolation?Belfast190 devices21%18 issuesDPNo cachePeers566 GBGroup (2) modeBelfast190 devices · 21%2 flagsAmsterdam1,300 devices69%87 issues · 7 criticalCache11.1 TBServingPeers2.0 TBGroup (2) modeAmsterdam1,300 devices · 69%Isolation?Munich2,000 devices70%148 issues · 7 criticalCache17.3 TBServingPeers3.7 TBGroup (2) modeMunich2,000 devices · 70%Isolation?Berlin1,100 devices34%784 issues · 556 criticalCache2.7 TBPart-wayPeers2.6 TBGroup (2) modeBerlin1,100 devices · 34%Isolation? · Autopilot…Frankfurt900 devices0%807 issues · 540 criticalDPNo cachePeersGroup (2) modeFrankfurt900 devices · 0%4 flagsHamburg160 devices0%132 issues · 83 criticalDPNo cachePeersGroup (2) modeHamburg160 devices · 0%4 flagsMadrid680 devices25%50 issuesDPNo cachePeers2.5 TBGroup (2) modeMadrid680 devices · 25%Isolation?San Francisco2,500 devices68%218 issues · 15 criticalCache21.0 TBServingPeers3.4 TBGroup (2) modeSan Francisco2,500 devices · 68%Isolation?New York1,800 devices68%137 issues · 6 criticalCache15.2 TBServingPeers2.7 TBGroup (2) modeNew York1,800 devices · 68%Isolation?Seattle1,600 devices28%1,033 criticalCache3.7 TBPart-wayPeers2.8 TBGroup (2) modeSeattle1,600 devices · 28%2 flags · Autopilot del…Austin1,100 devices34%739 issues · 551 criticalCache2.8 TBPart-wayPeers2.7 TBGroup (2) modeAustin1,100 devices · 34%Isolation? · Autopilot…Boston760 devices0%556 issues · 372 criticalDPNo cachePeersGroup (2) modeBoston760 devices · 0%3 flagsChicago690 devices0%566 issues · 372 criticalDPNo cachePeersGroup (2) modeChicago690 devices · 0%3 flagsDenver140 devices27%20 issuesDPNo cachePeers577 GBGroup (2) modeDenver140 devices · 27%3 flagsAtlanta105 devices20%16 issues · 2 criticalDPNo cachePeers330 GBGroup (2) modeAtlanta105 devices · 20%4 flagsToronto1,300 devices34%888 issues · 657 criticalCache3.3 TBPart-wayPeers3.2 TBGroup (2) modeToronto1,300 devices · 34%Isolation?Vancouver600 devices24%60 issues · 3 criticalDPNo cachePeers2.1 TBGroup (2) modeVancouver600 devices · 24%Isolation?Montreal400 devices24%34 issuesDPNo cachePeers1.4 TBGroup (2) modeMontreal400 devices · 24%Isolation?Bengaluru2,700 devices24%1,856 criticalCache5.0 TBPart-wayPeers3.9 TBGroup (2) modeBengaluru2,700 devices · 24%2 flags · Autopilot del…Hyderabad1,400 devices27%1,615 issues · 881 criticalCache2.6 TBPart-wayPeers2.5 TBGroup (2) modeHyderabad1,400 devices · 27%Isolation? · Autopilot…Pune440 devices18%125 issues · 5 criticalDPNo cachePeers1.1 TBGroup (2) modePune440 devices · 18%Isolation?Chennai105 devices20%35 issues · 2 criticalDPNo cachePeers329 GBGroup (2) modeChennai105 devices · 20%4 flagsSingapore1,300 devices68%91 issues · 5 criticalCache10.5 TBServingPeers1.8 TBGroup (2) modeSingapore1,300 devices · 68%Isolation?Tokyo1,200 devices69%66 issues · 3 criticalCache10.3 TBServingPeers1.9 TBGroup (2) modeTokyo1,200 devices · 69%Isolation?Osaka420 devices0%328 issues · 219 criticalDPNo cachePeersGroup (2) modeOsaka420 devices · 0%2 flagsFukuoka80 devices20%11 issuesDPNo cachePeers228 GBGroup (2) modeFukuoka80 devices · 20%3 flagsSydney1,000 devices30%752 issues · 553 criticalCache2.1 TBPart-wayPeers2.1 TBGroup (2) modeSydney1,000 devices · 30%Isolation? · Autopilot…Melbourne590 devices23%49 issues · 1 criticalDPNo cachePeers2.0 TBGroup (2) modeMelbourne590 devices · 23%Isolation?Perth90 devices19%101 issues · 78 criticalCachePart-wayPeers229 GBGroup (2) modePerth90 devices · 19%3 flags · Autopilot del…Stockholm1,600 devices80%68 issues · 2 criticalCache13.3 TBServingPeers5.0 TBGroup (2) modeStockholm1,600 devices · 80%Isolation?Copenhagen1,000 devices81%41 issues · 2 criticalCache8.3 TBServingPeers3.3 TBGroup (2) modeCopenhagen1,000 devices · 81%Isolation?Oslo750 devices80%31 issues · 1 criticalCache6.4 TBServingPeers2.4 TBGroup (2) modeOslo750 devices · 80%Isolation?Helsinki650 devices81%28 issuesCache5.5 TBServingPeers2.1 TBGroup (2) modeHelsinki650 devices · 81%Isolation?Remote workers (VPN)1,300 devices0%260 issues · 9 criticalPeerspeering offRemote workers (VPN)1,300 devices · 0%No upload10 GbpsDatacentre25.6 TB500 MbpsSD-WAN4.5 TB1 GbpsMetro Ethernet8.6 TB200 MbpsSD-WAN5.7 TB20 MbpsMPLS1.4 TB1 GbpsMetro Ethernet13.9 TB500 MbpsSD-WAN12.1 TB200 MbpsSD-WAN5.8 TB50 MbpsMPLS2.0 TB10 GbpsDatacentre5.9 TB1 GbpsMetro Ethernet9.1 TB500 MbpsSD-WAN10.1 TB500 MbpsSD-WAN13.7 TB50 MbpsMPLS2.4 TB200 MbpsSD-WAN7.4 TB1 GbpsMetro Ethernet11.7 TB1 GbpsMetro Ethernet8.4 TB1 GbpsMetro Ethernet16.6 TB500 MbpsSD-WAN10.6 TB200 MbpsSD-WAN11.1 TB200 MbpsSD-WAN10.6 TB30 MbpsMPLS1.5 TB25 MbpsLTE1.3 TB500 MbpsSD-WAN12.8 TB200 MbpsSD-WAN6.5 TB100 MbpsSD-WAN4.4 TB1 GbpsMetro Ethernet28.6 TB500 MbpsSD-WAN14.0 TB100 MbpsSD-WAN4.8 TB20 MbpsMPLS1.3 TB1 GbpsMetro Ethernet5.8 TB1 GbpsMetro Ethernet5.4 TB100 MbpsSD-WAN6.5 TB10 MbpsLTE930 GB500 MbpsSD-WAN9.8 TB200 MbpsSD-WAN6.6 TB20 MbpsLTE974 GB1 GbpsMetro Ethernet4.5 TB1 GbpsMetro Ethernet2.7 TB500 MbpsSD-WAN2.1 TB500 MbpsSD-WAN1.7 TB16.0 TB320 TB320 TB128 TB95.5 TB84.7 TB11.1 TB16.0 TB · path not in the site facts

Drag to pan. Hold Ctrl and scroll, or pinch, to zoom; the page scrolls as usual otherwise. With the diagram focused: + and − zoom, the arrow keys pan, 0 fits. Tab moves between sites; Enter opens one.

Across 42 sites and 46,000 devices, 336 TB came from the Microsoft CDN, 244 TB from Connected Cache and 84.5 TB from peers in the period. Dublin HQ is the internet breakout: every other site reaches the Microsoft CDN over the WAN through it.

  • Microsoft CDN (HTTP)
  • Connected Cache
  • LAN · Group · Internet peers
  • No bytes
  • Policy
  • Blocked
  • Line weight follows bytes
  • Connected Cache serving
  • part-way: not every subnet reaches it
  • legacy distribution point (DP), no cache
  • Pills on a site: sharing flags and Autopilot delay
  • Line weight follows bytes on one scale (square root), so branches stay visible beside the hub
Describe this diagram

Across 42 sites and 46,000 devices, 336 TB came from the Microsoft CDN, 244 TB from Connected Cache and 84.5 TB from peers in the period. Dublin HQ is the internet breakout: every other site reaches the Microsoft CDN over the WAN through it.

The path

  • Microsoft CDN: 336 TB in the period.
  • Internet breakout at Dublin HQ: 320 TB of CDN bytes leave through it.
  • Wide area network: carries every described site’s CDN bytes to the breakout.

Regions and countries

  • Europe: 15 sites · 20,380 devices · 57% efficiency on the WAN, 128 TB from the CDN. Countries: Ireland (2 sites), France (3 sites), United Kingdom (4 sites), Netherlands (1 site), Germany (4 sites), Spain (1 site).
  • North America: 11 sites · 10,995 devices · 41% efficiency on the WAN, 95.5 TB from the CDN. Countries: United States (1 of 2) (4 sites), United States (2 of 2) (4 sites), Canada (3 sites).
  • Asia Pacific: 11 sites · 9,325 devices · 35% efficiency on the WAN, 84.7 TB from the CDN. Countries: India (4 sites), Singapore (1 site), Japan (3 sites), Australia (3 sites).
  • Nordics: 4 sites · 4,000 devices · 81% efficiency on the WAN, 11.1 TB from the CDN. Countries: Sweden (1 site), Denmark (1 site), Norway (1 site), Finland (1 site).
  • Remote workers: 1 site · 1,300 devices · 0% efficiency, joined straight to the CDN (16.0 TB), path not in the site facts.

Every site (42)

  • Dublin HQ (Europe, Ireland): 5,600 devices, 69% efficiency, 431 issues · 38 critical; the internet breakout itself, on a 10 Gbps Datacentre link, carrying 25.6 TB from the CDN; Connected Cache serving from dp01.dub.contosoai.example, 47.9 TB; 9.1 TB from Group ID peers; 1 sharing flag: Peers are offered but not reached on 10.10.128.0/20: client isolation suspected.
  • Cork (Europe, Ireland): 1,000 devices, 70% efficiency, 60 issues · 1 critical; WAN link to Dublin HQ: 500 Mbps SD-WAN, 6 ms round trip, carrying 4.5 TB from the CDN; Connected Cache serving from dp01.ork.contosoai.example, 8.7 TB; 1.6 TB from Group ID peers; 1 sharing flag: Peers are offered but not reached on 10.11.128.0/20: client isolation suspected.
  • Paris (Europe, France): 1,900 devices, 69% efficiency, 133 issues · 5 critical; WAN link to Dublin HQ: 1 Gbps Metro Ethernet, 22 ms round trip, carrying 8.6 TB from the CDN; Connected Cache serving from dp01.par.contosoai.example, 16.3 TB; 2.9 TB from Group ID peers; 1 sharing flag: Peers are offered but not reached on 10.20.128.0/20: client isolation suspected.
  • Lyon (Europe, France): 610 devices, 36% efficiency, 381 issues · 281 critical; WAN link to Dublin HQ: 200 Mbps SD-WAN, 26 ms round trip, carrying 5.7 TB from the CDN; Connected Cache part-way (2 of 3 subnets reach it), 1.6 TB; 1.6 TB from Group ID peers; 1 sharing flag: Peers are offered but not reached on 10.21.128.0/20: client isolation suspected.
  • Toulouse (Europe, France): 120 devices, 28% efficiency, 22 issues; WAN link to Dublin HQ: 20 Mbps MPLS, 30 ms round trip, carrying 1.4 TB from the CDN; still a legacy distribution point, no Connected Cache; 558 GB from Group ID peers; 4 sharing flags: Peers are offered but not reached on 10.22.128.0/20: client isolation suspected; One device carries 70% of what its peer group shares; DOMinFileSizeToCache is below Microsoft's table for a peer group of 67; DOMinFileSizeToCache is below Microsoft's table for a peer group of 53.
  • London (Europe, United Kingdom): 3,000 devices, 68% efficiency, 246 issues · 19 critical; WAN link to Dublin HQ: 1 Gbps Metro Ethernet, 14 ms round trip, carrying 13.9 TB from the CDN; Connected Cache serving from dp01.lon.contosoai.example, 25.0 TB; 4.0 TB from Group ID peers; 1 sharing flag: Peers are offered but not reached on 10.12.128.0/20: client isolation suspected.
  • Manchester (Europe, United Kingdom): 1,300 devices, 36% efficiency, 860 issues · 618 critical; WAN link to Dublin HQ: 500 Mbps SD-WAN, 12 ms round trip, carrying 12.1 TB from the CDN; Connected Cache part-way (3 of 4 subnets reach it), 3.4 TB; 3.4 TB from Group ID peers; 1 sharing flag: Peers are offered but not reached on 10.13.128.0/20: client isolation suspected; Autopilot delay: builds wait about 12 minutes (DoctorDO’s model).
  • Edinburgh (Europe, United Kingdom): 520 devices, 25% efficiency, 38 issues; WAN link to Dublin HQ: 200 Mbps SD-WAN, 13 ms round trip, carrying 5.8 TB from the CDN; still a legacy distribution point, no Connected Cache; 1.9 TB from Group ID peers; 1 sharing flag: Peers are offered but not reached on 10.14.128.0/20: client isolation suspected.
  • Belfast (Europe, United Kingdom): 190 devices, 21% efficiency, 18 issues; WAN link to Dublin HQ: 50 Mbps MPLS, 9 ms round trip, carrying 2.0 TB from the CDN; still a legacy distribution point, no Connected Cache; 566 GB from Group ID peers; 2 sharing flags: Peers are offered but not reached on 10.15.128.0/20: client isolation suspected; DOMinFileSizeToCache is below Microsoft's table for a peer group of 84.
  • Amsterdam (Europe, Netherlands): 1,300 devices, 69% efficiency, 87 issues · 7 critical; WAN link to Dublin HQ: 10 Gbps Datacentre, 16 ms round trip, carrying 5.9 TB from the CDN; Connected Cache serving from dp01.ams.contosoai.example, 11.1 TB; 2.0 TB from Group ID peers; 1 sharing flag: Peers are offered but not reached on 10.23.128.0/20: client isolation suspected.
  • Munich (Europe, Germany): 2,000 devices, 70% efficiency, 148 issues · 7 critical; WAN link to Dublin HQ: 1 Gbps Metro Ethernet, 28 ms round trip, carrying 9.1 TB from the CDN; Connected Cache serving from dp01.muc.contosoai.example, 17.3 TB; 3.7 TB from Group ID peers; 1 sharing flag: Peers are offered but not reached on 10.16.128.0/20: client isolation suspected.
  • Berlin (Europe, Germany): 1,100 devices, 34% efficiency, 784 issues · 556 critical; WAN link to Dublin HQ: 500 Mbps SD-WAN, 30 ms round trip, carrying 10.1 TB from the CDN; Connected Cache part-way (3 of 4 subnets reach it), 2.7 TB; 2.6 TB from Group ID peers; 1 sharing flag: Peers are offered but not reached on 10.17.128.0/20: client isolation suspected; Autopilot delay: builds wait about 18 minutes (DoctorDO’s model).
  • Frankfurt (Europe, Germany): 900 devices, 0% efficiency, 807 issues · 540 critical; WAN link to Dublin HQ: 500 Mbps SD-WAN, 24 ms round trip, carrying 13.7 TB from the CDN; still a legacy distribution point, no Connected Cache; 0 B from Group ID peers; 4 sharing flags: Peers are offered but not reached on 10.18.128.0/20: client isolation suspected; Peers are refused on 10.18.1.0/24 because inbound TCP 7680 is blocked on the devices (not client isolation); Peers are refused on 10.18.2.0/24 because inbound TCP 7680 is blocked on the devices (not client isolation); Peers are refused on 10.18.3.0/24 because inbound TCP 7680 is blocked on the devices (not client isolation).
  • Hamburg (Europe, Germany): 160 devices, 0% efficiency, 132 issues · 83 critical; WAN link to Dublin HQ: 50 Mbps MPLS, 27 ms round trip, carrying 2.4 TB from the CDN; still a legacy distribution point, no Connected Cache; 0 B from Group ID peers; 4 sharing flags: Peers are refused on 10.19.1.0/25 because inbound TCP 7680 is blocked on the devices (not client isolation); Peers are offered but not reached on 10.19.128.0/20: client isolation suspected; DOMinFileSizeToCache is below Microsoft's table for a peer group of 83; DOMinFileSizeToCache is below Microsoft's table for a peer group of 77.
  • Madrid (Europe, Spain): 680 devices, 25% efficiency, 50 issues; WAN link to Dublin HQ: 200 Mbps SD-WAN, 32 ms round trip, carrying 7.4 TB from the CDN; still a legacy distribution point, no Connected Cache; 2.5 TB from Group ID peers; 1 sharing flag: Peers are offered but not reached on 10.24.128.0/20: client isolation suspected.
  • San Francisco (North America, United States): 2,500 devices, 68% efficiency, 218 issues · 15 critical; WAN link to Dublin HQ: 1 Gbps Metro Ethernet, 140 ms round trip, carrying 11.7 TB from the CDN; Connected Cache serving from dp01.sfo.contosoai.example, 21.0 TB; 3.4 TB from Group ID peers; 1 sharing flag: Peers are offered but not reached on 10.25.128.0/20: client isolation suspected.
  • New York (North America, United States): 1,800 devices, 68% efficiency, 137 issues · 6 critical; WAN link to Dublin HQ: 1 Gbps Metro Ethernet, 80 ms round trip, carrying 8.4 TB from the CDN; Connected Cache serving from dp01.nyc.contosoai.example, 15.2 TB; 2.7 TB from Group ID peers; 1 sharing flag: Peers are offered but not reached on 10.27.128.0/20: client isolation suspected.
  • Seattle (North America, United States): 1,600 devices, 28% efficiency, 1,391 issues · 1,033 critical; WAN link to Dublin HQ: 1 Gbps Metro Ethernet, 150 ms round trip, carrying 16.6 TB from the CDN; Connected Cache part-way (4 of 5 subnets reach it), 3.7 TB; 2.8 TB from Group ID peers; 2 sharing flags: Peers are offered but not reached on 10.26.128.0/20: client isolation suspected; Peers are refused on 10.26.2.0/24 because inbound TCP 7680 is blocked on the devices (not client isolation); Autopilot delay: builds wait about 24 minutes (DoctorDO’s model).
  • Austin (North America, United States): 1,100 devices, 34% efficiency, 739 issues · 551 critical; WAN link to Dublin HQ: 500 Mbps SD-WAN, 120 ms round trip, carrying 10.6 TB from the CDN; Connected Cache part-way (3 of 4 subnets reach it), 2.8 TB; 2.7 TB from Group ID peers; 1 sharing flag: Peers are offered but not reached on 10.28.128.0/20: client isolation suspected; Autopilot delay: builds wait about 12 minutes (DoctorDO’s model).
  • Boston (North America, United States): 760 devices, 0% efficiency, 556 issues · 372 critical; WAN link to Dublin HQ: 200 Mbps SD-WAN, 75 ms round trip, carrying 11.1 TB from the CDN; still a legacy distribution point, no Connected Cache; 0 B from Group ID peers; 3 sharing flags: Peers are offered but not reached on 10.29.128.0/20: client isolation suspected; Peers are refused on 10.29.1.0/24 because inbound TCP 7680 is blocked on the devices (not client isolation); Peers are refused on 10.29.2.0/24 because inbound TCP 7680 is blocked on the devices (not client isolation).
  • Chicago (North America, United States): 690 devices, 0% efficiency, 566 issues · 372 critical; WAN link to Dublin HQ: 200 Mbps SD-WAN, 100 ms round trip, carrying 10.6 TB from the CDN; still a legacy distribution point, no Connected Cache; 0 B from Group ID peers; 3 sharing flags: Peers are offered but not reached on 10.30.128.0/20: client isolation suspected; Peers are refused on 10.30.1.0/24 because inbound TCP 7680 is blocked on the devices (not client isolation); Peers are refused on 10.30.2.0/24 because inbound TCP 7680 is blocked on the devices (not client isolation).
  • Denver (North America, United States): 140 devices, 27% efficiency, 20 issues; WAN link to Dublin HQ: 30 Mbps MPLS, 125 ms round trip, carrying 1.5 TB from the CDN; still a legacy distribution point, no Connected Cache; 577 GB from Group ID peers; 3 sharing flags: Peers are offered but not reached on 10.31.128.0/20: client isolation suspected; DOMinFileSizeToCache is below Microsoft's table for a peer group of 70; DOMinFileSizeToCache is below Microsoft's table for a peer group of 70.
  • Atlanta (North America, United States): 105 devices, 20% efficiency, 16 issues · 2 critical; WAN link to Dublin HQ: 25 Mbps LTE, 90 ms round trip, carrying 1.3 TB from the CDN; still a legacy distribution point, no Connected Cache; 330 GB from Group ID peers; 4 sharing flags: Peers are offered but not reached on 10.32.128.0/20: client isolation suspected; One device carries 79% of what its peer group shares; DOMinFileSizeToCache is below Microsoft's table for a peer group of 46; DOMinFileSizeToCache is below Microsoft's table for a peer group of 59.
  • Toronto (North America, Canada): 1,300 devices, 34% efficiency, 888 issues · 657 critical; WAN link to Dublin HQ: 500 Mbps SD-WAN, 90 ms round trip, carrying 12.8 TB from the CDN; Connected Cache part-way (3 of 4 subnets reach it), 3.3 TB; 3.2 TB from Group ID peers; 1 sharing flag: Peers are offered but not reached on 10.33.128.0/20: client isolation suspected.
  • Vancouver (North America, Canada): 600 devices, 24% efficiency, 60 issues · 3 critical; WAN link to Dublin HQ: 200 Mbps SD-WAN, 150 ms round trip, carrying 6.5 TB from the CDN; still a legacy distribution point, no Connected Cache; 2.1 TB from Group ID peers; 1 sharing flag: Peers are offered but not reached on 10.34.128.0/20: client isolation suspected.
  • Montreal (North America, Canada): 400 devices, 24% efficiency, 34 issues; WAN link to Dublin HQ: 100 Mbps SD-WAN, 85 ms round trip, carrying 4.4 TB from the CDN; still a legacy distribution point, no Connected Cache; 1.4 TB from Group ID peers; 1 sharing flag: Peers are offered but not reached on 10.35.128.0/20: client isolation suspected.
  • Bengaluru (Asia Pacific, India): 2,700 devices, 24% efficiency, 2,745 issues · 1,856 critical; WAN link to Dublin HQ: 1 Gbps Metro Ethernet, 130 ms round trip, carrying 28.6 TB from the CDN; Connected Cache part-way (5 of 6 subnets reach it), 5.0 TB; 3.9 TB from Group ID peers; 2 sharing flags: Peers are offered but not reached on 10.36.128.0/20: client isolation suspected; Peers are refused on 10.36.2.0/24 because inbound TCP 7680 is blocked on the devices (not client isolation); Autopilot delay: builds wait about 48 minutes (DoctorDO’s model).
  • Hyderabad (Asia Pacific, India): 1,400 devices, 27% efficiency, 1,615 issues · 881 critical; WAN link to Dublin HQ: 500 Mbps SD-WAN, 135 ms round trip, carrying 14.0 TB from the CDN; Connected Cache part-way (3 of 4 subnets reach it), 2.6 TB; 2.5 TB from Group ID peers; 1 sharing flag: Peers are offered but not reached on 10.37.128.0/20: client isolation suspected; Autopilot delay: builds wait about 36 minutes (DoctorDO’s model).
  • Pune (Asia Pacific, India): 440 devices, 18% efficiency, 125 issues · 5 critical; WAN link to Dublin HQ: 100 Mbps SD-WAN, 140 ms round trip, carrying 4.8 TB from the CDN; still a legacy distribution point, no Connected Cache; 1.1 TB from Group ID peers; 1 sharing flag: Peers are offered but not reached on 10.38.128.0/20: client isolation suspected.
  • Chennai (Asia Pacific, India): 105 devices, 20% efficiency, 35 issues · 2 critical; WAN link to Dublin HQ: 20 Mbps MPLS, 150 ms round trip, carrying 1.3 TB from the CDN; still a legacy distribution point, no Connected Cache; 329 GB from Group ID peers; 4 sharing flags: Peers are offered but not reached on 10.39.128.0/20: client isolation suspected; One device carries 79% of what its peer group shares; DOMinFileSizeToCache is below Microsoft's table for a peer group of 46; DOMinFileSizeToCache is below Microsoft's table for a peer group of 59.
  • Singapore (Asia Pacific, Singapore): 1,300 devices, 68% efficiency, 91 issues · 5 critical; WAN link to Dublin HQ: 1 Gbps Metro Ethernet, 165 ms round trip, carrying 5.8 TB from the CDN; Connected Cache serving from dp01.sin.contosoai.example, 10.5 TB; 1.8 TB from Group ID peers; 1 sharing flag: Peers are offered but not reached on 10.40.128.0/20: client isolation suspected.
  • Tokyo (Asia Pacific, Japan): 1,200 devices, 69% efficiency, 66 issues · 3 critical; WAN link to Dublin HQ: 1 Gbps Metro Ethernet, 230 ms round trip, carrying 5.4 TB from the CDN; Connected Cache serving from dp01.tyo.contosoai.example, 10.3 TB; 1.9 TB from Group ID peers; 1 sharing flag: Peers are offered but not reached on 10.44.128.0/20: client isolation suspected.
  • Osaka (Asia Pacific, Japan): 420 devices, 0% efficiency, 328 issues · 219 critical; WAN link to Dublin HQ: 100 Mbps SD-WAN, 235 ms round trip, carrying 6.5 TB from the CDN; still a legacy distribution point, no Connected Cache; 0 B from Group ID peers; 2 sharing flags: Peers are offered but not reached on 10.45.128.0/20: client isolation suspected; Peers are refused on 10.45.1.0/24 because inbound TCP 7680 is blocked on the devices (not client isolation).
  • Fukuoka (Asia Pacific, Japan): 80 devices, 20% efficiency, 11 issues; WAN link to Dublin HQ: 10 Mbps LTE, 240 ms round trip, carrying 930 GB from the CDN; still a legacy distribution point, no Connected Cache; 228 GB from Group ID peers; 3 sharing flags: Peers are offered but not reached on 10.46.128.0/20: client isolation suspected; DOMinFileSizeToCache is below Microsoft's table for a peer group of 35; DOMinFileSizeToCache is below Microsoft's table for a peer group of 45.
  • Sydney (Asia Pacific, Australia): 1,000 devices, 30% efficiency, 752 issues · 553 critical; WAN link to Dublin HQ: 500 Mbps SD-WAN, 280 ms round trip, carrying 9.8 TB from the CDN; Connected Cache part-way (2 of 3 subnets reach it), 2.1 TB; 2.1 TB from Group ID peers; 1 sharing flag: Peers are offered but not reached on 10.41.128.0/20: client isolation suspected; Autopilot delay: builds wait about 60 minutes, past the Enrollment Status Page time-out (DoctorDO’s model).
  • Melbourne (Asia Pacific, Australia): 590 devices, 23% efficiency, 49 issues · 1 critical; WAN link to Dublin HQ: 200 Mbps SD-WAN, 285 ms round trip, carrying 6.6 TB from the CDN; still a legacy distribution point, no Connected Cache; 2.0 TB from Group ID peers; 1 sharing flag: Peers are offered but not reached on 10.42.128.0/20: client isolation suspected.
  • Perth (Asia Pacific, Australia): 90 devices, 19% efficiency, 101 issues · 78 critical; WAN link to Dublin HQ: 20 Mbps LTE, 300 ms round trip, carrying 974 GB from the CDN; Connected Cache part-way (0 of 2 subnets reach it), 0 B; 229 GB from Group ID peers; 3 sharing flags: Peers are offered but not reached on 10.43.128.0/20: client isolation suspected; DOMinFileSizeToCache is below Microsoft's table for a peer group of 40; DOMinFileSizeToCache is below Microsoft's table for a peer group of 50; Autopilot delay: builds wait about 120 minutes, past the Enrollment Status Page time-out (DoctorDO’s model).
  • Stockholm (Nordics, Sweden): 1,600 devices, 80% efficiency, 68 issues · 2 critical; WAN link to Dublin HQ: 1 Gbps Metro Ethernet, 38 ms round trip, carrying 4.5 TB from the CDN; Connected Cache serving from dp01.sto.contosoai.example, 13.3 TB; 5.0 TB from Group ID peers; 1 sharing flag: Peers are offered but not reached on 10.47.128.0/20: client isolation suspected.
  • Copenhagen (Nordics, Denmark): 1,000 devices, 81% efficiency, 41 issues · 2 critical; WAN link to Dublin HQ: 1 Gbps Metro Ethernet, 30 ms round trip, carrying 2.7 TB from the CDN; Connected Cache serving from dp01.cph.contosoai.example, 8.3 TB; 3.3 TB from Group ID peers; 1 sharing flag: Peers are offered but not reached on 10.48.128.0/20: client isolation suspected.
  • Oslo (Nordics, Norway): 750 devices, 80% efficiency, 31 issues · 1 critical; WAN link to Dublin HQ: 500 Mbps SD-WAN, 36 ms round trip, carrying 2.1 TB from the CDN; Connected Cache serving from dp01.osl.contosoai.example, 6.4 TB; 2.4 TB from Group ID peers; 1 sharing flag: Peers are offered but not reached on 10.49.128.0/20: client isolation suspected.
  • Helsinki (Nordics, Finland): 650 devices, 81% efficiency, 28 issues; WAN link to Dublin HQ: 500 Mbps SD-WAN, 44 ms round trip, carrying 1.7 TB from the CDN; Connected Cache serving from dp01.hel.contosoai.example, 5.5 TB; 2.1 TB from Group ID peers; 1 sharing flag: Peers are offered but not reached on 10.50.128.0/20: client isolation suspected.
  • Remote workers (VPN) (Remote workers): 1,300 devices, 0% efficiency, 260 issues · 9 critical; 16.0 TB from the CDN (path not in the site facts); peering off in Simple (99) mode; 1 sharing flag: 1,300 devices download but cannot upload to peers.