Skip to main content

Test browser connectivity to Databricks domains

The network diagnostic checks whether your browser can reach the domains that Databricks requires and measures connection performance. If the Databricks UI fails to load, notebooks hang, or assets appear broken, the diagnostic can help you identify DNS, firewall, or proxy issues.

These checks test domain reachability, not authenticated access to Databricks. Even if all domains are reachable, inbound network policies such as context-based ingress and IP access lists can still block requests to your workspace.

important

All checks run locally in your browser, and Databricks doesn't receive the results. The checks send read-only requests to public endpoints and don't require authentication or access your data. The WebSocket check connects to a public third-party echo server, echo.websocket.org, and sends it a test message. That server receives your IP address, browser user agent, and this page’s origin as connection metadata.

Step 1: Run the diagnostic​

Enter your workspace URL, then click Run diagnostic. The workspace URL is optional but recommended. With it, the diagnostic checks your workspace domains in addition to the shared Databricks domains. Paste the full address from your browser's address bar while the workspace is open.

Optional. Without a workspace URL, this checks content delivery domains and a public WebSocket echo server. Enter your workspace URL to also check connectivity to its domains.

Step 2: Review the results​

When the diagnostic finishes, review the results. If every required check passes, domain-level network blocking is unlikely. A failed request can result from browser policy or a network issue, such as a proxy, firewall, or DNS resolver.

Step 3: Share the report​

Copy the report that the diagnostic generates and share it with your network administrator or Databricks support. The report contains only the diagnostic results, your browser version, and the hostnames checked.

Additional resources​