Thought I’d post this for all as a heads up.
SurferTim posted solutions in the past for those running hotspots and having problems with paypal and changing IP’s, and problems with DNS cacheing.
Don’t know if changes will be needed again.
PayPal MTS Bulletin
PayPal continues to make significant investments and improvements to its infrastructure to improve our performance, scalability and availability to our customers. These improvements sometimes require us to perform necessary site maintenance upgrades. These upgrades sometimes require merchants to make changes to or update their existing integration.
Please make sure you are ready for this event by consulting with your technology team or individual(s) responsible for your PayPal integration.
What’s happening?
Because of a system upgrade, the following API endpoints are being updated:
api.paypal.com
api-3t.paypal.com
svcs.paypal.com
When is this happening?
This event is scheduled for the following date(s) and time(s):
Date: March 25th 2014
Time: 11:00 PM PT
Why is this happening?
We are performing this upgrade to ensure more efficient service for PayPal API users.
What do I need to do?
Merchants integrated in the following non-standard ways with PayPal’s API calls will be impacted when we update the API endpoints:
Merchants calling our APIs with a hardcoded PayPal API endpoint IP address rather than using DNS resolution. See section A below.
Merchants using HTTP methods other than GET, POST, DELETE and PUT. See section B below.
Merchants using the HTTP 1.0 protocol. See section C below.
Merchants whose firewall is configured to allow incoming and/or outgoing traffic from only a specific set of IP addresses will need to reconfigure their integration. See section D below.
Action items
Your technical team or individual(s) responsible for your PayPal integration will need to examine your current integration and make necessary changes.
Below are merchant action items for each of the impacts listed above:
A. Merchants calling our APIs with a hardcoded PayPal API endpoint IP address rather than using DNS resolution
Impact to your business: API calls will timeout or the merchant will encounter an internal error from their system
Your call to action: Use DNS resolution to access our API endpoints and/or open your firewall to the new IP addresses which will be communicated
B. Merchants using HTTP methods other than GET, POST, DELETE and PUT:
Impact to your business: API calls will return HTTP/1.0 400 Bad Request or HTTP Error 405 Method not allowed
Your call to action: Send the API requests using one of the allowed methods. Heartbeat calls using the HEAD method will not be allowed
C. Merchants using the HTTP 1.0 protocol:
Impact to your business: API calls will return HTTP/1.0 400 Bad Request
Your call to action: Merchants should update their code to HTTP 1.1 and include the Host header in the API request
D. Merchants needing firewall changes to allow new IP addresses:
Impact to your business: API calls will error out for merchants whose PayPal integration is behind a firewall that uses Access Control List (ACL) rules, and restricts outbound traffic to a limited number of IP addresses.
Your call to action: You need to update your firewall ACL to allow outbound access to a new set of IP addresses we will be publishing. Test your integration on Sandbox (the IP addresses for Sandbox API endpoints are listed at https://ppmts.custhelp.com/app/answers/detail/a_id/250). The list of new IP addresses for our Live API endpoints will be posted at https://ppmts.custhelp.com/app/answers/detail/a_id/92/kw/92 when available in January.
To assist with any questions you may have, Please see the FAQ at https://ppmts.custhelp.com/app/answers/detail/a_id/1063.