Poll Everywhere 中断历史

1. 2026年10月26日 UTC 20:18identified

   在某些情况下,编写报告所需时间比预期的要长。 我们已查明这一问题,并正在努力解决这一问题.

2. 2026年10月26日 UTC 20:40resolved

   这一事件已经得到解决.

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

1. 2026年10月6日 UTC 16:51investigating

   我们目前正在调查一个用户接受邀请后被重定向到错误页面的问题。 作为环绕工作,如果在错误页面上看到"Login Again"按钮,点击该按钮应解决邀请.

2. 2026年10月6日 UTC 18:06resolved

   这一事件已经得到解决.

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

1. 2026年9月18日 UTC 22:46investigating

   我们看到整个网站有504个网关超时以及整合.

2. 2026年9月18日 UTC 22:49investigating

   我们正在继续调查这一问题.

3. 2026年9月18日 UTC 23:07resolved

   这个问题已经得到解决。 这是因为我们的认证商出事了 关于这起事件的最新情况可在其状态页面上找到. https://status.workos.com/incidents/phs2prf38d75 (中文(简体) )

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

1. 2026年9月8日 UTC 16:35identified

   目前,我们提供基于电子邮件的客户支持的第三方服务供应商HubSpot正在出现停用。 见:https://status.hubspot.com/ (中文(简体) ). 在联系支助的问题得到解决后,我们将更新这一通知.

2. 2026年9月8日 UTC 16:36resolved

   我们的第三方服务提供者已经解决这个问题.

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

1. 2026年9月4日 UTC 16:33monitoring

   我们正在迁移我们的支援电话系统。 请透过电子邮件联系我们@pollwhere. +1 (209) 314-6894 +1 (415) 687-1503 我们赞赏你的耐心,并对任何不便表示歉意.

2. 2026年9月9日 UTC 15:43resolved

   这一事件已经得到解决.

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

1. 2026年8月25日 UTC 21:15identified

   我们已经确定了问题,并正在努力解决这个问题.

2. 2026年8月25日 UTC 21:18resolved

   这一事件已经得到解决。 如您在此期间发出邀请,且未收到邀请,请重新发送邀请.

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

1. 2026年8月12日 UTC 16:26investigating

   We are investigating an issue where the Add Choices, Question Flows, and other settings are missing from editing a question within a poll.

2. 2026年8月12日 UTC 16:31identified

   The issue has been identified as a bug with auto fit. We are actively working on a fix. As a work around in the meantime, window resizing should bring back the add choices and flows buttons on the bottom of the question edit page.

3. 2026年8月12日 UTC 16:46resolved

   This incident has been resolved

1. 2026年8月10日 UTC 06:42resolved

   From 13:33 PT to 17:50 PT on August 4, Poll Everywhere users were unable to login to new sessions. Existing login sessions were unaffected. We have implemented a long-term corrective that will stop this type of incident from happening in the future as of 22:40 PT on August 4. We are conducting an in-depth investigation and corrective actions to ensure that similar incidents do not occur. Please reach out to [email protected] if you have any questions related to this incident.

1. 2026年7月27日 UTC 15:51identified

   Google幻灯片正在推出一些用户的UI更新,打破了Google幻灯片民意调查插入. 我们正在积极研究一个补丁,以支持两个版本的UI. 作为工作,你可以尝试以下之一: • 创建新的浏览器配置文件,并用与Poll Everywhere有关的电子邮件地址签名,或 • 签署到另一个Google账户,并使用该账户插入幻灯片

2. 2026年7月28日 UTC 13:56identified

   我们已经查明了这个问题,并向Chrome Web Store和Microsoft Edge的扩展商店提交了最新的应用程序. 这些更新应在核准后提供.

3. 2026年7月28日 UTC 15:22resolved

   v1.20.5已放入商店,问题已经解决.

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

