Check-Host.cc

UDP Test from Canada

1 node in Montreal · TorIX Toronto

Canada — 1 Node

Cities
Montreal
ISPs / ASNs
OVH SAS AS16276
Datacenters
OVH SAS
Internet Exchanges
TorIX Toronto — Canada's largest IX by membership and traffic, based in Toronto
MBIX Montreal — Montreal-based IX serving Quebec and Eastern Canada networks
VANIX Vancouver — Vancouver IX, primary peering point for western Canada
Equinix Toronto — Carrier-neutral colocation and peering in the Toronto metro area

UDP Testing from Canada

UDP checks from the Montreal node send a probe to the target port from AS16276 (OVH SAS) and report whether a response was received. UDP probes are useful for testing DNS resolvers, NTP endpoints, game servers, SIP/VoIP gateways, and VPN endpoints such as WireGuard (51820) or OpenVPN UDP mode. No response is not conclusive proof that the service is down — many protocols discard probes that lack valid session framing and will not reply to a generic UDP packet.

OVH's Montreal network has clean UDP egress toward US East Coast and European destinations. UDP-based services that primarily serve North American and European users can be validated effectively from this node. Montreal to New York UDP paths typically show latency comparable to the ICMP RTT — around 15 ms — which is a useful baseline for confirming that no stateful firewall is inserting additional delay on UDP flows compared to the ping path.

For VPN operators targeting Canadian or US East Coast users, a UDP probe from Montreal confirms that the VPN endpoint port is reachable from a Montreal hosting network before deploying to production. Combine this with TCP checks on the management port and HTTP checks on any control-plane web interface to get a complete reachability picture from the Canadian vantage point.

Canada Network Infrastructure

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.