Historial de interrupciones de Socialdog

1. 25 de septiembre de 2026 a las 13:10 UTCresolved

   Gracias por usar SocialDog. Deseamos informarle de que se ha resuelto la cuestión que ocurrió el 25 de septiembre. Todas las características están funcionando normalmente. Sinceramente nos disculpamos por cualquier perturbación e inconveniente que esto pueda haber causado a su flujo de trabajo. Período Afectado 2026/9/25 21:22 – 21:44 (JST) Características modificadas Durante el incidente, algunos usuarios pueden haber experimentado errores al ver páginas o realizar acciones en SocialDog (Web y app). Causa Este problema fue causado por una comunicación de red temporalmente inestable entre algunos de nuestros servidores y nuestros sistemas internos. La comunicación se ha recuperado, y hemos confirmado que todos los servicios de SocialDog funcionan normalmente de nuevo. ◆Medidas de futuro Estamos revisando nuestra configuración del sistema para evitar que ocurran problemas similares en el futuro. Gracias por su paciencia y comprensión. Agradecemos su apoyo continuo a SocialDog.

Traducido automáticamente desde la actualización oficial del incidente.

1. 15 de agosto de 2026 a las 0: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 de agosto de 2026 a las 5:38 UTCmonitoring

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

3. 17 de agosto de 2026 a las 13:21 UTCresolved

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

1. 13 de agosto de 2026 a las 6: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 de agosto de 2026 a las 5: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 de agosto de 2026 a las 1: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 de agosto de 2026 a las 7:37 UTCmonitoring

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

3. 11 de agosto de 2026 a las 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 de agosto de 2026 a las 0: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 de agosto de 2026 a las 8: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 de agosto de 2026 a las 9: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 de agosto de 2026 a las 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 de agosto de 2026 a las 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 de agosto de 2026 a las 8: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 de agosto de 2026 a las 3:26 UTCresolved

   Gracias por usar SocialDog. Tras el mantenimiento realizado el 3 de agosto de 2026, algunas características no funcionaban como se esperaba. La cuestión ya se ha resuelto. Sinceramente nos disculpamos por cualquier inconveniente que esto pueda haber causado. ∙ Período de Incidencia 2026/8/3 23:00 - 2026/8/4 11:40 (JST) Características modificadas ・RSS Auto post :: Compromiso de puestos Lo que usted puede necesitar hacer ・RSS Auto post: Los artículos que no fueron publicados no serán publicados automáticamente. Por favor envíelos manualmente si es necesario. :: Compromiso de publicación: Los datos perdidos se recuperarán automáticamente con el tiempo. No se requiere acción por su parte. Situación actual Todas las características funcionan normalmente. Haremos todo lo posible para evitar que ocurran problemas similares.

Traducido automáticamente desde la actualización oficial del incidente.

1. 8 de julio de 2026 a las 1:43 UTCinvestigating

   X Inteligente. Las funciones de análisis pueden verse afectadas. Nos disculpamos por cualquier inconveniente.

2. 8 de julio de 2026 a las 2:06 UTCinvestigating

   X Inteligente. Las funciones de análisis pueden verse afectadas. Nos disculpamos por cualquier inconveniente. ∙ Período de Incidencia 2026/7/8 6:00 (JST) Características modificadas - Funciones de análisis - XECUCIÓN Causa Under investigation

3. 8 de julio de 2026 a las 7:52 UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

4. 8 de julio de 2026 a las 13:47 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 30 de junio de 2026 a las 4:03 UTCinvestigating

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

2. 30 de junio de 2026 a las 5:33 UTCmonitoring

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

3. 30 de junio de 2026 a las 5:56 UTCresolved

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

1. 24 de abril de 2026 a las 4: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 de abril de 2026 a las 0:12 UTCmonitoring

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

3. 25 de abril de 2026 a las 7:21 UTCresolved

   This incident has been resolved.

1. 24 de marzo de 2026 a las 2:29 UTCinvestigating

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

2. 24 de marzo de 2026 a las 9:12 UTCresolved

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

1. 9 de febrero de 2026 a las 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 de enero de 2026 a las 3: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 de enero de 2026 a las 4: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 de enero de 2026 a las 5:18 UTCmonitoring

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

4. 29 de enero de 2026 a las 6:05 UTCresolved

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

1. 21 de enero de 2026 a las 2: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 de enero de 2026 a las 5:11 UTCmonitoring

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

3. 21 de enero de 2026 a las 7:48 UTCresolved

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

1. 20 de enero de 2026 a las 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 de enero de 2026 a las 16:00 UTCresolved

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

1. 16 de enero de 2026 a las 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 de enero de 2026 a las 0:56 UTCresolved

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

1. 18 de noviembre de 2025 a las 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 de noviembre de 2025 a las 15:24 UTCresolved

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

1. 31 de octubre de 2025 a las 8: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 de noviembre de 2025 a las 2:10 UTCmonitoring

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

3. 3 de noviembre de 2025 a las 2:56 UTCresolved

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

1. 1 de julio de 2025 a las 8: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 de julio de 2025 a las 15:53 UTCmonitoring

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

3. 1 de julio de 2025 a las 16:50 UTCresolved

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

1. 26 de junio de 2025 a las 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 de junio de 2025 a las 3:38 UTCmonitoring

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

3. 27 de junio de 2025 a las 5:20 UTCresolved

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