> For the complete documentation index, see [llms.txt](https://docs.volunteers.thousandeyes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.volunteers.thousandeyes.com/help-center/your-whitebox/test-interruption-cross-traffic.md). # Test Interruption (Cross-Traffic) ![A cartoon of a sleeping Whitebox](https://3563921600-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6z2V3g47NJC7MtPOg7A2%2Fuploads%2Fgit-blob-4722103886f52e60b88ccce9613b45dd88476b29%2Fcross-traffic_1.png?alt=media) If your Whitebox has stopped reporting data, there’s a chance it’s because of constant activity on your network. We call this *cross-traffic*. By detecting cross-traffic, we ensure that we don’t disrupt your internet experience to run a test, but wait instead to gather the most accurate results possible. ## What Cross-Traffic Is *Cross-traffic* is the term we give to any network activity that goes to and from the internet, via the router, that’s not generated by one of our tests. A good way of thinking about it is to imagine there’s more than one source of network traffic crossing paths inside your router. ### Impacts to Your Tests The Whitebox and router SDK (software development kit) run tests according to a test schedule: some tests are hourly, some are daily, and others run between a set period of a few minutes. You can read more about test scheduling at [Scheduled Tests](https://docs.thousandeyes.com/product-documentation/connected-devices/test-management/test-triggers/scheduled-tests). ![Chart of scheduled tests over time crossing the cross traffic threshold](https://3563921600-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6z2V3g47NJC7MtPOg7A2%2Fuploads%2Fgit-blob-a7dce0f6995be9f0a000ff38b6c6089d199adf4b%2Fcross-traffic_2.png?alt=media) Before running a performance test, the test agents run a cross-traffic detection test to see how much of your bandwidth is available. When the level of cross-traffic exceeds the cross-traffic threshold, whether before or during a performance test, then the test stops. The test agents will then wait for a small time before trying again. However, if the internet is being used throughout, the “pause and retry” process will occur another five times before the entire test cycle is abandoned until the next scheduled test. For more information about our cross-traffic detection technology, see [Cross-Traffic](https://docs.volunteers.thousandeyes.com/help-center/your-whitebox/test-interruption-cross-traffic). ## Signs of Cross-Traffic Test Interruption Here are some signs that your Whitebox is not reporting data due to cross-traffic: * No new metrics or reports are appearing on your account dashboard. * Large gaps of several hours/days are appearing in your Download Speed chart (when viewed as a scatter plot for closer detail), despite not experiencing network outages. * On your account dashboard, all, or many, of your metrics appear as a flat line (when viewed as line charts) * Your monthly report card shows results that are significantly lower than usual or no results for a period of the month. These issues also apply to our [router agent](https://docs.thousandeyes.com/product-documentation/connected-devices/device-agents/router-agents). If your Whitebox has been disconnected due to changes to your network configuration, a power outage, or any other reason, see [Troubleshooting Your Whitebox](https://docs.volunteers.thousandeyes.com/help-center/troubleshooting/troubleshooting-your-whitebox). ## Minimizing Cross-Traffic Test Interruption If your Whitebox appears to be experiencing cross-traffic there’s nothing to worry about. The Whitebox has been designed to cope with a broad range of lifestyles and uses. However, prolonged usage of operations that demand significant bandwidth can mean your Whitebox is unable to run its scheduled tests. Some of these operations and systems include, but are not limited to: * Network-connected security cameras. * NAS (network attached storage) drives. * Wireless Hi-Fi systems. * Online gaming (playing network-intensive games on the highest settings for long hours). * 4K streaming. * Connecting two or more routers to a single Whitebox. The easiest way to check whether cross traffic is consistently interrupting your performance tests is to generate a download speed scatter plot. If test results are minimal then we recommend turning off another system that constantly uses the internet for a few hours a day. If your Whitebox is operating correctly again, you should be able to see test results populate on your dashboard after 48 hours. If you are still unsure or would like us to investigate, contact us by emailing . --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.volunteers.thousandeyes.com/help-center/your-whitebox/test-interruption-cross-traffic.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.