1. 2026年7月23日 UTC 14:20resolved

   我们收到报告说,在Poll Wheeldway 2.0中回答"世界云"和"QQA"问题的参与者在多次回答问题时偶尔会收到错误. 我们追踪到这期7月14日的更改,今天早上发布了一个定本.

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

1. 2026年7月21日 UTC 13:28resolved

   从3:52am PT到5:08 PT,Poll Wheeldway 2.0上出现了较高的出错率,有0.07%的请求失败,有500个内部服务器出错. 我们正在做一个长期的工作,但最初的影响已经减弱了.

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

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

   我们正在调查更高的错误率 当尝试验证

2. 2026年7月16日 UTC 08:32identified

   详细信息及更新请遵循https://status.workos.com/incidents/b52fkqjzcl20

3. 2026年7月16日 UTC 10:18monitoring

   情况似乎正在改善,继续检查https://status.workos.com/incicents/b52fkqjzcl20 详细情况和更新情况

4. 2026年7月16日 UTC 13:24resolved

   这个问题是同我们的第三方服务供应商WorkOS公司发生问题的结果,现已得到解决.

5. 2026年7月19日 UTC 22:10postmortem

   我们的第三方服务提供者WorkOS发表了一份[关于这一事件的死后](https://workos.com/blog/service-disruption-on-july-16-2026)。 在波尔各地,我们在定期审查供应商的过程中,考虑到了与第三方服务提供者有关的所有事件。 如果您对此事有任何疑问, 请联系@ [email protected] (mailto: [email protected]) 或联系您的 CSM .

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

1. 2026年7月2日 UTC 19:48identified

   我们已经确定,丹麦的数字没有为短信服务。 我们已经与我们的短信提供者联系,正在解决这一问题。 作为工作,您可以访问Profile - > 国际文本信息 - > 覆盖区域旋转到不同的数字 .

2. 2026年7月6日 UTC 15:38identified

   我们取消了丹麦的短信号码, 并失败了到德国的电话号码 而丹麦的号码没有工作.

3. 2026年7月13日 UTC 22:10identified

   该事件经过了更新,以包括丹麦以及其他一些国际数字. 作为工作,您可以访问Profile - > 国际文本信息 - > 覆盖区域将旋转至美国/加拿大.

4. 2026年7月13日 UTC 22:48resolved

   这一事件已经得到解决.

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

1. 2026年6月25日 UTC 09:19investigating

   Some tasks are currently delayed (such as deleting polls) in 1.0.

2. 2026年6月25日 UTC 09:23investigating

   The system has self-healed and brought the delay down to ~5 minutes and dropping. We are continuing to investigate.

3. 2026年6月25日 UTC 09:47identified

   We've identified the autoscaling performance issue and are working on implementing a long-term fix.

4. 2026年6月25日 UTC 10:45resolved

   We've changed the self-healing and autoscaling system to be more tolerant of faults at the times that the system has increased load. We've confirmed that the system is functioning normally as of right now and believe the problem to be resolved in the long term.

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

1. 2026年6月25日 UTC 08:53resolved

   We've discovered an automated monitoring issue that led automatic scaling to slow down certain user actions (like trashing polls) in 1.0. This issue is resolved, but we're looking into the root cause with the automatic monitoring system.

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

1. 2026年6月24日 UTC 19:46resolved

   Some users when trying to login to Poll Everywhere 2.0 were redirected incorrectly resulting in a 404 page. The root cause has been resolved.

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

1. 2026年6月15日 UTC 15:53resolved

   An automatic service update resulted in an outage for about 5 seconds, where approximately 80 requests failed. We have taken measures to prevent automatic service updates from creating this type of downtime in the future. Please contact [email protected] if you have any questions about this incident.

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

1. 2026年5月26日 UTC 03:31identified

   We've identified a disruption with our AI models. Our third-party service provider, Google, has discontinued the large language model used to generate poll content. We are working to migrate to a different model. During this time, AI features in Poll Everywhere 2.0 are unavailable. This issue does not affect Poll Everywhere 1.0.

2. 2026年5月26日 UTC 04:43resolved

   We have migrated to a comparable or equivalent model to the deprecated model. We will be taking further steps to understand this type of issue and prevent similar types of issues in the future. This issue started May 25, 2026 at midnight (i.e., 12:01am) PT.

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

1. 2026年5月5日 UTC 05:28monitoring

   A security incident affecting Instructure (Canvas) has been announced. Poll Everywhere is not affected by this security incident. It is possible that later changes that affect Canvas may require re-initializing Canvas LMS connections, but currently we are not aware of customers experiencing problems with LMS integrations as a result of this security incident. Please contact Poll Everywhere if you are experiencing any issues with Canvas at [email protected]. See: https://status.instructure.com/incidents/9wm4knj2r64z and https://status.instructure.com/incidents/ns0sjlmkvc6g. For information about the Canvas security incident, please reach out to your contact at Instructure directly.

2. 2026年5月11日 UTC 04:52monitoring

   We'd like to express our deepest sympathy for our partners, customers, teachers, and students affected by the Canvas security incident, particularly following the events of late last week. We understand that this is a particularly challenging time for everyone impacted, and we are sorry for the profound impact this has had on everyone during final exams and end-of-semester work. Poll Everywhere remains unaffected by the security incident with Canvas. Poll Everywhere has been conducting internal investigations and reviews, and confirmed that there is no impact to the Poll Everywhere platform at this time. Additionally, Instructure has not notified Poll Everywhere that any data related to its services has been impacted. Poll Everywhere's connection to Canvas uses the LTI Advantage standard, an industry-common integration pathway with a variety of LMS platforms, including (but not limited to) Canvas. We rely on a trusted set of keys provided by Instructure that validates that incoming data from Canvas is authentic. This key material is only changed by Instructure, and they have not changed it. However, if Instructure rotates this key material, Poll Everywhere will seamlessly update its data to trust the newly issued key material. The LTI standard also defines a set of keys that are maintained by Poll Everywhere. Poll Everywhere's key material (private keys) remains safely stored with Poll Everywhere, and has not been compromised. As a result, no API rotation, credential rotation, or other security-adjacent credential changes are necessary for any customer or end-user of Poll Everywhere to undertake, with respect to the Canvas integration, at this time. Please reach out to [email protected] if you have any questions related to the Canvas security incident and how it affects Poll Everywhere. Please refer to https://www.instructure.com/incident_update and https://status.instructure.com/ for the status of the Canvas platform.

3. 2026年5月14日 UTC 05:37resolved

   Thank you for your continued use and support of Poll Everywhere. We're sorry for the impact that the incident at Instructure has had on everyone impacted. With respect to the security incident at Instructure regarding Canvas, we believe that Instructure has directly communicated to all affected customers with resolution information about this incident. We believe this situation to be closed, and we will continue to monitor the situation in the background. For more information, on the Canvas side, please see: https://www.instructure.com/incident_update. Once again, Poll Everywhere was not impacted during the Canvas security incident. In terms of future impact to Poll Everywhere, we expect no action to be required in terms of rotation of LMS setup or configuration. We alter and adjust our security program, including organizational and technical controls, in response to security incidents in the industry, including this one. We will incorporate this incident into our future planning. We remain in contact with Instructure and will monitor their response to this situation going forward. Again, to be extremely clear, Poll Everywhere has had no impact from this incident at Instructure. However, we believe it is our role as members of the security community to learn from all incidents, including this one. If you have any questions, please feel free to reach out to [email protected].

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

1. 2026年5月4日 UTC 08:28resolved

   A small number of customers may have encountered an error upgrading their plans as a result of a tax calculation issue. This issue has been resolved, but the upgrade process will not automatically retry to prevent erroneous charges. Please retry those upgrades. If you encounter any issues upgrading, please contact [email protected].

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