Historia awarii Socialdog

1. 28 października 2026 02:47 UTCresolved

   Dziękuję za użycie Social Dog. Informujemy, że problem, który pojawił się po niedawnej aktualizacji systemu, został rozwiązany. Wszystkie funkcje funkcjonują teraz normalnie. Serdecznie przepraszamy za wszelkie zakłócenia i niedogodności, które mogły doprowadzić do waszego przepływu pracy. Okres odniesienia 2026 / 10 / 28 11: 22 - 11: 37 (JST) Agresywne funkcje Podczas incydentu niektórzy użytkownicy mogli doświadczyć błędów podczas przeglądania stron lub wykonywania działań w aplikacji SocialDog. Powód Kwestia ta została spowodowana zmianą ustawień systemu zawartych w najnowszej aktualizacji systemu. Poprawiliśmy konfigurację i potwierdziliśmy, że wszystkie usługi SocialDog działają normalnie. Wdrożenie przyszłych środków Przeglądamy konfigurację systemu, aby zapobiec podobnym problemom w przyszłości. Dziękuję za cierpliwość i zrozumienie. Doceniamy twoje ciągłe wsparcie dla SocjalDog.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 25 września 2026 13:10 UTCresolved

   Dziękuję za użycie Social Dog. Chcielibyśmy poinformować, że sprawa, która miała miejsce 25 września, została rozwiązana. Wszystkie funkcje funkcjonują teraz normalnie. Serdecznie przepraszamy za wszelkie zakłócenia i niedogodności, które mogły doprowadzić do waszego przepływu pracy. Okres odniesienia 2026 / 9 / 25 21: 22 - 21: 44 (JST) Agresywne funkcje Podczas incydentu, niektórzy użytkownicy mogli doświadczyć błędów podczas przeglądania stron lub wykonywania działań na stronie SocialDog (Web i app). Powód Ta kwestia była spowodowana chwilową niestabilną komunikacją sieciową pomiędzy niektórymi naszymi serwerami a naszymi systemami wewnętrznymi. Od tego czasu komunikacja uległa poprawie i potwierdziliśmy, że wszystkie usługi SocialDog działają normalnie. Wdrożenie przyszłych środków Przeglądamy konfigurację systemu, aby zapobiec podobnym problemom w przyszłości. Dziękuję za cierpliwość i zrozumienie. Doceniamy twoje ciągłe wsparcie dla SocjalDog.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 15 sierpnia 2026 00:44 UTCinvestigating

   Thank you for using SocialDog. We are currently experiencing a system issue where a temporary error has occurred during communication with the X API. We sincerely apologize for any disruption and inconvenience this may cause to your workflow. 【Affected Period】 2026/8/15 7:00 (JST) – Ongoing 【Issue Details】 ・Conversation trends ・Keyword Monitor 【Cause】 This issue was caused by temporary errors and instability in our system's communication with the X API. 【Current Status】 We will provide further updates on this page as soon as more information becomes available. Thank you for your patience and understanding while we work to resolve this.

2. 17 sierpnia 2026 05:38 UTCmonitoring

   The incident is now resolved. We are currently monitoring the status of the incident. We apologize for any inconvenience.

3. 17 sierpnia 2026 13:21 UTCresolved

   The incident is now resolved. We apologize for any inconvenience.

1. 13 sierpnia 2026 06:35 UTCinvestigating

   Thank you for using SocialDog. We are currently experiencing a system issue where a temporary error has occurred during communication with the X API. We sincerely apologize for any disruption and inconvenience this may cause to your workflow. 【Affected Period】 2026/8/13 12:45 (JST) – Ongoing 【Issue Details】 ・Conversation trends ・Keyword Monitor 【Cause】 This issue was caused by temporary errors and instability in our system's communication with the X API. 【Current Status】 We will provide further updates on this page as soon as more information becomes available. Thank you for your patience and understanding while we work to resolve this.

