Can't connect to TradeMe...from Sydney?

Forums › New Zealand Broadband › Can't connect to TradeMe...from Sydney?

kenkeniff

620 posts

Ultimate Geek

#138857 19-Jan-2014 18:02

In Chrome I get: "This webpage is not available" / Error code: ERR_CONNECTION_RESET
Firefox: "The connection was reset"

Seems I don't actually receive any headers back.

Problem has only started over the xmas holidays as have been able to access from this IP before.

I emailed TradeMe to see if they had started blocking my IP range recently however I didn't get back a definite answer.

---------------------------------------------------------------------------------------------------------------------------------------------------------
Microsoft Windows [Version 6.2.9200] (c) 2012 Microsoft Corporation. All rights reserved.

C:\Users\K>ping trademe.co.nz

Pinging trademe.co.nz [202.162.72.2] with 32 bytes of data:
Reply from 202.162.72.2: bytes=32 time=38ms TTL=244
Reply from 202.162.72.2: bytes=32 time=38ms TTL=244
Reply from 202.162.72.2: bytes=32 time=37ms TTL=246
Reply from 202.162.72.2: bytes=32 time=37ms TTL=246

Ping statistics for 202.162.72.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds:
Minimum = 37ms, Maximum = 38ms, Average = 37ms

C:\Users\K>tracert trademe.co.nz

Tracing route to trademe.co.nz [202.162.73.2] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms ecX-XXX-XXX-X-XX.ap-southeast-2.compute.amazonaws.com [54.252.X.XX]
2 2 ms 2 ms 2 ms 54.252.XXX.XXX
3 2 ms 2 ms 2 ms 54.240.192.108
4 2 ms 2 ms 2 ms 54.240.192.72
5 2 ms 2 ms 2 ms 202.50.232.93
6 2 ms 2 ms 2 ms ae0-10.sebr1.global-gateway.net.nz [202.50.232.241]
7 2 ms 2 ms 2 ms ae1-10.sgbr1.global-gateway.net.nz [203.96.120.201]
8 26 ms 26 ms 26 ms xe3-0-0.akbr4.global-gateway.net.nz [202.50.232.9]
9 26 ms 26 ms 26 ms ae1-2.akbr6.global-gateway.net.nz [210.55.202.214]
10 27 ms 27 ms 28 ms trademe-int.akbr5.global-gateway.net.nz [202.50.233.114]
11 27 ms 27 ms 27 ms 203.57.145.135
12 27 ms 27 ms 27 ms www.trademe.co.nz [202.162.73.2]

Trace complete.
---------------------------------------------------------------------------------------------------------------------------------------------------------

Any ideas?

kenkeniff

620 posts

Ultimate Geek

#969740 19-Jan-2014 20:36

I've also tried accessing 202.162.73.2 directly but get the same error.

Any ideas on how I can trace / diagnose this issue as TradeMe won't see to confirm nor deny they're blocking any AWS traffic?

quandum

204 posts

Master Geek

#969780 19-Jan-2014 23:24

Did you try another browser / device?

I would love to change the world, but they won't give me the source code

#BOFH

freitasm

BDFL - Memuneh
67053 posts

Uber Geek

Administrator

Trusted

Geekzone

Lifetime subscriber

#969782 19-Jan-2014 23:40

I am using a VPN ending in Sydney and it connects fine to Trade Me.

I see your IP address when posting this topic was not in Australia. I used the same VPN to connect via this other country and still loaded the Trade Me page just fine.

Perhaps an ISP problem?

johnr

19282 posts

Uber Geek
Inactive user

#969783 19-Jan-2014 23:43

Why would not contact your ISP first?

kenkeniff

620 posts

Ultimate Geek

#969821 20-Jan-2014 08:10

quandum: Did you try another browser / device?

Same issue in Chrome and Firefox.

freitasm: I am using a VPN ending in Sydney and it connects fine to Trade Me.

I see your IP address when posting this topic was not in Australia. I used the same VPN to connect via this other country and still loaded the Trade Me page just fine.

Perhaps an ISP problem?

Depends what GeoIP service you're using;
http://ip-lookup.net/ says I'm in Australia
http://www.hostip.info/ says United States

The VM I'm remote desktop'ed into is definitely in Sydney though.

johnr: Why would not contact your ISP first?

Just thought there might be a way to further diagnose the problem and narrow down or rule out whether it is a client, ISP or TradeMe issue.

I can access all of TradeMe's other sites just fine (tmsandbox.co.nz, stuff.co.nz, oldfriends.co.nz etc)

I wouldn't be surprised if they were blocking an IP range I'm on as I frequently get errors / captchas from websites for "Suspicious browsing behaviour / You appear to be a robot" due to being on AWS (obviously a lot of bots hosted on the same network getting blacklisted).