No access from AU?

[s77656769]

Anyone else seeing this problem? Traceroute shows a path via AAPT.

 

Was working fine yesterday, and had a productive session "ignoring" threads that were old or uninteresting, then it just stopped dead.  Guessed a server problem and thought I'd try again later. Now is tomorrow is later, and I had to resort to VPN for connectivity.

 

Both my home adsl and mobile connections won't connect to PA, get timeout messages.

 

ADSL traceroute -I times out to 64.59.76.194, as does telnet to port 80.  However telnet port 80 to 64.59.76.193 connects so it doesn't look like a subnet based network block.

 

Could I have hit some usage limiter for my IP address?

 

Seems strange that my mobile access would be blocked too then?

 

And my account obviously works over VPN?

 

Ideas anyone?

[Deuces]

AAPT are filtering the internet for our governments petty whims now. Is this the reason? no idea but it could be.

[s77656769]

AAPT are filtering the internet for our governments petty whims now. Is this the reason? no idea but it could be.

 

I was under the impression that all the major players were involved, so I'd expect a more general issue if they are all playing from the same playlist.  Wouldn't expect PA would be on the ASIC hit list, however it could be part of their redfaced collateral damage.  Don't know if PA are sharing their IP address, or if it is dedicated.  Reverselook up is hotwifediaries.com, so looks like it is shared, or could be an artifact of age.

[biggles]

\i am using from the sunshine coast in queensland and dont have any problem logging in or viewing.

[s77656769]

Thanks for the feedback, not a general problem then, just maybe specific to me?

 

Did some further testing with my phone and made sure was nt using WiFi to my ADSL, and thru the mobile network, it works, so maybe my IP address is blocked some how?

 

Doing some tcp traceroutes on port 80, something seems dodgy:

 

 

# traceroute -T -p 80  64.59.76.194  # ie PA
traceroute to 64.59.76.194 (64.59.76.194), 30 hops max, 60 byte packets
...
 5  203-174-185-153.syd.static-ipl.aapt.com.au (203.174.185.153)  38.497 ms  38.507 ms  38.997 ms
 6  * * *
 7  xe-7-0-0-420.sgbr2.global-gateway.net.nz (202.50.233.5)  37.810 ms  36.424 ms  36.488 ms
 8  * * *
 9  * * *
10  * * *
11  205.158.79.141.ptr.us.xo.net (205.158.79.141)  198.935 ms  197.903 ms  196.542 ms
12  te1-0-0d0.cir1.la3-ca.us.xo.net (207.88.15.29)  197.337 ms  198.314 ms  197.203 ms
13  207.88.14.217.ptr.us.xo.net (207.88.14.217)  288.134 ms  287.836 ms  288.002 ms
14  vb15.rar3.dallas-tx.us.xo.net (207.88.12.45)  284.564 ms  287.507 ms  287.535 ms
15  207.88.14.158.ptr.us.xo.net (207.88.14.158)  295.418 ms  277.986 ms  289.815 ms
16  ip67-94-116-14.z116-94-67.customer.algx.net (67.94.116.14)  285.105 ms  285.074 ms  291.703 ms
17  * * *

 

while testing an adjacent address, .193 works, so looks like block is specific to PA and my IP.

 

Anyone know how to get some technical comment from PA Admins?