Help Center

Diving Deeper

Does MEW API Have a Limit on the Amount of Requests I Can Make?

2 min read

If you are a heavy user of our API or MyEtherWallet (MEW), you may get rate-limited.

If so, it typically looks something like this:

Error: Invalid JSON RPC response: ERROR: The request could not be satisfied. The origin closed the connection. Generated by cloudfront (CloudFront) Request ID: XXXXXXX \" at Object.InvalidResponse (/home/drone/projects/mew/asset-position-disposal/node_modules/web3/lib/web3/errors.js:38:16) at XMLHttpRequest.request.onreadystatechange (/home/drone/projects/mew/asset-position-disposal/node_modules/web3/lib/web3/httpprovider.js:115:32) at XMLHttpRequestEventTarget.dispatchEvent (/home/drone/projects/mew/asset-position-disposal/node_modules/xhr2/lib/xhr2.js:64:18) at XMLHttpRequest._setReadyState (/home/drone/projects/mew/asset-position-disposal/node_modules/xhr2/lib/xhr2.js:354:12) at XMLHttpRequest._onHttpResponseEnd (/home/drone/projects/mew/asset-position-disposal/node_modules/xhr2/lib/xhr2.js:509:12) at IncomingMessage.<anonymous> (/home/drone/projects/mew/asset-position-disposal/node_modules/xhr2/lib/xhr2.js:469:24) at emitNone (events.js:110:20) at IncomingMessage.emit (events.js:207:7) at endReadableNT (_stream_readable.js:1047:12) at _combinedTickCallback (internal/process/next_tick.js:102:11)

(Source)

MyEtherWallet, at the time of this writing, rate-limits at 400 requests per minute (or about 6 requests per second). This is in order to prevent DDOS’s like we have seen before, or people using our nodes to excess and making us pay an even larger bill.

Our goal is to allow individuals to interact with Ethereum, not provide uber-robust infrastructure for all your heart’s desires. This should be more than enough for a single person’s use, but feel free to reach out to us about why you need more, and we can adjust.

If you are going to be using it more than 400 req per minute on average, or just want to ensure uptime, we strongly recommend you get your own node.

Our backend infrastructure is on AWS and is open-source via Docker + CloudFormation walkthrough. You can actually do it yourself and run your own public or private node via these instructions.

Or you could pay a small fee and use QuikNode, which makes it even easier.

For both of these options, you could connect to your new node via the ‘Add Custom Node’ option in the network selector in the top-right corner. Further details on how to connect to your own node can be found here, or you could connect directly via API.

Does MEW API Have a Limit on the Amount of Requests I Can Make?

2 min read

If you are a heavy user of our API or MyEtherWallet (MEW), you may get rate-limited.

If so, it typically looks something like this:

Error: Invalid JSON RPC response: ERROR: The request could not be satisfied. The origin closed the connection. Generated by cloudfront (CloudFront) Request ID: XXXXXXX \" at Object.InvalidResponse (/home/drone/projects/mew/asset-position-disposal/node_modules/web3/lib/web3/errors.js:38:16) at XMLHttpRequest.request.onreadystatechange (/home/drone/projects/mew/asset-position-disposal/node_modules/web3/lib/web3/httpprovider.js:115:32) at XMLHttpRequestEventTarget.dispatchEvent (/home/drone/projects/mew/asset-position-disposal/node_modules/xhr2/lib/xhr2.js:64:18) at XMLHttpRequest._setReadyState (/home/drone/projects/mew/asset-position-disposal/node_modules/xhr2/lib/xhr2.js:354:12) at XMLHttpRequest._onHttpResponseEnd (/home/drone/projects/mew/asset-position-disposal/node_modules/xhr2/lib/xhr2.js:509:12) at IncomingMessage.<anonymous> (/home/drone/projects/mew/asset-position-disposal/node_modules/xhr2/lib/xhr2.js:469:24) at emitNone (events.js:110:20) at IncomingMessage.emit (events.js:207:7) at endReadableNT (_stream_readable.js:1047:12) at _combinedTickCallback (internal/process/next_tick.js:102:11)

(Source)

MyEtherWallet, at the time of this writing, rate-limits at 400 requests per minute (or about 6 requests per second). This is in order to prevent DDOS’s like we have seen before, or people using our nodes to excess and making us pay an even larger bill.

Our goal is to allow individuals to interact with Ethereum, not provide uber-robust infrastructure for all your heart’s desires. This should be more than enough for a single person’s use, but feel free to reach out to us about why you need more, and we can adjust.

If you are going to be using it more than 400 req per minute on average, or just want to ensure uptime, we strongly recommend you get your own node.

Our backend infrastructure is on AWS and is open-source via Docker + CloudFormation walkthrough. You can actually do it yourself and run your own public or private node via these instructions.

Or you could pay a small fee and use QuikNode, which makes it even easier.

For both of these options, you could connect to your new node via the ‘Add Custom Node’ option in the network selector in the top-right corner. Further details on how to connect to your own node can be found here, or you could connect directly via API.

Customer Support