2. 14 sierpnia 2026 05:42 UTCresolved

   This incident has been resolved. As the X API remains unstable, we will notify you here if the same issue occurs again. We apologize for any inconvenience.

1. 11 sierpnia 2026 01:10 UTCinvestigating

   Thank you for using SocialDog. Analysis functions, may be affected. We apologize for any inconvenience. 【Affected Period】 2026/8/11 9:00 (JST) – Ongoing 【Issue Details】 Analysis functions, may be affected. 【Cause】 The root cause of this issue is currently under investigation. 【Current Status】 We will provide further updates on this page as soon as more information becomes available. Thank you for your patience and understanding while we work to resolve this.

2. 11 sierpnia 2026 07:37 UTCmonitoring

   The incident is now resolved. We are currently monitoring the status of the incident. We apologize for any inconvenience.

3. 11 sierpnia 2026 11:57 UTCmonitoring

   Thank you for using SocialDog. We are currently experiencing a system issue where some users are unable to view "Conversation trends." We sincerely apologize for any disruption and inconvenience this may cause to your workflow. 【Issue Details】 Users may experience difficulties loading or viewing data within the "Conversation trends" feature. 【Cause】 This issue was caused by temporary errors and instability in our system's communication with the X API. Thank you for your patience and understanding while we work to resolve this.

4. 12 sierpnia 2026 00:58 UTCresolved

   Thank you for using SocialDog. We are pleased to inform you that the issue we reported earlier has been completely resolved. All affected features are now functioning normally. We sincerely apologize for any disruption and inconvenience this may have caused to your workflow. 【Affected Period】 2026/8/11 17:20 – 2026/8/12 9:00 (JST) 【Affected Features】 During the incident, users may have experienced difficulties with the following features: ・Viewing "Conversation trends" 【Cause】 This issue was caused by temporary errors and instability in our system's communication with the X API. We have confirmed that the API connection has fully recovered, and all SocialDog services are operating normally again. Thank you for your patience and understanding. We appreciate your continued support of SocialDog.

1. 10 sierpnia 2026 08:11 UTCinvestigating

   Thank you for using SocialDog. We are currently experiencing a system issue where some users are unable to view "Conversation trends." We sincerely apologize for any disruption and inconvenience this may cause to your workflow. 【Affected Period】 2026/8/10 16:36 (JST) – Ongoing 【Issue Details】 Users may experience difficulties loading or viewing data within the "Conversation trends" feature. 【Cause】 The root cause of this issue is currently under investigation. 【Current Status】 We will provide further updates on this page as soon as more information becomes available. Thank you for your patience and understanding while we work to resolve this.

2. 10 sierpnia 2026 09:20 UTCresolved

   Thank you for using SocialDog. We are pleased to inform you that the issue we reported earlier has been completely resolved. All affected features are now functioning normally. We sincerely apologize for any disruption and inconvenience this may have caused to your workflow. 【Affected Period】 2026/8/10 16:36 – 18:11 (JST) 【Affected Features】 During the incident, users may have experienced difficulties with the following features: ・Viewing "Conversation trends" ・Setting up and acquiring data for "Keyword Monitors" 【Cause】 This issue was caused by temporary errors and instability in our system's communication with the X API. We have confirmed that the API connection has fully recovered, and all SocialDog services are operating normally again. Thank you for your patience and understanding. We appreciate your continued support of SocialDog.

1. 4 sierpnia 2026 13:50 UTCinvestigating

   Thank you for using SocialDog. We are currently experiencing an issue where engagement data for posts cannot be retrieved. We are investigating the cause and will provide an update as soon as we have more details. We sincerely apologize for the inconvenience.

2. 4 sierpnia 2026 14:32 UTCidentified

   The issue we previously reported, where engagement data for posts could not be retrieved, has now been resolved. 【Affected period】 2026/8/4 22:22 - 2026/8/4 23:11 (JST) 【Details】 During the period above, engagement data for posts was not being retrieved. 【Cause】 The process had been stopped due to the impact of maintenance carried out on August 3. 【Current status】 The feature has been restored. We are working to recover the data that was not collected during the affected period, and expect this to be completed by the end of tomorrow. We sincerely apologize for the inconvenience caused.

