Once you receive this output, please send to our support team – also, we encourage to contact your ISP as well if you are noticing difficulty connecting to or any other Atlassian products.Use the IP address and go to (NTT is our network provider):.Check our status page to ensure we haven't reported any outages/issues:.Check latency between major internet backbones (AT&T, Cogent, NTT, Sprint, Verizon, Level3, etc.) –.You should see ~ 10-100ms responses depending on where you are located geographically. You can sometimes test this by running a ping or traceroute to. If you're in an office with an issue, contact your local network administrator to be sure that they aren't blocking/slowing connections. This will rule out any intermediate networking equipment.

Connect your computer directly to your internet connection, if possible.For wireless networks, try cloning when very near to your access point.Sometimes a simple cable issue can cause significant slowness or a flaky network connection. Check all wired and wireless interfaces physically.Try using Google DNS if you're having issues trying to resolve the site: Check all network and configuration settings between the two machines if you see slowness in only a single machine.Once you've narrowed down the issue to a specific machine or machines, double check the following No? Go on to check the other common causes.Yes? Then, likely the slowness you are experiencing on the original machine is caused by your network. Check the common causes below to further narrow down the issue.Is the speed significantly faster on this network?.No? Go on to check if your network is the problem.įor example, if your office has the issue, check your home connection or even your cell using tethering.Yes? Then, likely the slowness you are experiencing is a result of your computer or its environment. Check the common causes below to further narrow down the issue.Is the speed significantly faster on the other machine.

Go to another computer on your network.

Is it your computer, the environment on your computer, or the network the computer is on. Try to find out the source of the slower connection. If you aren't seeing 200 KiB/s or faster, continue troubleshooting. Let this serve as your benchmark to target. Any number equal to or larger than 200 KiB/s is a good result. The speed in this test was 1.21 MiB/s which is very fast.

Microsoft remote desktop for mac mtu