Connection Reset Errors

Some of our users are continually receiving Connection Reset errors. The cause of the error can be two-fold: 

1. Your network  connection is experiencing problems. This is very common. It can be caused by your Internet Service Provider, your computer, or any routing server between your computer and our server. 

2. Our server is experiencing problems. Although we have made major upgrades to our server in November and are continually monitoring for errors, there will be times that our server becomes unavailable. We attempt to keep our true down time as minimal as possible and are striving to reach a minimal 1% downtime.  We appreciate your patience in this matter.

How to tell if you have network connection problems? Trace Route Test
A Trace Route test will determine where you are experiencing problems in connecting to our server. Here is a few samples results:
The * symbols are equivalent to a network error.

Example 1: Typical slow connection result
C:\WINDOWS>tracert www.intermatwrestle.co
Tracing route to www.intermatwrestle.com [216.122.98.250]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms APTIVA3 [192.168.0.1]
2 128 ms 134 ms 120 ms ins024.netins.net [167.142.225.74]
3 139 ms 120 ms 134 ms ins-core1.desm.netins.net [167.142.225.253]
4 212 ms 133 ms 140 ms 901.Hssi4-0.GW1.MSP1.ALTER.NET [157.130.96.145]
5 266 ms 191 ms 166 ms 151.ATM2-0.XR1.CHI4.ALTER.NET [146.188.209.114]
6 184 ms 153 ms 159 ms 195.ATM1-0.TR1.CHI4.ALTER.NET [146.188.208.210]
7 * * * Request timed out.
8 245 ms 229 ms 223 ms 199.ATM6-0.XR1.SEA1.ALTER.NET [146.188.200.97]
9 202 ms 236 ms 230 ms 195.ATM8-0-0.GW2.SEA1.ALTER.NET [146.188.200.49]
10 265 ms 255 ms 242 ms lightrealm-gw.customer.ALTER.NET [157.130.176.50
11 212 ms 268 ms 263 ms www.intermatwrestle.com [216.122.98.250]
Trace complete.

Notice the "* * * Request Timed out." line. This is an example of a connection problem, to a server router at line 7(Line 7 is NOT the InterMat server). The above example will result in  a slow connection or a connection reset to the InterMat website. This is NOT an InterMat Server error.

EXAMPLE  2: Connection Reset Error / BAD CONNECTION
Tracing route to www.intermatwrestle.com [216.122.98.250]
over a maximum of 30 hops:
1 1 ms <10 ms 1 ms APTIVA3 [192.168.0.1]
2 * 3269 ms * ins025.netins.net [167.142.225.75]
3 * * 3303 ms ins-core1.desm.netins.net [167.142.225.253]
4 * 3060 ms 3258 ms 901.Hssi4-0.GW1.MSP1.ALTER.NET [157.130.96.145]
5 * 3430 ms * 151.ATM1-0.XR1.CHI4.ALTER.NET [146.188.209.106]
6 * 3330 ms * 295.ATM2-0.TR1.CHI4.ALTER.NET [146.188.208.218]
7 * * * Request timed out.
8 3410 ms * 3377 ms 299.ATM6-0.XR1.SEA1.ALTER.NET [146.188.200.105]
9 * * 3428 ms 195.ATM8-0-0.GW2.SEA1.ALTER.NET [146.188.200.49]
10 * 3407 ms * lightrealm-gw.customer.ALTER.NET [157.130.176.50
11 * * 3498 ms www.intermatwrestle.com [216.122.98.250]
Trace complete.

This example will probably result in a "Connection Reset" error. This is NOT an InterMat server problem. Note the connection times in ms (ms=milliseconds) are extremely high compared to Example 1. Also note the large number of astericks (*). The astericks denote that no information was returned.

Example 3: Good Trace route
Tracing route to www.intermatwrestle.com [216.122.98.250]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms APTIVA3 [192.168.0.1]
2 157 ms 163 ms 182 ms ins025.netins.net [167.142.225.75]
3 148 ms 145 ms 144 ms ins-core1.desm.netins.net [167.142.225.253]
4 253 ms 173 ms 155 ms 901.Hssi4-0.GW1.MSP1.ALTER.NET [157.130.96.145]
5 179 ms 174 ms 164 ms 151.ATM1-0.XR1.CHI4.ALTER.NET [146.188.209.106]
6 253 ms 164 ms 164 ms 295.ATM2-0.TR1.CHI4.ALTER.NET [146.188.208.218]
7 233 ms 241 ms 242 ms 106.ATM7-0.TR1.SEA1.ALTER.NET [146.188.136.166]
8 245 ms 232 ms 241 ms 299.ATM6-0.XR1.SEA1.ALTER.NET [146.188.200.105]
9 252 ms 242 ms 241 ms 195.ATM8-0-0.GW2.SEA1.ALTER.NET [146.188.200.49]
10 235 ms 242 ms 231 ms lightrealm-gw.customer.ALTER.NET [157.130.176.50
11 253 ms 241 ms 232 ms www.intermatwrestle.com [216.122.98.250]
Trace complete.

Note the low ms times and no astericks(*). This is a good connection to our server.

Example 4: InterMat server down
Tracing route to www.intermatwrestle.com [216.122.98.250]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms APTIVA3 [192.168.0.1]
2 157 ms 163 ms 182 ms ins025.netins.net [167.142.225.75]
3 148 ms 145 ms 144 ms ins-core1.desm.netins.net [167.142.225.253]
4 253 ms 173 ms 155 ms 901.Hssi4-0.GW1.MSP1.ALTER.NET [157.130.96.145]
5 179 ms 174 ms 164 ms 151.ATM1-0.XR1.CHI4.ALTER.NET [146.188.209.106]
6 253 ms 164 ms 164 ms 295.ATM2-0.TR1.CHI4.ALTER.NET [146.188.208.218]
7 233 ms 241 ms 242 ms 106.ATM7-0.TR1.SEA1.ALTER.NET [146.188.136.166]
8 245 ms 232 ms 241 ms 299.ATM6-0.XR1.SEA1.ALTER.NET [146.188.200.105]
9 252 ms 242 ms 241 ms 195.ATM8-0-0.GW2.SEA1.ALTER.NET [146.188.200.49]
10 235 ms 242 ms 231 ms lightrealm-gw.customer.ALTER.NET [157.130.176.50
11 * * * Request timed out. www.intermatwrestle.com [216.122.98.250]
Trace complete.

Note: This is a result of our server being down. 

Click here to learn how to do a Trace Route Test