3. 5 sierpnia 2026 08:37 UTCresolved

   Thank you for using SocialDog. Following our previous updates regarding the issue where post reaction data could not be fetched, we would like to inform you that the recovery of the missing data during the affected period has been fully completed. All systems and features are now operating normally. We sincerely apologize for any inconvenience and disruption this incident may have caused you. We will continue to work on preventing future occurrences. Thank you for your continued support of SocialDog.

1. 4 sierpnia 2026 03:26 UTCresolved

   Dziękuję za użycie Social Dog. Po konserwacji przeprowadzonej w dniu 3 sierpnia 2026 r. niektóre cechy nie działały zgodnie z oczekiwaniami. Sprawa została rozwiązana. Serdecznie przepraszamy za wszelkie niedogodności, jakie mogło to spowodować. Okres incydentu 2026 / 8 / 3 23: 00 - 2026 / 8 / 4 11: 40 (JST) Agresywne funkcje RRSS Auto post RRRR Zaangażowanie pocztowe Co może trzeba zrobić RRSS Auto post: Artykuły, które nie zostały opublikowane nie zostaną automatycznie opublikowane. W razie potrzeby należy je wysłać ręcznie. wpis: brakujące dane zostaną automatycznie odzyskane z upływem czasu. Nie jest wymagane żadne działanie z twojej strony. Bieżący status Wszystkie funkcje działają normalnie. Zrobimy wszystko, co w naszej mocy, aby zapobiec podobnym problemom.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 8 lipca 2026 01:43 UTCinvestigating

   Xev, Xev, Xev. Funkcje analizy, może być naruszone. Przepraszamy za wszelkie niedogodności.

2. 8 lipca 2026 02:06 UTCinvestigating

   Xev, Xev, Xev. Funkcje analizy, może być naruszone. Przepraszamy za wszelkie niedogodności. Okres incydentu 2026 / 7 / 8 6: 00 Agresywne funkcje - Funkcje analizy / Powód W toku dochodzenia

3. 8 lipca 2026 07:52 UTCmonitoring

   Wprowadzono rozwiązanie i monitorujemy wyniki.

4. 8 lipca 2026 13:47 UTCresolved

   Ten incydent został rozwiązany.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 30 czerwca 2026 04:03 UTCinvestigating

   There is a system failure of the X API. Analysis functions, may be affected. We apologize for any inconvenience.

2. 30 czerwca 2026 05:33 UTCmonitoring

   The incident is now resolved. We are currently monitoring the status of the incident. We apologize for any inconvenience.

3. 30 czerwca 2026 05:56 UTCresolved

   The incident is now resolved. We apologize for any inconvenience.

1. 24 kwietnia 2026 04:27 UTCinvestigating

   We are currently experiencing technical difficulties with our Instagram media posting features. We sincerely apologize for any inconvenience this may cause our users. Image and video posts may fail to be published. 【Incident Period】 2026/4/24 5:00 (JST) 〜 Present 【Affected Features】 - Scheduled posts 【Cause】 Under investigation

2. 25 kwietnia 2026 00:12 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 25 kwietnia 2026 07:21 UTCresolved

   This incident has been resolved.

1. 24 marca 2026 02:29 UTCinvestigating

   There is a system failure of the X API. Analysis functions, may be affected. We apologize for any inconvenience.

2. 24 marca 2026 09:12 UTCresolved

   The incident is now resolved. We apologize for any inconvenience.

1. 9 lutego 2026 12:08 UTCresolved

   We are pleased to inform you that the technical difficulties preventing users from logging into our mobile apps have been resolved. We sincerely apologize for any inconvenience this may have caused. 【Incident Period】 2026/2/9 14:23 - 2026/2/9 21:04 (JST) 【Scope】 ・Mobile Applications (iOS / Android) 【Affected Features】 ・App login 【Status】 The issue has been resolved.

