Histórico de interrupções do Socialdog

1. 15 Eost 2026 da 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 Eost 2026 da 05:38 UTCmonitoring

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

3. 17 Eost 2026 da 13:21 UTCresolved

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

1. 13 Eost 2026 da 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 Eost 2026 da 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 Eost 2026 da 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 Eost 2026 da 07:37 UTCmonitoring

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

3. 11 Eost 2026 da 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 Eost 2026 da 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 Eost 2026 da 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 Eost 2026 da 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.

Traduzido automaticamente da atualização oficial do incidente.

1. 4 Eost 2026 da 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 Eost 2026 da 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 Eost 2026 da 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 Eost 2026 da 03:26 UTCresolved

   Obrigado por usar SocialDog. Após a manutenção realizada em 3 de agosto de 2026, algumas características não funcionaram como esperado. A questão está agora resolvida. Pedimos sinceramente desculpas por qualquer inconveniente que isso possa ter causado. Período Incidente 2026/8/3 23:00 - 2026/8/4 11:40 (JST) Características afetadas .RSS Auto post Após o noivado O que você pode precisar fazer Postagem automática: Os artigos que não foram publicados não serão publicados automaticamente. Por favor, publique-os manualmente, se necessário. □Engajamento pós-post: os dados em falta serão recuperados automaticamente ao longo do tempo. Nenhuma ação é necessária de sua parte. Estado atual Todos os recursos estão funcionando normalmente. Faremos o possível para evitar que questões semelhantes ocorram.

Traduzido automaticamente da atualização oficial do incidente.

1. 8 Gouere 2026 da 01:43 UTCinvestigating

   X! Funções de análise, podem ser afetadas. Pedimos desculpa por qualquer inconveniente.

2. 8 Gouere 2026 da 02:06 UTCinvestigating

   X! Funções de análise, podem ser afetadas. Pedimos desculpa por qualquer inconveniente. Período Incidente 2026/7/8 6:00 (JST) Características afetadas - Funções de análise - X! Causa Sob investigação

3. 8 Gouere 2026 da 07:52 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

4. 8 Gouere 2026 da 13:47 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 30 Mezheven 2026 da 04:03 UTCinvestigating

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

2. 30 Mezheven 2026 da 05:33 UTCmonitoring

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

3. 30 Mezheven 2026 da 05:56 UTCresolved

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

1. 24 Ebrel 2026 da 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 Ebrel 2026 da 00:12 UTCmonitoring

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

3. 25 Ebrel 2026 da 07:21 UTCresolved

   This incident has been resolved.

1. 24 Meurzh 2026 da 02:29 UTCinvestigating

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

2. 24 Meurzh 2026 da 09:12 UTCresolved

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

1. 9 Cʼhwevrer 2026 da 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 Genver 2026 da 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 Genver 2026 da 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 Genver 2026 da 05:18 UTCmonitoring

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

4. 29 Genver 2026 da 06:05 UTCresolved

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

1. 21 Genver 2026 da 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 Genver 2026 da 05:11 UTCmonitoring

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

3. 21 Genver 2026 da 07:48 UTCresolved

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

1. 20 Genver 2026 da 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 Genver 2026 da 16:00 UTCresolved

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

1. 16 Genver 2026 da 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 Genver 2026 da 00:56 UTCresolved

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

1. 18 Du 2025 da 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 Du 2025 da 15:24 UTCresolved

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

1. 31 Here 2025 da 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 Du 2025 da 02:10 UTCmonitoring

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

3. 3 Du 2025 da 02:56 UTCresolved

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

1. 1 Gouere 2025 da 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 Gouere 2025 da 15:53 UTCmonitoring

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

3. 1 Gouere 2025 da 16:50 UTCresolved

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

1. 26 Mezheven 2025 da 17:38 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. 27 Mezheven 2025 da 03:38 UTCmonitoring

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

3. 27 Mezheven 2025 da 05:20 UTCresolved

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

1. 28 Mae 2025 da 23:19 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. We are closely monitoring information from X. https://docs.x.com/incidents We are currently investigating.

2. 29 Mae 2025 da 08:53 UTCmonitoring

   We are closely monitoring information from X. https://docs.x.com/incidents

3. 29 Mae 2025 da 09:52 UTCresolved

   The incident is now resolved. We apologize for any inconvenience. We are closely monitoring information from X. https://docs.x.com/incidents