Help Center

Diving Deeper

Does MEW API Have a Limit on the Amount of Requests I Can Make?

2 min read

If you are a heavy user of our API or MyEtherWallet (MEW), you may get rate-limited.

If so, it typically looks something like this:

Error: Invalid JSON RPC response: ERROR: The request could not be satisfied. The origin closed the connection. Generated by cloudfront (CloudFront) Request ID: XXXXXXX \" at Object.InvalidResponse (/home/drone/projects/mew/asset-position-disposal/node_modules/web3/lib/web3/errors.js:38:16) at XMLHttpRequest.request.onreadystatechange (/home/drone/projects/mew/asset-position-disposal/node_modules/web3/lib/web3/httpprovider.js:115:32) at XMLHttpRequestEventTarget.dispatchEvent (/home/drone/projects/mew/asset-position-disposal/node_modules/xhr2/lib/xhr2.js:64:18) at XMLHttpRequest._setReadyState (/home/drone/projects/mew/asset-position-disposal/node_modules/xhr2/lib/xhr2.js:354:12) at XMLHttpRequest._onHttpResponseEnd (/home/drone/projects/mew/asset-position-disposal/node_modules/xhr2/lib/xhr2.js:509:12) at IncomingMessage.<anonymous> (/home/drone/projects/mew/asset-position-disposal/node_modules/xhr2/lib/xhr2.js:469:24) at emitNone (events.js:110:20) at IncomingMessage.emit (events.js:207:7) at endReadableNT (_stream_readable.js:1047:12) at _combinedTickCallback (internal/process/next_tick.js:102:11)

(Source)

MyEtherWallet, at the time of this writing, rate-limits at 400 requests per minute (or about 6 requests per second). This is in order to prevent DDOS’s like we have seen before, or people using our nodes to excess and making us pay an even larger bill.

Our goal is to allow individuals to interact with Ethereum, not provide uber-robust infrastructure for all your heart’s desires. This should be more than enough for a single person’s use, but feel free to reach out to us about why you need more, and we can adjust.

If you are going to be using it more than 400 req per minute on average, or just want to ensure uptime, we strongly recommend you get your own node.

Our backend infrastructure is on AWS and is open-source via Docker + CloudFormation walkthrough. You can actually do it yourself and run your own public or private node via these instructions.

Or you could pay a small fee and use QuikNode, which makes it even easier.

For both of these options, you could connect to your new node via the ‘Add Custom Node’ option in the network selector in the top-right corner. Further details on how to connect to your own node can be found here, or you could connect directly via API.

Does MEW API Have a Limit on the Amount of Requests I Can Make?

2 min read

If you are a heavy user of our API or MyEtherWallet (MEW), you may get rate-limited.

If so, it typically looks something like this:

Error: Invalid JSON RPC response: ERROR: The request could not be satisfied. The origin closed the connection. Generated by cloudfront (CloudFront) Request ID: XXXXXXX \" at Object.InvalidResponse (/home/drone/projects/mew/asset-position-disposal/node_modules/web3/lib/web3/errors.js:38:16) at XMLHttpRequest.request.onreadystatechange (/home/drone/projects/mew/asset-position-disposal/node_modules/web3/lib/web3/httpprovider.js:115:32) at XMLHttpRequestEventTarget.dispatchEvent (/home/drone/projects/mew/asset-position-disposal/node_modules/xhr2/lib/xhr2.js:64:18) at XMLHttpRequest._setReadyState (/home/drone/projects/mew/asset-position-disposal/node_modules/xhr2/lib/xhr2.js:354:12) at XMLHttpRequest._onHttpResponseEnd (/home/drone/projects/mew/asset-position-disposal/node_modules/xhr2/lib/xhr2.js:509:12) at IncomingMessage.<anonymous> (/home/drone/projects/mew/asset-position-disposal/node_modules/xhr2/lib/xhr2.js:469:24) at emitNone (events.js:110:20) at IncomingMessage.emit (events.js:207:7) at endReadableNT (_stream_readable.js:1047:12) at _combinedTickCallback (internal/process/next_tick.js:102:11)

(Source)

MyEtherWallet, at the time of this writing, rate-limits at 400 requests per minute (or about 6 requests per second). This is in order to prevent DDOS’s like we have seen before, or people using our nodes to excess and making us pay an even larger bill.

Our goal is to allow individuals to interact with Ethereum, not provide uber-robust infrastructure for all your heart’s desires. This should be more than enough for a single person’s use, but feel free to reach out to us about why you need more, and we can adjust.

If you are going to be using it more than 400 req per minute on average, or just want to ensure uptime, we strongly recommend you get your own node.

Our backend infrastructure is on AWS and is open-source via Docker + CloudFormation walkthrough. You can actually do it yourself and run your own public or private node via these instructions.

Or you could pay a small fee and use QuikNode, which makes it even easier.

For both of these options, you could connect to your new node via the ‘Add Custom Node’ option in the network selector in the top-right corner. Further details on how to connect to your own node can be found here, or you could connect directly via API.

Customer Support