> ## Documentation Index > Fetch the complete documentation index at: https://support.legora.com/llms.txt > Use this file to discover all available pages before exploring further. # Network connectivity > Run the connectivity check, read each result, and share a report with your IT team. ## Overview This page explains the network connectivity check, what each result means, and how to share the report. The check is a browser page at [connectivity.legora.com](https://connectivity.legora.com). It shows whether your network can reach Legora, then builds a report for your IT team or Legora Support. Anyone can run it in a browser, including when sign-in to Legora is blocked. The check uploads Legora’s own test files. > [!NOTE] > > Run it on the same device, browser, network, and VPN connection where the problem shows up. If your organization restricts outbound traffic, share [Legora network and domain requirements](https://support.legora.com/legora-network-and-domain-requirements.md) with your IT team as well. ## How it works This section covers how to run the check, read the result, and share the report. ### Run the check Keep your device, browser, network, and VPN connection unchanged for the first run: 1. Open [connectivity.legora.com](https://connectivity.legora.com). 2. Select **Check**. 3. Wait until the run finishes. While it runs, the page says **Checking your network**. 4. Expand a section under **Test results**. Before the run, that heading reads **What gets tested**. 5. Select **Download** to save the full report. The page tests global services and four regions: **Europe**, **United States**, **Asia Pacific**, and **Australia**. Read the global results and the region that hosts your organization. Ask your IT team or [Legora Support](mailto:support@legora.com) when you are unsure of the region. ### Read the results The **Test result** row names the overall outcome. Each section under **Test results** has its own outcome. In the downloaded report, read **Needs attention** first. It lists each step and region that needs a closer look, with its destination and explanation. | Result | Where you see it | Meaning and next step | | - | - | - | | **Healthy** | Overall **Test result** and a section | Every step in that scope passed. The overall line reads **Everything seems to have worked**. If the problem continues, share the report. | | **Caution** | Overall **Test result** and a section | Some connections need attention. Expand the section for words such as **Slow**, **Interrupted**, or **Unstable**. | | **Failed** | Overall **Test result** | A check could not connect or finish. Follow an incident link when one is shown, then review the report with your IT team. | | **Blocked** | A section | That section could not connect or finish. Review the report with your IT team. | | **Inconclusive** | Overall **Test result** | The page could not complete the observation. If checks were paused after too many runs, wait a minute and select **Check** again. | | **Unavailable** | A section | That section’s result is unclear. Use the same wait-and-retry step when a rate limit is the cause. | | **Not tested** | Overall **Test result** or a section | That part has not run. Select **Check**. | | **Unknown** | An expanded step | The page could not confirm an answer from Legora. The report names what it observed. | **Healthy** means every step in that scope passed. **Unavailable**, **Inconclusive**, **Unknown**, and **Not tested** mean the page is still missing a confirmed pass for that part. **Healthy** covers the connections in that run. Account access, sign-in settings, add-in installation, and upload speed need their own checks. When Legora is reporting an incident, **Test result** links to [status.legora.com](https://status.legora.com). ### Understand the checks The page groups its checks into seven sections: * **Browser:** Connections that load Legora, sign in, and reach services such as the Legora API and search. * **Files:** The upload host, **Test file transfer** for a plain PDF, and **Protected file transfer** for an encrypted PDF. * **WebSockets:** **Live connection**, **Two-way message**, and **Idle connection**. * **Live collaboration:** Connections for document editing and Tabular Review, including **Tabular Review backup server**. * **Word Add-in:** **Add-in sign-in**, **Add-in app**, and **Add-in API**. * **Outlook Add-in:** **Add-in sign-in** and **Add-in app**. * **Excel Add-in:** **Add-in sign-in** and **Add-in app**. **Global login**, **Global identity service**, and **Session refresh** check Legora’s global authentication. **Sign-in** checks the legacy authentication host, and **Sign-in (regional)** checks the regional sign-in host. **Single sign-on** checks the single sign-on host. **Add-in sign-in** uses the global add-in host for Legora’s global authentication. **Add-in app** uses the regional host. Word also checks the regional **Add-in API**. ### Share the report Share the full report so your IT team or Legora Support can see the destinations and results: * **Copy:** Copies the full report. * **Download:** Saves an English text file. The name starts with `legora-connectivity-test-` and includes the test date. * **Email:** Opens a draft that contains a summary. Attach the downloaded file, or paste the copied report, before you send it. The draft includes a **Firm** line and a **What is not working** line. **Actions required** appears when the result is **Caution** or **Failed** and the page attributes the result to your network. **Step 1** reads **Copy or download the technical details**. **Step 2** reads **Share the details with someone from your firm’s IT department**. The last row reads **Email the details to Legora support** and shows **Email**. When the result is **Healthy**, **Copy** and **Download** appear under **If you’re still experiencing problems**, beside **Share these details with Legora support**. The report includes browser details, the test time, destinations, regional results, and short explanations. When you report a problem, include your organization, the action that failed, and whether you used a VPN. The check leaves cookies, local storage, and session storage empty. Legora discards the test files. After a completed live check, Legora receives the check outcomes, the regions tested, the technical reasons, and a browser type such as Chrome or Edge. When the page pauses checks because this address ran them too often, it skips that message. The report you choose to share includes the fuller browser details above. ## Troubleshooting Use the matching item below, then run the check again after your IT team changes the network. ### What if a file upload fails? Share the report with your IT team and ask them to review the upload destination and any limits on file transfers. If **Test file transfer** completes and **Protected file transfer** is **Blocked**, a security tool may be stopping a file it cannot scan. The report then says “A plain PDF reached Legora. An encrypted PDF of the same size did not.” ### What if Live collaboration shows Caution? Expand **Live collaboration** to see whether document editing or Tabular Review is affected. Tabular Review can keep working through **Tabular Review backup server** when a primary host is **Blocked**. A blocked document-editing step marks the section **Blocked**. Document editing uses that host alone. Ask your IT team to review [Legora network and domain requirements](https://support.legora.com/legora-network-and-domain-requirements.md), including the collaboration backup domains. A **Healthy** result covers the connections this check ran. ### What if a firewall, proxy, or VPN affects the result? Ask your IT team to review the affected domains and the explanations in the report. Keep the first report so you can compare it with a later run. Change the network or VPN with your IT team. ### What if the problem continues on a Healthy result? Select **Copy** or **Download** under **If you’re still experiencing problems**. Email the full report to [Legora Support](mailto:support@legora.com) with the affected action, the time, and the browser.