incident.io Status 中断历史

1. 2026年10月2日 UTC 23:47resolved

   状况:已解决 这一事件已经得到解决。 通过Slack的登录再次正常运行,无需采取进一步行动. 受影响的组件 Slack app (操作)

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

1. 2026年8月20日 UTC 16:31resolved

   现状:已解决的紧急情况现已恢复正常。 在协调世界时下午1:00至15:08之间,一些微软API的延迟时间有所增加. Microsoft Teams中的信息以更耐用的方式发送。 我们的仪表板和移动应用程序没有受到影响。 受影响的组件 Microsoft Teams app(业务)

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

1. 2026年8月18日 UTC 11:37resolved

   状况:已解决 我们现在回滚 上市警报又正常了 警报摄取、处理和呼气(操作)

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

1. 2026年8月3日 UTC 17:04resolved

   状态: 已解决 Opsgenie webhook 发送在 17: 48 左右恢复正常 BST 受影响的组件 Opsgenie(操作)

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

1. 2026年8月1日 UTC 02:45resolved

   状态:在协调世界时00:00至02:44之间解决了,一些AI特性返回了更高的出错率. 我们现在看到完全康复。 受影响的组件 Datadog(业务) 聚合(业务) Zapier(业务) 推取通知(业务) 快捷(业务) Okta(业务) GitHub(业务) Google日历(业务) 电子邮件(业务) Opslevel(业务) Asana(业务) 哨兵(业务) Splunk(业务) 移动应用(业务) 透视(业务) 代理(业务) Azure DevOps(业务) Cortex(业务) 放大(业务) Dashboard(业务) SAML登录(业务) Pager Duty(业务) 在线(业务) 谷歌汇合(业务) 禅台(业务) API(业务) Vanta(业务) 移动电话(业务) 微软团队应用(业务) 状态页面(业务) Jira(业务) Atlassian 状况页面(业务) Google Doc(业务) 警报摄取、处理和呼呼(操作) 点击(操作) Opsgenie(操作) 短消息(操作) Slack(操作)

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

1. 2026年7月16日 UTC 08:32investigating

   我们知道一些客户在使用SAML时 遇到的问题,我们正在调查,不久将提供最新情况.

2. 2026年7月16日 UTC 09:12identified

   这个问题还在继续,我们正在着手解决。 所有其他功能都不受影响. 移动应用程序和仪表板上的现有会议不受影响,继续正常使用。 我们将在接下来的30分钟内发布下一次更新.

3. 2026年7月16日 UTC 09:27monitoring

   SAML的登录系统目前正在与更高的延迟性合作。 我们会继续监视直到完全恢复 所有其他功能都未受影响.

4. 2026年7月16日 UTC 10:16monitoring

   我们继续看到SAML登录错误和延迟度上升 所有其他功能都未受影响.

5. 2026年7月16日 UTC 10:29monitoring

   SAML 登录器现在正常运行 。 我们将继续监视任何进一步的问题.

6. 2026年7月16日 UTC 10:54resolved

   SAML登录继续正常进行.

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

1. 2026年6月23日 UTC 19:45investigating

   我们已查明了影响我们仪表板上一些要求的加急和超时。 问题看来是暂时的,我们建议加以澄清。 我们正在继续调查.

2. 2026年6月23日 UTC 19:55monitoring

   延迟和出错率已恢复正常。 我们继续监视任何进一步的问题.

3. 2026年6月23日 UTC 20:25resolved

   在协调世界时19:31-30至19:34:30之间,我们仪表板上的一些请求击中了更高的延迟和连接误差. 其原因是Google云平台上的上游网络事件. 错误是短暂的,通常会刷新。 机率和误差率恢复正常,我们注意事情。 我们将张贴一个死后 覆盖全部撞击.

4. 2026年6月25日 UTC 11:51resolved

   在协调世界时19:31:30至19:34:30之间,我们观察到延迟性有限地增加以及少量仪表板出错. 这影响到我们仪表板的0比03%的通话 我们内部的合成监测检测到了这一点。 造成这些高误差的原因是当时GCP内部的网络问题. 我们的日志显示我们的GCP负载平衡器没有转发成功响应,以及试图到达外部服务时的网络超时也证实了这一点. 影响仅限于少数用户,通过刷新仪表板解决.

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

1. 2026年5月27日 UTC 22:42identified

   我们发现错误率上升 与我们的Slack整合。 目前我们正调查这如何影响我们的平台.

