Hacker Newsnew | past | comments | ask | show | jobs | submit | aertmann's commentslogin

  Update:

  We are continuing to monitor the impact on multiple 
  components in our production environment. We observe 
  mitigation as of Tue, 08 Apr 2025 22:42 GMT

  Our technical teams have identified the External root cause 
  and are actively working with the vendor to mitigate the 
  impact as quickly as possible. We will continue to provide 
  updates as the situation progresses.

  Affected Regions: Global
  Apr 8, 21:51 UTC


And gone, evidence wiped.


Weirdly enough I was able to work around this outage by using their new API endpoint URL api-m.paypal.com / api-m.sandbox.paypal.com instead of api.paypal.com / api.sandbox.paypal.com. No more 403s in the auth endpoint using the new URL that they use in their updated documentation: https://developer.paypal.com/api/rest/authentication

This URL change doesn't seem well communicated at all, but some people have gotten an email but there's no such details available officially anywhere publicly as far as I can tell.

https://www.paypal-community.com/t5/REST-APIs/Migrating-api-... https://www.paypal-community.com/t5/NVP-SOAP-APIs/will-new-c...


Can confirm, S3 backed CloudFront experiencing random errors in us-east-2 for the past 15 minutes at least.


Same here, since 27 minutes. Now acknowledged on https://health.aws.amazon.com/health/status


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: