Cronologia incidenti

We will be performing an upgrade of our authentication database to improve reliability and performance.

The maintenance is planned for Friday, June 12 at 00:00 UTC and is expected to last less than 2 minutes. We have chosen this time to minimize the impact.

During this maintenance window, the following services will be temporarily unavailable:

• All authenticated API v1 endpoints
• Authentication to the platform through the UI

API v2 will not be affected, as it uses a new separate authentication system based on API keys.

Thank you for your understanding and patience while we complete this upgrade.

During a database upgrade, our service experienced approximately 14 minutes of downtime. We had anticipated less than 5 minutes, but the upgrade took longer than expected.

We chose to perform this maintenance during a low-traffic period (21:45 UTC) to minimize the impact on our users. While the downtime exceeded our target, we will learn from this experience and improve our processes.

For future major upgrades, we will communicate in advance and ensure better planning around maintenance windows.

The good news is that the database upgrade was successfully completed. This major upgrade brings significant performance improvements and provides a stronger foundation to support our growth.

Thank you for your understanding and patience. We truly appreciate your support.

The platform is currently experiencing service disruptions related to a database upgrade. Our team is actively working to restore full functionality as quickly as possible.

We apologize for the inconvenience and appreciate your patience while we complete this important infrastructure improvement. Updates will be provided as they become available.

We will perform a major database upgrade. During this time, all write operations will be unavailable.

Expected duration: less than 5 minutes.

We apologize for the inconvenience and thank you for your understanding.

To prepare for a database upgrade that will bring significant performance improvements, we will restart the database around 18:00 UTC. The operation will take only a few seconds, but the application may experience brief disruptions during that time.

We apologize for any inconvenience.

Between 08:23 UTC and 08:32 UTC, we experienced an incident affecting the entire application, resulting in several timeouts. The issue was caused by our search feature, which triggered a significant CPU spike on our database infrastructure.

We have deployed a hotfix to temporarily limit the feature’s capabilities while we work on a new, more performant solution designed to prevent this type of issue from happening again.