Web3Modal API elevated 400 and 403 responses
Incident Report for Reown

Resolved
Web3Modal API availability was impacted for ~2 hours (09.45-11:39 UTC) because of a broken API deployment where requests were resulting in a 400 status (bad request).
In addition to that, projects created after April 18 11:30 UTC were unable to use Web3Modal, as requests to the API were resulting in a 403 status (forbidden).

The incident has been fully resolved.
Posted Apr 22, 2024 - 11:45 UTC
This incident affected: Explorer API.