DNS checks from the Montreal node query authoritative nameservers directly from AS16276 (OVH SAS, Montreal) and return the resolved records with query timing. Because the query goes to the authoritative server rather than a recursive resolver, it bypasses caches and shows the current record at the source. This is the correct method for verifying DNS propagation after a record change — you see what the authoritative server actually has, not what a resolver is still caching from a previous TTL.

Montreal is a particularly useful DNS test location for GeoDNS validation covering the Canadian market. OVH's AS16276 Montreal prefix space is consistently geolocated to Canada by Route 53 GeoDNS, Cloudflare load balancer geo rules, and NS1 filter chains. A DNS test from this node confirms that Canadian-targeted GeoDNS rules return the correct Canadian or North American endpoint. If the Montreal node gets a European IP back from your GeoDNS, the database mapping your OVH Montreal IP to its country is incorrect.

DNS query times from Montreal to anycast authoritative services like Cloudflare NS (1.1.1.1) or AWS Route 53 should be in the 1–5 ms range, as both operate anycast nodes in Montreal and Toronto. Query times above 20 ms from Montreal to a major authoritative provider suggest the authoritative server has no Canadian anycast node and is resolving from a US or European location. This adds latency to every DNS lookup for Canadian users — relevant for high-traffic sites where DNS lookup time is a measurable component of total page load time.

Canada's internet infrastructure is divided along geographic lines. Toronto is the financial and commercial hub, home to TorIX — the country's largest internet exchange by both membership count and peak traffic. Montreal serves as the eastern gateway, with strong connectivity to the US Northeast and transatlantic routes via New York. Vancouver anchors the west coast with direct paths to the US Pacific Northwest and, through undersea cables, to Asia-Pacific. Our probe node sits in Montreal on AS16276 (OVH SAS), hosted in OVH's own datacenter — Montreal is the North American operations base for OVH, one of the world's largest hosting and cloud providers.

OVH (AS16276) is a significant network in its own right. It operates a large global backbone with its own fiber infrastructure and peering agreements at major IXPs including MBIX Montreal, TorIX Toronto, and multiple European exchanges. Traffic from the OVH Montreal node tends to route efficiently toward both US East Coast and European destinations, reflecting OVH's dual transatlantic and North American footprint. The AS16276 prefix space is well-known to major GeoIP databases as a hosting network headquartered in France but with a major Canadian presence.

Reference RTTs from the Montreal node: Montreal to New York is approximately 15 ms over well-peered paths, Montreal to Toronto around 17 ms, Montreal to Boston 10–12 ms, and Montreal to London approximately 85 ms. These figures are consistent with OVH's direct peering at DE-CIX Frankfurt and LINX London, which avoids unnecessary transit hops for transatlantic traffic. Montreal to Los Angeles runs roughly 70–75 ms via central US backbones.

Canada's domestic backbone connects the major cities via long-haul fibre operated by Bell Canada (AS577), Telus (AS852), Rogers (AS812), and Shaw (AS6327). These carriers maintain east-west capacity across thousands of kilometres of geography. Cross-country latency from Montreal to Vancouver is typically 65–75 ms. At the IX level, TorIX in Toronto anchors the national peering ecosystem — most Canadian ISPs maintain a TorIX port even if they also peer regionally at MBIX or VANIX. Equinix Toronto provides carrier-neutral colocation adjacent to the TorIX fabric.

Testing from the Montreal node covers a specific slice of Canadian network conditions: an OVH-hosted server in eastern Canada with strong US Northeast and European connectivity. For services targeting Canadian audiences broadly, the Montreal node is most representative of Quebec and Atlantic Canada users, and of Canadian traffic that routes through US East Coast hubs. Services specifically targeting Ontario or western Canada would benefit from nodes in Toronto or Vancouver for a fuller picture, but Montreal provides a solid baseline for Canada-wide reachability tests.