Cannot access GTAM on Android

Close. If you can open the terminal again and run the following:

tracert www.gtamotorcycle.com

And copy/paste the results here that’d be great

Microsoft Windows [Version 10.0.26100.4351]
(c) Microsoft Corporation. All rights reserved.

C:\Users\johns>tracert www.gtamotorcycle.com

Tracing route to gtamotorcycle.com [51.161.11.223]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.1
2 15 ms 12 ms 14 ms pool-99-232-128-1.cpe.net.cable.rogers.com [99.232.128.1]
3 17 ms 16 ms 17 ms lan-lt.wbb.net.cable.rogers.com [24.156.143.253]
4 14 ms 12 ms 14 ms 69.63.249.58
5 22 ms 15 ms 19 ms 209.148.235.222
6 19 ms 18 ms 17 ms ovh.ip4.torontointernetxchange.net [206.108.34.189]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 30 ms 23 ms 22 ms be105.bhs-g2-nc5.qc.ca [192.99.146.48]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
 
Microsoft Windows [Version 10.0.26100.4351]
(c) Microsoft Corporation. All rights reserved.

C:\Users\johns>tracert www.gtamotorcycle.com

Tracing route to gtamotorcycle.com [51.161.11.223]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.1
2 15 ms 12 ms 14 ms pool-99-232-128-1.cpe.net.cable.rogers.com [99.232.128.1]
3 17 ms 16 ms 17 ms lan-lt.wbb.net.cable.rogers.com [24.156.143.253]
4 14 ms 12 ms 14 ms 69.63.249.58
5 22 ms 15 ms 19 ms 209.148.235.222
6 19 ms 18 ms 17 ms ovh.ip4.torontointernetxchange.net [206.108.34.189]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 30 ms 23 ms 22 ms be105.bhs-g2-nc5.qc.ca [192.99.146.48]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
Well that's not good.
 
For anyone having issues accessing the website, please email me your IP address and your user name.

cutekill@gtamotorcycle.com
 
As I mentioned in one of the other threads, I was unable to access the site for around 3 weeks, from either my home laptop on either wifi or hardwired or from my phone using home wifi, work wifi, starbucks wifi or just data., This started in late May until mid June. As suddenly as it started it stopped. I did not receive any 403/404 errors, just the same sort of screen as Jayell.

Obviously since I couldnt access the site I was unable to report an issue at that time. I suspect there may be more users that had an issue (or still do) that havent or cant report it. I wouldnt have if I hadnt noticed these threads when I got back on.
 
Last edited:
Microsoft Windows [Version 10.0.26100.4351]
(c) Microsoft Corporation. All rights reserved.

C:\Users\johns>tracert www.gtamotorcycle.com

Tracing route to gtamotorcycle.com [51.161.11.223]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.1
2 15 ms 12 ms 14 ms pool-99-232-128-1.cpe.net.cable.rogers.com [99.232.128.1]
3 17 ms 16 ms 17 ms lan-lt.wbb.net.cable.rogers.com [24.156.143.253]
4 14 ms 12 ms 14 ms 69.63.249.58
5 22 ms 15 ms 19 ms 209.148.235.222
6 19 ms 18 ms 17 ms ovh.ip4.torontointernetxchange.net [206.108.34.189]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 30 ms 23 ms 22 ms be105.bhs-g2-nc5.qc.ca [192.99.146.48]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

I just ran my own traceroute (was successful) and the bexxx.bhs-g2-nc5.qc.ca is the last hop before GTAM/Canspace hosting. Most likely Canspace's datacenter provider: OVH Hosting.

I think there's some IP filtering that's happening at either the router or on the host itself at OVH or Canspace. I don't think this is at the application layer, but lower.

@cutekill may have to inquire at the ISP to see if there's IP blocking done at that level.
 
Microsoft Windows [Version 10.0.26100.4351]
(c) Microsoft Corporation. All rights reserved.

C:\Users\johns>tracert www.gtamotorcycle.com

Tracing route to gtamotorcycle.com [51.161.11.223]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.1
2 15 ms 12 ms 14 ms pool-99-232-128-1.cpe.net.cable.rogers.com [99.232.128.1]
3 17 ms 16 ms 17 ms lan-lt.wbb.net.cable.rogers.com [24.156.143.253]
4 14 ms 12 ms 14 ms 69.63.249.58
5 22 ms 15 ms 19 ms 209.148.235.222
6 19 ms 18 ms 17 ms ovh.ip4.torontointernetxchange.net [206.108.34.189]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 30 ms 23 ms 22 ms be105.bhs-g2-nc5.qc.ca [192.99.146.48]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
I'm on Rogers and have a very similar tracert result with the 3 timeouts and then a response from the bhs-g2-nc5.qc.ca domain. I agree that something is probably happening on the network layer, not the GTAM server itself.
 
Last edited:
I'm on Rogers and have a very similar tracert result with the 3 timeouts and then a response from the bhs-g2-nc5.qc.ca domain.

Network Trivia:

Timeouts then a successful response from a subsequent host just mean those intermediate routers have filtered out ICMP and won't respond to ping or traceroute requests.

They're configured that way to protect against ICMP flood attacks.

It's when you get timeouts and then an unsuccessful traceroute that further investigation is typically warranted.

ObDisclosure: Used to be a network admin for an ISP in the late 1900s... 😬
 
GTAM seems to be working now. The only change on my side is that my router notified me that it rebooted after performing an update yesterday morning at 3AM, but I still have the same IP address.
 
I just ran my own traceroute (was successful) and the bexxx.bhs-g2-nc5.qc.ca is the last hop before GTAM/Canspace hosting. Most likely Canspace's datacenter provider: OVH Hosting.

I think there's some IP filtering that's happening at either the router or on the host itself at OVH or Canspace. I don't think this is at the application layer, but lower.

@cutekill may have to inquire at the ISP to see if there's IP blocking done at that level.
I'm trying to follow up with those that have sent me their IPs via email, as requested
 
Back
Top Bottom