Incidents reported on status page for Bot.cr https://status.bot.cr/ https://d1lppblt9t2x15.cloudfront.net/logos/37d2d2ea87dcfe84e15f552a8010c93c.png https://status.bot.cr/ en https://status.bot.cr/incident/939966 Tue, 30 Jun 2026 16:30:00 -0000 https://status.bot.cr/incident/939966#06af863e557ae00d88f68b1ad3c1c72851dfd97831f96f57a5eee8ab9b3f06c8 We identified an API consumer making more than 1,000 requests within a short period of time, which exhausted the available database connections. Database connectivity has been restored, and the API is now fully operational. We are following up with the consumer to implement a more scalable synchronization approach and prevent similar incidents in the future. https://status.bot.cr/incident/939966 Tue, 30 Jun 2026 16:00:00 -0000 https://status.bot.cr/incident/939966#ffeaa2167aba70df82f54259c259b05e1d9613fdf007a84f08c08409204a0c1b The API was unavailable due to a loss of connectivity between the API server and the database. https://status.bot.cr/incident/939959 Sat, 27 Jun 2026 17:00:00 -0000 https://status.bot.cr/incident/939959#ed223219eac5d9bfab5cf96b29ea41e5eccb0961d33cc948c80508c5d7e584fa Service was restarted and the sync of the API was resolved https://status.bot.cr/incident/939959 Sat, 27 Jun 2026 16:31:00 -0000 https://status.bot.cr/incident/939959#fd7ba92484243f3c9325222e15db2d0aa8e53970a31c82203298fbffc86e49a7 Some listings were taking more than one day to update reflect the changes done in the API. https://status.bot.cr/incident/940010 Mon, 01 Jun 2026 12:00:00 -0000 https://status.bot.cr/incident/940010#2bb1a70e2e7785bdeb1f4fe92a259a92accabba4b6d6050e5385f9da97dc6be9 The CRM is operating