We are currently experiencing a delay in updating data in Sympa

Update timeline

1. monitoring Apr 15, 2026, 01:44 PM UTC

   This means that when new information is added, for example a new employee, it may not appear in the system immediately. Some updates may show within seconds or minutes, while others can take longer. We have increased system capacity and are closely monitoring the situation to reduce the delays. We’re sorry for the inconvenience and will keep you updated. Your Sympa Team

2. monitoring Apr 15, 2026, 02:51 PM UTC

   The delays in updating data in Sympa have now returned to normal levels. New information, such as added employees, should now appear in the system as expected, including in reporting. We will continue to monitor the situation closely to ensure everything remains stable before closing this incident. Thank you for your patience, and we’re sorry for the inconvenience. Your Sympa Team

3. resolved Apr 15, 2026, 04:59 PM UTC

   The issue causing delays in updating data in Sympa has been resolved. Data is now updating normally, and new information, such as added employees, is visible in the system as expected, including in reporting. We have monitored the situation and confirmed that everything is stable. Thank you for your patience, and we’re sorry for the inconvenience. Your Sympa Team

4. postmortem Apr 20, 2026, 06:09 AM UTC

   **What happened** * We experienced delays in updating data in Sympa. This meant that when new information was added—such as a new employee—it did not always appear in the system immediately. Some updates were processed within seconds or minutes, while others took longer than expected. Additionally, some customers may have experienced slowness when using reporting features. **Why it happened** * The delays were caused by an unusually high load in the system. This increased volume of updates created a backlog, meaning that new information had to wait longer than usual before being processed and displayed. **What we did** * Increased system capacity to handle the higher load * Scaled up our reporting infrastructure to improve performance * Monitored the system closely to reduce the backlog of updates * Continued to track performance to ensure the situation stabilized