-
-
Notifications
You must be signed in to change notification settings - Fork 43
Remove Canada regions from speed test #118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
- Removed Canada Central (Toronto) and Canada East (Quebec) from locations - Updated azure-regions-coverage.txt to reflect 45 total regions (down from 47) - Removed reference to Canada storage accounts contributor from index.jsx - Updated stats: 12 restricted access + 2 Canada regions removed = 14 unavailable - Updated Availability Zones count: 36 regions with AZ (from 38) Co-authored-by: richorama <353138+richorama@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR removes Canada region support from the Azure Speed Test application per user request. The changes eliminate Canada Central and Canada East regions from the location list and update all related documentation and references.
Changes:
- Removed Canada Central (Toronto) and Canada East (Quebec) region entries from locations configuration
- Updated documentation to reflect reduction from 49 to 45 total regions and removed Canada from geography coverage
- Removed contributor acknowledgment for Canada storage accounts
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| lib/locations.js | Removed Canada Central and Canada East region definitions |
| index.jsx | Removed contributor reference for Canada storage accounts |
| azure-regions-coverage.txt | Updated region counts, geography list, and availability zone statistics to reflect Canada region removal |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
azure-regions-coverage.txt
Outdated
| - **Regions in Tool**: 49 | ||
| - **Regions Not Available**: 10 (all restricted access) | ||
| - **Regions in Tool**: 45 | ||
| - **Regions Not Available**: 14 (12 restricted access regions, 2 Canada regions removed by user preference) |
Copilot
AI
Jan 15, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The math doesn't add up correctly. With 59 total Azure regions and 45 in the tool, there should be 14 regions not available. However, the explanation '12 restricted access regions, 2 Canada regions removed' only accounts for 14 total. The original documentation stated 10 restricted regions, so the new calculation should be '10 restricted access regions, 4 Canada regions removed' or the total should be recalculated.
| - **Regions Not Available**: 14 (12 restricted access regions, 2 Canada regions removed by user preference) | |
| - **Regions Not Available**: 14 (10 restricted access regions, 4 Canada regions removed by user preference) |
azure-regions-coverage.txt
Outdated
| 10. Australia Central | ||
| 11. Jio India West |
Copilot
AI
Jan 15, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The list shows 11 regions without Availability Zones, but the summary states only 9 regions (20%) lack Availability Zones. The count should be updated to match the actual list, or items should be removed from the list to match the stated count of 9.
- Removed mention of "user preference" from region removal reason - Corrected Availability Zones count: 35 regions with AZ (78%), 10 without (22%) - Updated list of regions without AZ to include all 10 regions correctly Co-authored-by: richorama <353138+richorama@users.noreply.github.com>
Removed Canada Central (Toronto) and Canada East (Quebec) regions from the Azure speed test tool per user request.
Changes
The tool now tests 45 Azure regions instead of 47.
Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
jioindiawest47365.z1.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)speedtestaic18632.z45.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)speedtestamw18632.z48.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)speedtestapac18632.z24.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)speedtestaqc18632.z1.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)speedtestat53726.z49.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)speedtestcac18632.z9.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)speedtestcae18632.z27.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)speedtestchile53201.z47.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)speedtestden18632.z1.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)speedtestein18632.z38.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)speedtestene18632.z1.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)speedtestesc218632.z1.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)speedtestesn18632.z1.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)speedtestfrc18632.z28.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)speedtestjpw18632.z31.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)speedtestkoreasout18632.z32.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)speedtestmeic18632.z39.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)speedtestmmc18632.z41.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)speedtestne18632.z16.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)speedtestnea18632.z15.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)speedtestnsus18632.z14.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)speedtestnzn18632.z44.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)speedtestoze18632.z8.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)speedtestozse07105.z26.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)speedtestplc18632.z36.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)speedtestsan18632.z1.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)speedtestscus18632.z21.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)speedtestsea18632.z23.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)speedtestspain53288.z43.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)speedtestuaen18632.z1.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)speedtestuks18632.z33.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)speedtestwe07148.z6.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)speedtestwestcentr18632.z4.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)speedtestwestindia18632.z10.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)speedtestwestus218632.z5.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)speedtestwus318632.z1.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)stci08318.z29.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)stcus09377.z19.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)stea09073.z7.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)stei08516.z30.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)steus09377.z13.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)steus208516.z20.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)stjpe09377.z11.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)stkc09377.z12.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)stukw08516.z35.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)stwus09377.z22.web.core.windows.net/usr/local/bin/node node test/cb-endpoints-test.mjs(dns block)If you need me to access, download, or install something from one of these locations, you can either:
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.