Socialdog の障害履歴

1. 2026年10月28日 2:47 UTCresolved

   SocialDogをご利用いただき、誠にありがとうございます。 最近のシステム更新後に発生した問題が解決されたことをお知らせします。 すべての機能が正常に機能しています。 大変ご迷惑をおかけいたしますが、ご迷惑をおかけいたしますが、ご迷惑をおかけいたしますが、何卒宜しくお願い申し上げます。 【感染期間】 2026/10/28 11:22 - 11:37 (JST) 【特徴】 インシデント中には、ページを表示したり、SocialDogアプリでアクションを実行するときに、一部のユーザーはエラーが発生することがあります。 【原因】 この問題は、最近のシステム更新に含まれているシステム設定の変更によって引き起こされました。 設定を修正し、すべてのSocialDogサービスは正常に動作していることを確認します。 【今後の取り組み】 今後同様の問題が起きるのを防ぐため、システム構成を検討しています。 誠に有難うございます。 引き続き、ソーシャルドッグのご支援を賜りますようお願い申し上げます.

公式のインシデント更新を自動翻訳しています。

1. 2026年9月25日 13:10 UTCresolved

   SocialDogをご利用いただき、誠にありがとうございます。 9月25日に発生した問題が解決されたことをお知らせします。 すべての機能が正常に機能しています。 大変ご迷惑をおかけいたしますが、ご迷惑をおかけいたしますが、ご迷惑をおかけいたしますが、何卒宜しくお願い申し上げます。 【感染期間】 2026/9/25 21:22 - 21:44 (日本) 【特徴】 インシデント中に、ページを表示したり、SocialDog(Webとアプリ)でアクションを実行するときに、一部のユーザーはエラーが発生することがあります。 【原因】 この問題は、一部のサーバーと内部システム間で一時的に不安定なネットワーク通信によって引き起こされました。 コミュニケーションが回復し、すべてのSocialDogサービスは正常に動作していることが確認されています。 【今後の取り組み】 今後同様の問題が起きるのを防ぐため、システム構成を検討しています。 誠に有難うございます。 引き続き、ソーシャルドッグのご支援を賜りますようお願い申し上げます.

公式のインシデント更新を自動翻訳しています。

1. 2026年8月15日 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. 2026年8月17日 5:38 UTCmonitoring

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

3. 2026年8月17日 13:21 UTCresolved

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

1. 2026年8月13日 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. 2026年8月14日 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. 2026年8月11日 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. 2026年8月11日 7:37 UTCmonitoring

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

3. 2026年8月11日 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. 2026年8月12日 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. 2026年8月10日 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. 2026年8月10日 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. 2026年8月4日 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. 2026年8月4日 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. 2026年8月5日 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. 2026年8月4日 3:26 UTCresolved

   SocialDogをご利用いただき、誠にありがとうございます。 2026年8月3日(水)メンテナンス終了後、一部機能が期待通りに機能しなかった。 問題は解決しました。 大変ご迷惑をおかけいたしますが、何卒ご了承くださいますようお願い申し上げます。 【開催期間】 2026/8/3 23:00 - 2026/8/4 11:40 (JST) 【特徴】 ・RSSオートポスト ・ポストエンゲージメント 【お求めのお願い】 ・RSSオートポスト:公開されていない記事が自動的に投稿されません。 必要に応じて手動で投稿してください。 ・投稿のエンゲージメント:データの欠損は、自動的に時間をかけて取得されます。 あなたの部分にアクションは必要ありません。 【現在の状況】 すべての機能は正常に動作しています。 同様の問題が起きるのを防ぐため、最大限に取り組みます.

公式のインシデント更新を自動翻訳しています。

1. 2026年7月8日 1:43 UTCinvestigating

   Xの投稿は、 分析機能、影響を受ける可能性があります。 大変申し訳ございません.

2. 2026年7月8日 2:06 UTCinvestigating

   Xの投稿は、 分析機能、影響を受ける可能性があります。 大変申し訳ございません。 【開催期間】 2026/7/8 6:00 (JST) 〜 現在 【特徴】 - 解析機能 - Xの投稿一覧 【原因】 調査中

3. 2026年7月8日 7:52 UTCmonitoring

   修正を実装し、結果を監視しています.

4. 2026年7月8日 13:47 UTCresolved

   この事件は解決しました.

公式のインシデント更新を自動翻訳しています。

1. 2026年6月30日 4:03 UTCinvestigating

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

2. 2026年6月30日 5:33 UTCmonitoring

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

3. 2026年6月30日 5:56 UTCresolved

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

1. 2026年4月24日 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. 2026年4月25日 0:12 UTCmonitoring

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

3. 2026年4月25日 7:21 UTCresolved

   This incident has been resolved.

1. 2026年3月24日 2:29 UTCinvestigating

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

2. 2026年3月24日 9:12 UTCresolved

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

1. 2026年2月9日 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. 2026年1月29日 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. 2026年1月29日 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. 2026年1月29日 5:18 UTCmonitoring

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

4. 2026年1月29日 6:05 UTCresolved

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

1. 2026年1月21日 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. 2026年1月21日 5:11 UTCmonitoring

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

3. 2026年1月21日 7:48 UTCresolved

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

1. 2026年1月20日 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. 2026年1月20日 16:00 UTCresolved

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

1. 2026年1月16日 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. 2026年1月17日 0:56 UTCresolved

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

1. 2025年11月18日 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. 2025年11月18日 15:24 UTCresolved

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

1. 2025年10月31日 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. 2025年11月3日 2:10 UTCmonitoring

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

3. 2025年11月3日 2:56 UTCresolved

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

1. 2025年7月1日 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. 2025年7月1日 15:53 UTCmonitoring

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

3. 2025年7月1日 16:50 UTCresolved

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