1. 29 stycznia 2026 03:56 UTCinvestigating

   We are currently experiencing technical difficulties with our X (Twitter) posting features. We sincerely apologize for any inconvenience this may cause our users. Posts may fail to be published. 【Incident Period】 2026/1/29 7:55 (JST) 〜Present 【Affected Features】 ・Scheduled posts ・RSS Auto-posting 【Cause】 Under investigation

2. 29 stycznia 2026 04:42 UTCidentified

   We have confirmed that posting failures are primarily occurring when media (images or videos) are attached. This issue is caused by a disruption in the X API. For more details regarding the X API status, please refer to the following link. https://docs.x.com/incidents

3. 29 stycznia 2026 05:18 UTCmonitoring

   The incident is now resolved. We are currently monitoring the status of the incident. We apologize for any inconvenience.

4. 29 stycznia 2026 06:05 UTCresolved

   The incident is now resolved. We apologize for any inconvenience.

1. 21 stycznia 2026 02:26 UTCinvestigating

   Thank you for using SocialDog. We are currently experiencing an issue with some SocialDog features due to an external system (data infrastructure) failure. During this time, the following features may be temporarily unavailable or may not display data correctly. 【Affected Features】 ・Post Engagement ・Post Performance ・Competitor Analysis ・Campaigns 【Occurrence Period】 2026/01/21 10:45 (JST) - Ongoing 【Cause and Status】 We have confirmed that a temporary failure has occurred in the external infrastructure used by our system. We are currently investigating the issue for resolution. We apologize for any inconvenience this may cause and appreciate your understanding and cooperation.

2. 21 stycznia 2026 05:11 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 21 stycznia 2026 07:48 UTCresolved

   The incident is now resolved. We apologize for any inconvenience.

1. 20 stycznia 2026 11:57 UTCidentified

   We are currently experiencing an issue where keyword searches via the X API are not functioning correctly. We have confirmed that the "Keyword Monitor" and "Conversation trends (Beta)" features may fail to operate when certain search keywords are included. We are currently investigating this issue. Reference: https://devcommunity.x.com/t/im-getting-a-4xx-error-calling-the-search-api-with-is-retweet/254995 We apologize for any inconvenience.

2. 20 stycznia 2026 16:00 UTCresolved

   The incident is now resolved. We apologize for any inconvenience.

1. 16 stycznia 2026 15:37 UTCidentified

   There is a system failure of the X API. All functions, including posting and analysis functions, may be affected. We apologize for any inconvenience.

2. 17 stycznia 2026 00:56 UTCresolved

   The incident is now resolved. We apologize for any inconvenience.

1. 18 listopada 2025 13:31 UTCidentified

   There is a system failure of the X API. All functions, including posting and analysis functions, may be affected. We apologize for any inconvenience.

2. 18 listopada 2025 15:24 UTCresolved

   The incident is now resolved. We apologize for any inconvenience.

1. 31 października 2025 08:56 UTCinvestigating

   We are currently experiencing an issue where insights for some Instagram posts cannot be retrieved properly. We are investigating, but the issue appears to be related to Instagram API service availability. We apologize for any inconvenience.

2. 3 listopada 2025 02:10 UTCmonitoring

   The incident is now resolved. We are currently monitoring the status of the incident. We apologize for any inconvenience.

3. 3 listopada 2025 02:56 UTCresolved

   The incident is now resolved. We apologize for any inconvenience.

1. 1 lipca 2025 08:49 UTCinvestigating

   There is a system failure of the X API. All functions, including posting and analysis functions, may be affected. We apologize for any inconvenience.

2. 1 lipca 2025 15:53 UTCmonitoring

   The incident is now resolved. We are currently monitoring the status of the incident. We apologize for any inconvenience.

3. 1 lipca 2025 16:50 UTCresolved

   The incident is now resolved. We apologize for any inconvenience.