The API-4 incident has been resolved.

The issue was caused by a hardware failure and has been successfully resolved by our infrastructure teams. All services are now fully operational, and we will continue to closely monitor the infrastructure to ensure stability.

If you experience any remaining issues, please contact our support team through the dashboard.

We sincerely apologize for the inconvenience caused and thank you for your patience.

API-4 is currently unavailable. Our team is actively investigating the issue and working to restore service as quickly as possible.

We will provide an update as soon as we have more information.

Thank you for your patience.

This incident has now been fully resolved, and all affected services are operating normally again.

Our team has completed the necessary fixes and continues to monitor the service to ensure stability.

If you are still experiencing any issues, please contact us through the dashboard support chat with the relevant details so our team can investigate.

Thank you for your patience.

It is currently not possible to add a new WhatsApp account to Unipile. The authentication flow, including QR code generation and scanning, is temporarily unavailable due to an outage affecting an external dependency required by this process.

We have identified the source of the issue. No action can currently be taken on our side, and account authentication will become available again once the affected third-party service is operational.

Existing WhatsApp accounts already connected to Unipile are not affected.

The incident related to LinkedIn's recent Classic Search changes is now fully resolved.

100% of Classic Search features are operational again across both V1 and V2, including People, Company, and Post Search.

We have also addressed the edge cases reported by customers following the rollout.

If you still encounter any unexpected behavior or a specific edge case, please contact us through the dashboard support chat with the complete API request so our team can investigate.

Thank you for your patience throughout this incident.

The updates for LinkedIn Classic Company Search and Post Search are now finalized.

The V1 update will be progressively deployed to all customers within the next few hours, with the full rollout expected by 4:00 AM UTC.

The same changes will be deployed to V2 during the day on August 14.

A few edge cases may still require adjustments tomorrow as we monitor the new implementation across different accounts and search configurations.

If you encounter any issue after the rollout, please contact us through the dashboard support chat and include the complete API request causing the issue. This will allow our team to investigate and adjust any remaining edge cases quickly.

We will continue monitoring the rollout closely.

The Classic Search update has now been successfully deployed to all customers.

If you still encounter unexpected results, please send us the exact search request through the support chat in your dashboard. We can continue adjusting a few remaining edge cases, particularly around shared relations, keyword matching with some language-specific variations, and missing profile pictures.

Following LinkedIn's changes, there are also two permanent changes to Classic Search:

• The limit parameter is now automatically limited to a maximum of 10 results per page.
• The total count is no longer available, as LinkedIn no longer provides this information in its Classic Search UI.

Our team is now working on finalizing the update for Classic Company Search and Post Search for accounts where LinkedIn's changes have made the previous search method unavailable.

We will provide another update as soon as these remaining search types are ready.

[V2] Update - LinkedIn Classic Search The first fix for LinkedIn's classic search has now been finalized and successfully tested on V2. The search for PEOPLE is now fully functional. Our team is now working on search for companies and posts.

[V1] Update - LinkedIn Classic Search The first fix for LinkedIn's classic search has now been finalized and successfully tested on V1. The search for PEOPLE is now fully functional. Our team is now working on search for companies and posts. Customers who need the update immediately can contact our support team, and we can enable it for their accounts on request. The update will be automatically rolled out to all affected accounts on V1 tonight at 4:00 AM CEST, as planned. We will continue monitoring the rollout and will provide a final update once it is fully deployed.

We have made significant progress on adapting to LinkedIn's recent Classic Search changes.

Our team is now completing the final adjustments and testing to ensure everything works as expected.

We plan to start rolling out the fix to the first users who contacted our support team around August 11 at 1:00 PM CEST, followed by a full rollout to all affected accounts around August 12 at 4:00 AM CEST.

Thank you for your patience. We will continue to keep you updated as the rollout progresses.

LinkedIn has introduced changes to its Classic Search and has started gradually rolling them out to a limited number of accounts.

As a result, LinkedIn Classic Search may return 0 results for some affected accounts.

Our team has already identified the changes and is actively working on adapting the integration. We expect to deploy the necessary updates at the beginning of next week.

We are continuing to monitor the rollout and will provide updates as we make progress.

We identified performance degradation affecting parts of our infrastructure starting around 06:00 UTC.

Throughout the day, we have deployed several improvements that have significantly reduced the impact. However, some requests may still experience increased latency, timeouts, or occasional failures.

Our team continues to closely monitor the situation and is working to fully resolve the remaining issues. We will provide another update within the next few hours, or sooner if the situation changes.

If you are still experiencing any issues, please don't hesitate to contact our support team with details so we can investigate your specific case.

The WhatsApp integration has been updated to support the latest provider-side changes.

We are currently investigating an issue affecting our WhatsApp integration.

WhatsApp experienced a disruption overnight. The service has now recovered for our V1 platform, but V2 is still affected. At this stage, we suspect this may be related to a change on WhatsApp's side following the outage, although the exact cause has not yet been confirmed.

Our team is actively investigating the issue and will provide updates as soon as we have more information.

The incident has now been resolved, and all affected services are operating normally again.

The root cause was an issue within our hosting provider's high-availability database infrastructure. Service has now been restored, and our platform is fully operational.

Although the incident is resolved, our engineering team will continue to closely monitor the platform over the coming hours to ensure continued stability.

Thank you for your patience and understanding throughout this incident.

We have identified that the issue originates from our hosting provider, Scaleway, and is affecting their high-availability database infrastructure.

Scaleway has acknowledged the incident and is actively working on a resolution. Their incident report is available here: https://status.scaleway.com/incidents/bsp2y5fysy9w

Our engineering team is in direct contact with Scaleway and is closely monitoring the situation. In parallel, we are evaluating alternative solutions and mitigation strategies should the incident persist longer than expected.

We will continue to provide updates as soon as new information becomes available.

We are currently investigating an issue affecting database access on our infrastructure.

As a result, some services may experience intermittent issues, including:

Dashboard V1 Hosted Auth V2 Beta

Our team is actively working to identify the root cause and restore normal service as quickly as possible.

We will provide another update as soon as we have more information.

Monitoring - Network Connectivity Restored

Connectivity appears to have been restored following the network incident affecting Scaleway's PAR2 datacenter.

The affected API clusters are now reachable again, and services are progressively returning to normal operation.

Current Status Our team is currently performing verification checks across all affected infrastructure to ensure that services, containers, databases, queues, webhooks, and background workers have fully recovered and are operating normally.

Impact Customers may have experienced temporary connection failures, increased latency, webhook delivery delays, authentication issues, or service interruptions between 11:08 UTC and the restoration of network connectivity.

Started June 22, 2026 – 11:08 UTC

Status Monitoring

We will continue monitoring the platform and will publish a final update once all verification checks have been completed successfully.

Investigating - Network Incident at Scaleway (PAR2)

We are currently investigating a network incident affecting a full datacenter zone at our infrastructure provider, Scaleway (PAR2).

The incident impacts the following API clusters:

API-1, API-3, API-4, API-8, API-9, API-10, API-11, API-13, API-15, API-17, API-19, API-23, API-25, API-26, API-28, API-30, API-32, API-34, API-36, API-38, API-40, API-42, API-45, API-47, API-49, and API-51.

Impact Customers hosted on the affected infrastructure may experience connection failures, increased latency, webhook delivery delays, authentication issues, or temporary service unavailability.

Current Status The issue has been identified as an upstream network incident within Scaleway's PAR2 datacenter. We are actively monitoring the situation and working with Scaleway's teams while they restore connectivity.

Started June 22, 2026 – 11:08 UTC

We will continue to provide updates as more information becomes available from Scaleway and our monitoring systems.

The incident affecting customers hosted on API-46 has been resolved.

Root cause: a hardware issue with the server's disk caused service disruption. The faulty hardware has been replaced and all services have been fully restored.

The API and dashboard are now operating normally.

We are currently investigating an incident affecting customers hosted on API-46

Impact: Users may be unable to access both the API and the dashboard.

