Interesting… Did you try to use a different network/router (WiFi/3G/LTE/etc)?

and i think i shoud mention again that if i click on test endpoint for 20 times, i get one 200 response.

Access to XMLHttpRequest at ‘https://real-time-amazon-data.p.rapidapi.com/search?query=Phone&page=1&country=US&category_id=aps’ from origin ‘https://rapidapi.com’ has been blocked by CORS policy: Response to preflight request doesn’t pass access control check: No ‘Access-Control-Allow-Origin’ header is present on the requested resource.

GET https://real-time-amazon-data.p.rapidapi.com/search?query=Phone&page=1&country=US&category_id=aps net::ERR_FAILED

POST https://events.launchdarkly.com/events/bulk/62824a89e7089d15a6f85aa4 net::ERR_SSL_PROTOCOL_ERROR

Access to fetch at ‘https://o493232.ingest.sentry.io/api/5859573/envelope/?sentry_key=f569275a91994757a4df56ef0762f2e6&sentry_version=7&sentry_client=sentry.javascript.react%2F7.51.1’ from origin ‘https://rapidapi.com’ has been blocked by CORS policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource. If an opaque response serves your needs, set the request’s mode to ‘no-cors’ to fetch the resource with CORS disabled.

POST https://o493232.ingest.sentry.io/api/5859573/envelope/?sentry_key=f569275a91994757a4df56ef0762f2e6&sentry_version=7&sentry_client=sentry.javascript.react%2F7.51.1 net::ERR_FAILED 403 (Forbidden)

these errors appeared in console by the way i`m using test endpoint in rapidapi .

Hi,

I think there are two different things here:

1. The original 503 issue you have (CORS related).
2. meiwhizz 503 issue - due to intermittent issues on the cloud provider side - this one is resolved I believe.

Regarding number 1: Can you please copy & paste here the javascript console output (in chrome developer tools) at the time of the API call?

Thank you,
Adam @ OpenWeb Ninja

hello again

the problem still exists.

but now i get a 200 out of 20 function calls and others return 503.

this is happening from yesterday not a few minutes.

but i must say, since yesterday i`m getting 503 from other apis too ! only difference is i get one 503 in every 3 request. but Real-Time Amazon Data
returns 503 almost every time.

so maybe rapidapi is the source of problem ?

Hi,

There was a temporary issue for a few minutes because of a issue on the cloud provider side, it is now back to normal. We are also putting a fallback in place to cover this case.

Sorry for the inconvenience,
Adam @ OpenWeb Ninja

I am also getting 503 error - this is also happening when Testing the Endpoints in RapidAPI - seems to have just started a while ago

I see, thanks for the details.

Can you please copy & paste here the javascript console output (in chrome developer tools) at the time of the API call?

hello,

thanks for responding so fast,

both linux and windows.
even api hub in rapid api is returning 503

Hi there,

Thank you for your message.

I see that all of your requests from the last 3 months succeeded with HTTP 200. This could be a RapidAPI gateway error (that didn’t arrive to the API) or some networking issue. What environment are you using to call the API?

Thank you,
Adam @ OpenWeb Ninja