Hello we are having too many time out and SSL exception errors from
https://buy.itunes.apple.com/verifyReceipt
Issue start date 24 Jan 2020 15:10 GMT+3
Is there anyone having same problem
Hello we are having too many time out and SSL exception errors from
https://buy.itunes.apple.com/verifyReceipt
Issue start date 24 Jan 2020 15:10 GMT+3
Is there anyone having same problem
Not marked green anymore, for whatever that's worth. Did anyone have a specific IP address for the endpoint that was still working? I did a scan through some of them and didn't find a working one.
Having the same issue in UK since around 12:00. Getting SSL errors and HTML responses coming through instead of the expected JSON response
Same; first occurrence at 2020-01-24 14:23 UTC
Failing for us too. https://buy.itunes.apple.com/verifyReceipt is returning HTML
I called support but they were of no help. Their system status does show now that there is an ongoing issue for the "App Store" but nothing beyond that :-(
It looks like the Apple System Status is back to Green (and was briefly marked "Resolved"). That said, we're still definitely experiencing the issue.
We have been experiencing this problem for the past 4 hours.. I tried reporting it to Apple Support via phone but was not successful.
Still broken when it resolves to the 17.120.254.x range, but working if it resolves to the 17.173.66.x or 17.42.254.x ranges.
Same error
"Connecting to the iTunes Store" HTML responses.
Receipt verification failed: jsonDecodeError
Can confirm that we are still experiencing the issue on all our games.
We are also experiencing this issue when hitting the verifyReceipt endpoint, it is returning strange "connecting..." HTML instead of JSON.
Still broken here too. At least the indicator is now green. It would be nice if the HTML error message became JSON again soon.
We're starting to see signs of recovery. The API is returning expected results, and errors are dropping sharply across our monitoring.
Yup. Looks like the problem was fixed 3 minutes before your post.
Anyone else still experiencing these errors/timeouts frequently in the last 2 days?