Our team is actively investigating the issue and working to restore service as quickly as possible. We will provide updates as soon as more information becomes available.

The issue has now been resolved.

Services are progressively returning to normal operation. Many services are already fully operational, while a few remaining components are still completing their startup and verification procedures.

We are closely monitoring the platform and expect the last remaining services to be fully restored within the next few minutes.

We fully understand the impact that this prolonged interruption has had on your production environments and the disruption it may have caused to your teams and customers.

We will be conducting a full review of this incident and taking the necessary measures to prevent a similar situation from occurring again.

Thank you for your patience and understanding throughout this incident.

We are actively working on restoring API-8.

The infrastructure issue has been resolved, and we are currently waiting for the RAID array to fully resynchronize before bringing services back online. This precaution is necessary to ensure no data is lost and that the platform returns to a healthy state.

We expect a return to normal operation within the next few minutes.

Thank you for your patience.

We are currently experiencing a new incident affecting API-8.

Following the previous outage, Scaleway performed an unplanned maintenance operation on the underlying infrastructure, which has resulted in API-8 becoming unavailable again.

Our team is actively working with Scaleway's engineers to restore service as quickly as possible. We are monitoring the situation closely and will provide further updates as soon as we have additional information.

Affected services: API-8 Status: Investigating / In Progress Root cause: Unplanned infrastructure maintenance performed by Scaleway following the previous incident. Current action: Coordinating with Scaleway to restore service.

We apologize for the inconvenience and will keep you informed of any developments.

Resolved – API-8 Incident

The incident affecting customers hosted on API-8 has been resolved.

This outage was a continuation of the initial hardware incident reported earlier. During the additional maintenance, further issues were identified on the affected server, requiring additional intervention.

The necessary corrective actions have now been completed and all services are operating normally.

We will continue to closely monitor to ensure stability.

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

The incident affecting customers hosted on API-8 is still ongoing.

While service was temporarily restored, additional hardware-related issues have been identified. Our team is actively working on a permanent resolution.

Users may continue to experience intermittent access issues affecting both the API and the dashboard.

We will provide further updates as soon as possible.

The incident affecting customers hosted on API-8 has been resolved.

Root cause: a hardware issue with the server's disk caused service disruption, a fix have been deployed .

We apologize for the inconvenience and will continue to monitor the platform closely.

We are currently investigating an incident affecting customers hosted on API-8.

Impact: Users may be unable to access both the API and the dashboard.

Our team is actively investigating the issue and working to restore service as quickly as possible. We will provide updates as soon as more information becomes available.

The updates have now been deployed and the service has been restored.

We will continue to closely monitor the situation and make additional adjustments if necessary.

If you encounter duplicate chats, this may be due to some conversation IDs having changed on Instagram's side. In this case, the simplest solution is to delete the account and reconnect it, which will rebuild the chat mapping with the latest identifiers.

Thank you for your patience throughout this incident.

A fix have been deployed, additional updates will follow over the coming hours to fully adapt to Instagram's changes and restore some remaining features, like media retrieval.

Thank you for your patience while we complete these final adjustments.

We are continuing to work on adapting to the Instagram changes. The modifications introduced on their side are fairly significant and require deeper adjustments than initially expected.

Our team is actively working on the fix, and we are making good progress. We currently hope to deploy an update within the next few hours and will keep you informed as soon as we have more information.

Thank you for your patience.

Instagram has made a change on its end that is affecting the startup of Realtime. We have identified the issue, and a fix is currently being developed.

The incident affecting customers hosted on API-25 has been resolved.

Root cause: a hardware issue with the server's RAM caused service disruption. The faulty hardware has been replaced and all services have been fully restored.

The API and dashboard are now operating normally.

We apologize for the inconvenience and will continue to monitor the platform closely.

We are currently investigating an incident affecting customers hosted on API-25.

Impact: Users may be unable to access both the API and the dashboard.

Our team is actively investigating the issue and working to restore service as quickly as possible. We will provide updates as soon as more information becomes available.