Possible Causes
InfiniCLOUD is an internet-based service, therefore it must connect to a variety of networks in order to reach your local environment. As a result, determining the actual cause of low performance might be challenging. Please see the list below if you are having performance issues.
- Check load time speed for other sites.
- If websites other than InfiniCLOUD are also slow to load or respond, there may be an issue with your internet connection.
- Are load time speeds slower than usual for sites other than InfiniCLOUD
- Are connectivity issues occurring?
- If only connections to InfiniCLOUD are slow.
- High congestion on InfiniCLOUD. Further information will be available on InfiniCLOUD's website if congestion lasts for an extended period of time.
- Excessive device use or stress. Check device's resource usage for signs of a problem.
- A routing issue between your Internet Service Provider (ISP) and InfiniCLOUD.
- Immediate action is required from both your ISP and InfiniCLOUD to resolve this issue.
- Immediate action is required from both your ISP and InfiniCLOUD to resolve this issue.
It is possible to enhance speeds by establishing a direct connection between your ISP and InfiniCLOUD.
Without the complete participation of the user's ISP, any issues affecting the user's ISP cannot be resolved by the user or InfiniCLOUD.
* See also: What is the maximum speed?
Trace your route to InfiniCLOUD
The following information can help InfiniCLOUD better understand issues with poor connections. InfiniCLOUD usage patterns in general typically entail transfers from the user's end to InfiniCLOUD. As a result, for an appropriate portrayal, input from the user is required.
The Traceroute command (Tracert in Windows) shows the network route to a remote host, allowing for real-time analysis of intermediate routers along the path. While the reaction times for each router are not directly related to bandwidth (upload and download speeds), they can be utilized to perform a quick assessment of network capabilities.
How to use Traceroute
On Windows systems:
In this example, we run Tracert to yura.teracloud.jp. Adding the -d option performs the trace without DNS resolution.
C:\>tracert -d yura.teracloud.jp Tracing route to yura.teracloud.jp [103.49.141.114] over a maximum of 30 hops: 1 5 ms 6 ms 6 ms **.**.255.254 2 7 ms 6 ms 7 ms **.**.158.190 3 6 ms 6 ms 10 ms **.**.77.125 4 6 ms 6 ms 6 ms **.**.77.225 5 9 ms 9 ms 9 ms **.**.109.25 6 8 ms 9 ms 9 ms **.**.224.72 7 10 ms 10 ms 10 ms **.**.140.193 8 13 ms 12 ms 12 ms **.**.140.18 9 13 ms 12 ms 12 ms 103.49.141.114 Trace complete.
On Unix-like systems:
Here we run Traceroute to yura.teracloud.jp. The -I option specifies that Internet Control Message Protocol (ICMP) will be used, and -n conducts the trace without Domain Name System (DNS) resolution.
$ traceroute -I -n yura.teracloud.jp 1 **.**.255.254 5.924 ms 5.743 ms 5.838 ms 2 **.**.158.190 7.037 ms 6.303 ms 6.442 ms 3 **.**.77.125 5.839 ms 5.843 ms 11.042 ms 4 **.**.77.225 5.763 ms 5.844 ms 5.846 ms 5 **.**.109.25 9.302 ms 8.768 ms 8.577 ms 6 **.**.224.72 9.345 ms 8.704 ms 8.705 ms 7 **.**.140.193 9.311 ms 9.378 ms 9.302 ms 8 **.**.140.18 12.211 ms 12.236 ms 12.826 ms 9 103.49.141.114 12.692 ms 12.836 ms 12.279 ms
The values shown in milliseconds (ms) are each router's response time, representing the time taken to travel to the given router and back.
If response time increases greatly at a particular point, it is likely that an issue with the internet route is causing performance problems.
Share your Traceroute results with us
InfiniCLOUD is constantly looking to improve and enhance each users experience. Please fill out the following form to submit your Traceroute results and assist InfiniCLOUD in creating new blueprints for future network and service enhancements.
Submission Form
Please run the Traceroute or Tracert command against the InfiniCLOUD server containing your data area (xxx.teracloud.jp) and send us the results.