We signed up for KnownHost VPS services about a month ago, and ever since we signed up, our PayPal IPNs was just not working. This is crucial to our business, since we sell instant downloadable PDF sheet music, which is not so instant if IPNs donīt work ( We all need to sleep once in a while too, right? )This ment that our orders did not go from "pending" to "completed", allowing the customer to download their products. We had to udate orders manually. And we didnīt receive a single email from PayPal after any sale whatsoever. So after a week, we got pretty frustrated, and kept asking KnownHost if they could fix this issue - we also sent numerous emails to PayPal asking them about the error. On top of that, we hired two developers to see what they could do about it. A very long story short : AT&T had blocked our main IP, and this was the reason for the IPN not working - in the end it was PayPal who figured it out, but they couldnīt have done it without the service of either KnownHost and our developers - it was really a collaboration, and everybody was pulling their load to get this worked out. We were extremely close to just give up, and sign up for another host, but then again, we didnīt fully understand the issue, so who was to say that the problem wouldnīt follow us to a new host? Thanks to KnownHost for not giving up - especially thanks to Paul from KnownHost - Highly appreciated help!
Well, if you are planning to move, you need to make sure the ip is clean before moving everything.
But I can see it is resolved already? or Am I missing something?
Everything is resolved - took us three weeks to figure out what the problem was. Are you saying that this is a normal thing to check the IP before signing up? I dont think the "normal" user is aware of this. It sure didnīt strike even PayPal or Knownhost, or the 2 developers I hired to check the IP at first.
This is not the intention of the provider to give you a bad ip but it does happen when this particular ip was used for spam by their old client before.
This really doesn't have much to do at all with a bad IP, as that IP can access everything else on AT&T's network. It is specifically blocked when dealing with traffic from that IP or from PayPal's IP when passing across an AT&T Circuit.
Pretty much a place they should never be blocking IP addresses from in the first place.
To illustrate it in terms of a traceroute coming from the customers services it would look similar to this.
This appears to be almost as if someone @ AT&T has configured their transit routers to use an incorrect block list. It would be perfectly acceptable if the traffic was blocked @ 8 or 9, or even @ 1 or 2. This is where traffic is normally blocked at.
But for AT&T to randomly block transit traffic, travelling from one network to another network is not normal, and leaves all parties in a disadvantageous spot.
Ontop of which it only seems certain routes within the AT&T network are blocked. While that IP cannot access Paypal IPN's when transitioning through the AT&T network, it can access other test sites within the AT&T network.
The end of the day it is resolved for the customer but apparently AT&T and Sprint have become notorious for randomly blocking IP's in mid transit when dealing with PayPal IPN's (if you search their forums you'll find the reports).