Is YouScan Down?

This incident has been resolved. --- [2026-07-01T13:50:41.734+03:00] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-07-01T13:39:24.533+03:00] (identified) Customers might experience up to 30 minutes delay in regular data ingestion.

This incident has been resolved. --- [2026-05-22T16:56:11.576+03:00] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-05-22T13:01:13.239+03:00] (identified) Users can create topics now Note that preview statistics may be inaccurate now --- [2026-05-22T11:58:29.645+03:00] (identified) Our data storage provider started maintenance that affected our history storage Users cannot temporarily create topics and may be facing issues with history collection

The recovery work for the May 19 incident is now fully complete: - All affected topics have been fully restored - Mentions ingested during the affected window (01:15–14:00 CEST on May 19) have been backfilled into the impacted topics. - Manual and API markup changes from the affected period have been replayed and reapplied. Your topics, mentions, and markup should now reflect a complete and consistent state. If you notice anything still missing or inconsistent in your workspace, please contact support, and we'll investigate right away. We sincerely apologize for the disruption and thank you for your patience while we worked through the recovery. --- [2026-05-20T14:06:40.375+03:00] (monitoring) Service restored. Data recovery in progress. **Summary** On May 19, during planned maintenance of our mentions storage cluster, an operational error caused a portion of recently indexed data to become temporarily unavailable, and the YouScan application was briefly impacted. We have restored service and are in the process of recovering the affected data. **What was affected** * **YouScan application** — briefly unavailable on May 19 (around 14:00–14:30 CEST). Fully restored. * **Topic creation** — was unavailable on May 19 between approximately 14:00 and 22:00 CEST. Fully restored. * **Mentions data** — mentions ingested between approximately 01:15 and 14:00 CEST on May 19 were affected. We have restored the bulk of this data from our most recent backup and are re-collecting the remainder directly from the internal intermediate storage. * **Markup applied manually or via API** — tagging, sub-category assignments, sentiment changes, etc. performed during the affected window were lost when data was rolled back to the backup. We are replaying these actions automatically from our internal transaction logs. **What we've done** * Restored the affected topics from the most recent snapshot. * Initiated re-collection of mentions for affected topics. * Started automated replay of markup actions performed during the affected window. **What to expect** We expect to fully recover the affected data. * Any missing mentions (ingested between 01:15 and 14:00 CEST) will continue to backfill over the next 24 hours. No action is required on your part — affected topics will fill in automatically. * Any changes made to mentions during the affected window will be applied automatically as well. We sincerely apologize for the disruption and thank you for your patience. — The YouScan Team --- [2026-05-20T00:16:50.168+03:00] (monitoring) We are continuing to monitor for any further issues. --- [2026-05-19T19:53:41.858+03:00] (monitoring) All missing topics are recovered. Any mentions that might be missing will be backfilled soon. --- [2026-05-19T16:01:17.364+03:00] (identified) YouScan is currently experiencing a platform incident. Our engineering team is actively investigating and working to restore full service as quickly as possible. We sincerely apologize for the disruption. We know how much you rely on YouScan, and we are fully focused on resolving this. Updates will follow as soon as we have more information. Thank you for your patience and understanding. --- [2026-05-19T15:52:34.614+03:00] (identified) We are continuing to work on a fix for this issue. --- [2026-05-19T15:52:22.315+03:00] (identified) We have identified the root cause, and are restoring the data right now --- [2026-05-19T15:29:02.456+03:00] (investigating) We are currently investigating this issue.