2. 2026年5月27日 UTC 23:02identified

   斯拉克已经承认了他们那边的事件. 您可以查看他们的状态页面[此处](https://slack-status.com/2026-05/46d9d5d41fbedd9f).

3. 2026年5月27日 UTC 23:21monitoring

   Slack操作出错率和延迟度已恢复正常,整合恢复. 您可以在Slack的状态页面[这里]上查询最新消息(https://slack-status.com/2026-05/46d9d5d41fbedd9f).

4. 2026年5月28日 UTC 00:19monitoring

   我们继续监视Slack继续恢复, 不再看到Slack的应用程序受到任何直接影响 您可以在Slack的状态页面上查询最新消息[这里](https://slack-status.com/2026-05/46d9d5d41fbedd9f "这里").

5. 2026年5月28日 UTC 02:31monitoring

   我们正在继续监测Slack恢复情况。 我们没有看到任何直接影响 我们的Slack应用。 您可以在Slack的状态页面上查询最新消息[此处](https://slack-status.com/2026-05/46d9d5d41fbedd9f "这里").

6. 2026年5月28日 UTC 06:29resolved

   斯拉克证实他们的服务已基本恢复到业务水平. 自协调世界时昨天~23:20以来,我们没有看到任何对Slack应用的直接影响. 在Slack的状态页面[这里](https://slack-status.com/2026-05/46d9d5d41fbedd9f)上.

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

1. 2026年5月14日 UTC 14:08identified

   We have identified increased error rates with our Slack integration. We are currently investigating how this is impacting our platform - this seems to be an issue on the Slack side, particularly around channel creation.

2. 2026年5月14日 UTC 14:12identified

   We've confirmed the issue is relating to errors being returned by Slack. This is affecting a number of features of our integration, including: • Creating incident channels • Sending messages • Syncing Slack user groups Our web dashboard continues to be available and Scribe is unaffected.

3. 2026年5月14日 UTC 14:41monitoring

   Slack have acknowledged the incident on their side. You can follow their status page [here](https://slack-status.com/2026-05/fe557ca05fdb64fa).

4. 2026年5月14日 UTC 15:15monitoring

   We're continuing to monitor the situation - Slack have posted an update on their status page to confirm that they're working on it.

5. 2026年5月14日 UTC 15:45resolved

   The issue has been resolved on Slack's side and we've confirmed that things look normal on our side too.

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

1. 2026年5月7日 UTC 07:37resolved

   The website is now up and working as normal.

2. 2026年5月7日 UTC 07:37identified

   The web dashboard is unavailable due to a JavaScript deployment issue.

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

1. 2026年4月27日 UTC 23:58monitoring

   我们发现在接收Opsgenie的网络呼号时, 我们的系统正在正常运行,一旦到达就处理警报;这个问题似乎在Opsgenie的一边。 并分享最新消息.

2. 2026年4月28日 UTC 00:14resolved

   Webhooks 似乎再次正常到达, 所以你不应该再看到任何延迟.

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

1. 2026年4月9日 UTC 07:33identified

   We have identified increased error rates with our Atlassian Statuspage integration. Atlassian have published this to their status page [here](https://metastatuspage.com/incidents/94fwk40f4z15).

2. 2026年4月9日 UTC 07:55resolved

   Error rates have returned to normal levels.

1. 2026年3月24日 UTC 16:30identified

   We have identified increased error rates coming from Microsoft Teams. We are currently investigating how this is impacting our platform and we will update with more information shortly as we learn more.

2. 2026年3月24日 UTC 17:27monitoring

   We have identified increased error rates coming from Microsoft Teams that are causing delays in sending messages to Teams channels and DMs. We'll continue to monitor the situation and we will update with more information shortly as we learn more. We will provide the next update by 1830 UTC.

3. 2026年3月24日 UTC 18:33monitoring

   We are continuing to see an increase in error rates from Microsoft Teams, causing a delay in sending some messages to Teams channels and DMs. We are monitoring the situation and will provide an update by 1930 UTC.

4. 2026年3月24日 UTC 19:30monitoring

   We have seen an improvement in error rates and latency for requests to Microsoft Teams, and we expect the performance of sending messages to Teams channels and DMs to have returned to normal. We are continuing to monitor to ensure performance remains as expected, and we will provide a further update by 2100 UTC.

5. 2026年3月24日 UTC 20:52resolved

   We are no longer seeing elevated latency and error rates from Microsoft Teams.

1. 2026年3月24日 UTC 15:31identified

   We have identified increased error rates with an upstream call transcription provider. This is affecting Scribe for all customers. Our team are investigating and we will update with more information shortly as we learn more.

2. 2026年3月24日 UTC 15:33monitoring

   The issues were isolated to one region and we have performed a failover to a secondary region, restoring Scribe for all customers. You may need to ask Scribe to rejoin your call. We'll continue to monitor the situation and are working closely with the upstream provider while they resolve the issue.

3. 2026年3月24日 UTC 16:18monitoring

   Our failover region is continuing to work as expected, and Scribe functionality has been restored. You may need to ask Scribe to rejoin your calls. We'll continue to monitor the situation and are working closely with the upstream provider while they resolve the issue.

4. 2026年3月24日 UTC 17:02resolved

   We continue to use the failover region, and Scribe performance has returned to expected levels.

1. 2026年3月13日 UTC 14:19investigating

   We are currently investigating reports that users are unable to login using Slack.

2. 2026年3月13日 UTC 14:53identified

   Users in some Slack workspaces are unable to sign in with Slack. We have escalated this issue to Slack. Signing in with SAML and Microsoft Teams is not affected.

3. 2026年3月13日 UTC 15:54monitoring

   Slack have rolled back a change which caused this issue, and we have confirmed recovery. Please reach out to support if you're still experiencing any issues signing in with Slack.

4. 2026年3月13日 UTC 16:40resolved

   Slack have confirmed that the issue has been fully resolved, and affected customers have verified that they can log in successfully.

1. 2026年3月12日 UTC 13:20identified

   We've identified a drop in inbound traffic to [incident.io](http://incident.io "incident.io") from Opsgenie. This means that alerts may be slow to show up in [incident.io](http://incident.io "incident.io"), and paging via Opsgenie may be slow to reflect updates. This appears to be an issue with outbound webhooks on Opsgenie's side, we're monitoring the situation and will update as we know more.

2. 2026年3月12日 UTC 14:27resolved

   Traffic appears to be back to normal levels now.

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

   We have identified increased error rates with our Atlassian Statuspage integration. Atlassian have acknowledged an issue on their side (<https://metastatuspage.com/incidents/ctw5xv6t643h>). We'll continue to monitor this until the issue is resolved.

2. 2026年2月2日 UTC 11:37monitoring

   Atlassian's status page continues to show the issue with Statuspage (<https://metastatuspage.com/incidents/ctw5xv6t643h>). To restore the integration you can follow Atlassian's recommended workaround to regenerate your API key and reconnect in incident.io. We'll continue to monitor this until the issue is resolved.

3. 2026年2月2日 UTC 13:30monitoring

   Atlassian's status page continues to show the issue with Statuspage (<https://metastatuspage.com/incidents/ctw5xv6t643h>). To restore the integration you can follow Atlassian's recommended workaround to regenerate your API key and reconnect in [incident.io.](http://incident.io./ "incident.io.") We'll continue to monitor this until the issue is resolved.

4. 2026年2月2日 UTC 15:41monitoring

   Atlassian's status page continues to show the issue with Statuspage (<https://metastatuspage.com/incidents/ctw5xv6t643h>). To restore the integration you can follow Atlassian's recommended workaround to regenerate your API key and reconnect in [incident.io.](http://incident.io./ "incident.io.") We'll continue to monitor this and give an update in the next hour.

5. 2026年2月2日 UTC 16:06monitoring

   Atlassian's status page now reports that they are rolling out a fix (<https://metastatuspage.com/incidents/ctw5xv6t643h>). In the meantime, to restore the integration you can follow Atlassian's recommended workaround to regenerate your API key and reconnect in [incident.io.](http://incident.io./ "incident.io.") We continue to monitor the issue until it is resolved.

6. 2026年2月2日 UTC 16:56resolved

   Atlassian have confirmed that the issues with Statuspage have been resolved. You should now be able to reuse your original API key in our integration.

1. 2026年1月12日 UTC 15:36identified

   We have identified increased error rates with our Sentry integration. We are currently investigating how this is impacting our platform and we will update with more information shortly as we learn more.

2. 2026年1月12日 UTC 15:38monitoring

   Sentry have acknowledged an issue on their side ([https://status.sentry.io/incidents/wpg3tnwnwctj](https://status.sentry.io/incidents/wpg3tnwnwctj "https://status.sentry.io/incidents/wpg3tnwnwctj")), and we're seeing alerts come through from them ok. We'll continue to monitor things before closing this out.

3. 2026年1月12日 UTC 15:59resolved

   We've not seen any errors from Sentry since 15:35 UTC so we're closing this out. Please see Sentry's status page for any further details.

1. 2025年12月22日 UTC 10:29identified

   We have identified an increased rate of Sentry integrations becoming disconnected. Alert ingestion is unaffected. Please don't uninstall our application from Sentry: we are working to restore these connections on our side, and no action is currently required. We will provide an update in 30 minutes.

2. 2025年12月22日 UTC 10:58identified

   We're currently testing the fix that will allow us to re-connect any disconnected Sentry integrations on behalf of customers, and will have another update on this in 30 minutes.

3. 2025年12月22日 UTC 11:34identified

   We've verified a fix locally, and we're starting to roll this out in production now.

4. 2025年12月22日 UTC 12:04monitoring

   We have confirmed that we are able to restore these connections, and we are now in the process of restoring these. When this happens, you'll see that the Sentry integration no longer flags up as requiring reconnection. Once we have finished restoring access, we'll post another update here.

5. 2025年12月22日 UTC 13:57resolved

   We have managed to re-establish a connection to Sentry for almost all of the affected customers. If Sentry is still showing up as disconnected, you will need to remove the incident.io integration from the Sentry side, and then go through the reinstallation flow by opening incident.io and going to Settings → Integrations → Sentry. If you do this, please note that Sentry will remove the "Notify incident.io" action from alert rules when you uninstall the integration. If that was the only action in the alert rule, the entire rule is disabled. You will therefore need to verify any alert rules after re-installing.

1. 2025年12月15日 UTC 10:31investigating

   We are aware of an issue that is causing delays updating data in Insights. The team are currently investigating, and we'll provide further updates soon.

2. 2025年12月15日 UTC 11:49identified

   We are aware of an issue that is causing delays updating data in Insights. The team are currently working on mitigating this, and we'll provide further updates soon.

3. 2025年12月15日 UTC 14:41resolved

   The team have resolved this issue, and Insights are now syncing as expected.