This week, we released a new way to secure your RPC Endpoints by limiting the number of requests that can be made to them. Additionally, we added a new section to the Analytics to show the location of the requests.
Security: Rate Limit
Protecting your API keys from being leaked is not always possible, and we understand that. That's why we added a Rate Limit option to secure your underlying RPC infrastructure from abuse.
To see the rate limit, select your desired project and go to the Security section. You will find a new section called Rate Limit.
Our rate limit feature allows you to set the number of requests that can be made to your RPC endpoints within a given time frame and choose the algorithm to determine the window. To learn more, check out our Rate Limit documentation.
Analytics: Location and Source
In Analytics, we enhanced the display of location data. Now, in addition to seeing the map, you can view a list of the countries and cities from where the requests are originating.
Additionally, we added a new section to show the source of the requests.
Transactions: Error Filter
You can now easily filter your transaction logs by error.
Miscellaneous
Some other minor improvements we worked on this week include:
- Ability to filter logs by
426response status code - Improved WebSocket observability
What's next?
Looking ahead, we continue to work on the Alerts release. We expect it to be available in approximately two weeks.
If you want to stay updated with our progress, you can follow us on Twitter