# API limitations of the pool of public nodes
You can use our public nodes to retreive the information from Waves' blockchain, but we recommend you to use your own nodes, because our pool has some limitations listed in the table below.
- There is a Nginx-server in front of each node in the pool, which limits the amount of connections and the number of requests per second a client is allowed to send to a node.
- In the table below regular expressions are used to express paths' names, such as, for example, \d+.
- The term burst below — is a Nginx's setting that defines the maximum size of the "splash" of the requests. If the amount of arriving requests per second exceeds the defined value, all the exceeding requests are put into a queue. The burst is the size of that queue. If the number of the exceeding requests begins to surpass the value of the burst, then new exceeding requests will not be put into the queue, and will be canceled with the error. Read more in the documentation.
|Path||Maximum number of simultaneous connections to Nginx-server per IP-address (if limit will be exceeded, a client will get HTTP Status 503)||Maximum number of the requests to Nginx-server per IP-address|
|15||20 (burst 50)|
|100||20 (burst 50)|
|/transactions/info/.+||15||20 (burst 50)|
|/blocks/height|/transactions/unconfirmed||15||20 (burst 50)|