Deep Index Errors: 520, 502

Technical Issue Reporting
#12

If you DM me, I’ll send you my API key to test with. My pro account is currently for testing. I dont have any data in Moralis. I just use it for node access.

#13

I don’t think that the api key is the problem in this case

#14

Was there any change in your API response headers configuration recently? @cryptokid @ivan
Most of my jobs stopped working properly so it’s a big blocker for me .

Thanks for your time guys

#15

I don’t know of any change in API response headers configuration

can you try to make the requests from a different location to see if there is a difference?

#16

I tested it with another network and it worked properly so I’m pretty sure it’s on cloudflare side then. Same as @shrimplypibbles, I do a lot of calls and I suspect my IP to be banned from. When we do a lot of calls we should face rate limiting errors from Moralis but not be blocked by Cloudflare…

Is it possible to be whitelisted again?

#17

if the IP would be banned, then you could not do any call in a specific time interval

anyway, send me the IP din DM

#18

I believe I’m experiencing this. I haven’t been able to make a call since this thread was posted.

#19

what error do you get?

#20

For the logs endpoint, I get unknown error or request aborted.

For erc20 metadata, sometimes empty response. Ex: https://deep-index.moralis.io/api/v2/erc20/metadata?chain=eth&addresses=0x8a6D4C8735371EBAF8874fBd518b56Edd66024eB

#21

this works for me now, I tried 10 times

#22

I switched my IP to a VPN provided IP and it works again. I have not triggered any rate limits yet. I suspect if I do, this same issue will happen to my new IP. So I will test that out after I finish building, or if im able to obtain another IP.

1 Like
#23

I increased my requests per second to 20, and now im facing the 502 errors again. This time, subsequent requests are met with a 504

#24

and if you decrease it now it works well?

we did a change in API backend recently (~15-30 minutes ago), if you see something strange it could also be because of that change

#25

correct, it works fine at 10 requests per second for small payloads.

Longer payloads now timeout with a 504 after a few minutes.

Its a bit disappointing though because the pro plan should be netting us about 60 requests per second if im not mistaken

#26

you have a request example for this?

#27

can you try now again with larger payloads?

#28
#29

i execute each of those 10 per second. It consistently fails with a 504

1 Like
#30

I was able to replicate that 504 error sometimes with that list

#31

now you should not get that 504 error