Pipedream 中断历史

1. 2026年10月5日 UTC 17:58investigating

   我们正在调查一个问题 我们的Anthropic账户 权力字符串.com聊天。 所有管梦.com的服务和工作流程都应不受影响.

2. 2026年10月5日 UTC 18:32resolved

   string.com聊天正常,服务恢复.

自动翻译自官方事件更新。

1. 2026年7月29日 UTC 00:06identified

   这一问题已经确定,一个解决办法正在实施之中.

2. 2026年7月29日 UTC 00:22monitoring

   一项措施已经执行,我们正在监测结果.

3. 2026年7月29日 UTC 00:34resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年7月28日 UTC 23:40investigating

   我们目前正在调查这一问题.

2. 2026年7月28日 UTC 23:53monitoring

   一项措施已经执行,我们正在监测结果.

3. 2026年7月28日 UTC 23:59resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年7月14日 UTC 17:45investigating

   我们目前正在调查这一问题.

2. 2026年7月14日 UTC 18:21monitoring

   一项措施已经执行,我们正在监测结果.

3. 2026年7月14日 UTC 18:33resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年5月1日 UTC 03:53investigating

   We've disabled editing / building new Python code steps in the Pipedream UI due to a downstream AWS issue. We'll update this as soon as we hear more from AWS.

2. 2026年5月3日 UTC 19:15resolved

   This incident has been resolved.

1. 2026年4月24日 UTC 02:07investigating

   We are currently investigating degraded performance for event sources and workflows.

2. 2026年4月24日 UTC 02:47resolved

   This incident has been resolved.

1. 2026年4月9日 UTC 17:47resolved

   This incident has been resolved.

1. 2026年2月24日 UTC 00:39investigating

   We are currently investigating this issue.

2. 2026年2月24日 UTC 00:45investigating

   We are continuing to investigate this issue.

3. 2026年2月24日 UTC 00:45resolved

   This incident has been resolved.

1. 2026年2月9日 UTC 12:21investigating

   We are currently investigating this issue.

2. 2026年2月9日 UTC 13:08identified

   The issue has been identified and a fix is being implemented.

3. 2026年2月9日 UTC 13:14monitoring

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

4. 2026年2月9日 UTC 17:35resolved

   This incident has been resolved.

1. 2026年2月2日 UTC 16:53identified

   We have identified that the Pipedream REST API is slightly degraded. We are currently working on a fix.

2. 2026年2月2日 UTC 23:08resolved

   We have deployed a fix and are monitoring

1. 2026年1月12日 UTC 23:31investigating

   We are currently investigating and will follow up once we identify the issue.

2. 2026年1月12日 UTC 23:47identified

   We have identified the cause of the issues and are working on mitigating it.

3. 2026年1月13日 UTC 00:50monitoring

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

4. 2026年1月13日 UTC 00:51resolved

   This incident has been resolved.

1. 2025年11月20日 UTC 02:03investigating

   We are currently investigating this issue.

2. 2025年11月20日 UTC 02:03investigating

   We are investigating instability with the Front End

3. 2025年11月20日 UTC 02:17resolved

   Our front end services experienced unusual request patterns which led to degraded performance. We have updated our systems to address the issue and performance has returned to normal levels.

1. 2025年11月4日 UTC 15:53investigating

   We are currently investigating this issue.

2. 2025年11月4日 UTC 16:30monitoring

   Things have stabilized and we're continuing to monitor

3. 2025年11月4日 UTC 19:14resolved

   root cause identified, Short term Mitigation efforts have been successful. Long term Mitigation solution has been identified and will be implemented as soon as the fix has passed our QA processes.

1. 2025年10月20日 UTC 13:10investigating

   We are seeing some HTTP triggers returning a 503 status and are investigating.

2. 2025年10月20日 UTC 14:00identified

   These errors are due to our upstream provider (AWS) still having an ongoing outage.

3. 2025年10月20日 UTC 16:15identified

   We are continuing to work on a fix for this issue.

4. 2025年10月20日 UTC 16:24identified

   Multiple services are experiencing a service disruption as a result of a downstream provider (AWS). We are closely monitoring the status.

5. 2025年10月20日 UTC 20:05identified

   Some services are starting to come back online, some of the queued events are being processed.

6. 2025年10月20日 UTC 21:51monitoring

   Event queues have caught up. We are continuing to monitor the platform.

7. 2025年10月21日 UTC 01:26resolved

   This incident has been resolved.

1. 2025年9月16日 UTC 17:56investigating

   We are currently investigating this issue.

2. 2025年9月16日 UTC 18:15monitoring

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

3. 2025年9月16日 UTC 19:09monitoring

   We are continuing to monitor for any further issues.

4. 2025年9月16日 UTC 19:09resolved

   This incident has been resolved.

1. 2025年9月2日 UTC 16:38investigating

   We are currently investigating this issue.

2. 2025年9月2日 UTC 16:40investigating

   We are continuing to investigate this issue.

3. 2025年9月2日 UTC 16:59monitoring

   Service has improved and is back to normal. We are monitoring the performance.

4. 2025年9月2日 UTC 18:32resolved

   This incident has been resolved.

1. 2025年8月22日 UTC 20:23investigating

   The Discord integration isn't working properly. We are looking into it.

2. 2025年8月22日 UTC 20:40monitoring

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

3. 2025年8月22日 UTC 20:51resolved

   This incident has been resolved.

1. 2025年8月21日 UTC 17:23investigating

   We are currently investigating this issue.

2. 2025年8月21日 UTC 18:53identified

   We have identified a latency issue with one of our downstream partner providers. We are currently evaluating ways to mitigate the effect.

3. 2025年8月21日 UTC 19:40resolved

   This incident has been resolved.

1. 2025年8月15日 UTC 23:40investigating

   We are currently investigating this issue.

2. 2025年8月16日 UTC 00:29monitoring

   Webhooks have caught up and we are monitoring.

3. 2025年8月16日 UTC 00:51resolved

   This incident has been resolved.

1. 2025年8月11日 UTC 15:43investigating

   We are currently investigating this issue.

2. 2025年8月11日 UTC 16:57resolved

   This incident has been resolved.