Time: Dec. 8, 2021, 2:46 a.m.

Status: Resolved

Update: This incident has been resolved.

Time: Dec. 7, 2021, 5:55 p.m.

Status: Identified

Update: AWS is experiencing service degradation. Customers might experience problems relating to specific console pages. 6Connex will continue to monitor the situation and update any impacts it might have on our services.

Time: Dec. 8, 2021, 2:46 a.m.

Status: Resolved

Update: This incident has been resolved.

Time: Dec. 7, 2021, 5:55 p.m.

Status: Identified

Update: AWS is experiencing service degradation. Customers might experience problems relating to specific console pages. 6Connex will continue to monitor the situation and update any impacts it might have on our services.

Time: Aug. 5, 2021, 8:34 p.m.

Status: Resolved

Update: In an effort to meet client requirements and provide improved attendee experiences on both mobile and fixed devices, 6Connex performed an upgrade to all environments on Aug 4. Notification of the upgrade activities was provided via our standard processes (i.e. status.6connex.com and CSM/PM communications), but it became evident early on Aug 5 that the changes were not well-received by our virtual event partners. As a result of client feedback, 6Connex rolled back all the changes to the previous environment configuration, and tested to ensure that full feature functionality was restored. That effort was completed on Aug 5 at 3:15 PM CDT. Going forward, 6Connex will complete a root cause analysis, provide an incident report, and expand our user acceptance testing (UAT) and release notes. We apologize for the disruption and inconvenience this has caused, this is not the experience we desire for our clients. We appreciate your patience and partnership, and look forward to working with you in the future.

Time: Aug. 5, 2021, 8:01 p.m.

Status: Identified

Update: 6Connex has completed the rollback of the Aug 4 upgrade in all environments and is completing final testing. We will advise when all testing and maintenance activities are complete.

Time: Aug. 5, 2021, 7:12 p.m.

Status: Identified

Update: 6Connex has completed the rollback of the Aug 4 upgrade in the .us and .eu environments. All testing was successful and no user impacts were discovered.. 6Connex is moving forward with the final rollback in the .com environment, with completion targeted by COB Central time. We will advise when all maintenance activities are complete.

Time: Aug. 5, 2021, 6:41 p.m.

Status: Identified

Update: 6Connex has completed the rollback of the Aug 4 upgrade in the .us environment, and all testing was successful. No user impact was noted. 6Connex has commenced the rollback in the .eu environment, with completion targeted for mid-afternoon CDT. The .com rollback will commence once .eu is complete.

Time: Aug. 5, 2021, 3:37 p.m.

Status: Identified

Update: 6Connex has completed the rollback of the Aug 4 upgrade in the .us environment, and QA testing is underway. 6Connex intends to continue with the rollback in the .eu and .com environments once QA testing of the first rollback is complete

Time: Aug. 5, 2021, 1:47 p.m.

Status: Identified

Update: On August 4, 6Connex upgraded all environments to provide additional features and functionality in our virtual event platform. Based on client feedback received on August 5, 6Connex has decided to roll back those changes, and revert to the previous status. More information will be released once the rollback plan has been finalized, no later than 1030am CDT.

Time: Aug. 5, 2021, 8:34 p.m.

Status: Resolved

Update: In an effort to meet client requirements and provide improved attendee experiences on both mobile and fixed devices, 6Connex performed an upgrade to all environments on Aug 4. Notification of the upgrade activities was provided via our standard processes (i.e. status.6connex.com and CSM/PM communications), but it became evident early on Aug 5 that the changes were not well-received by our virtual event partners. As a result of client feedback, 6Connex rolled back all the changes to the previous environment configuration, and tested to ensure that full feature functionality was restored. That effort was completed on Aug 5 at 3:15 PM CDT. Going forward, 6Connex will complete a root cause analysis, provide an incident report, and expand our user acceptance testing (UAT) and release notes. We apologize for the disruption and inconvenience this has caused, this is not the experience we desire for our clients. We appreciate your patience and partnership, and look forward to working with you in the future.

Time: Aug. 5, 2021, 8:01 p.m.

Status: Identified

Update: 6Connex has completed the rollback of the Aug 4 upgrade in all environments and is completing final testing. We will advise when all testing and maintenance activities are complete.

Time: Aug. 5, 2021, 7:12 p.m.

Status: Identified

Update: 6Connex has completed the rollback of the Aug 4 upgrade in the .us and .eu environments. All testing was successful and no user impacts were discovered.. 6Connex is moving forward with the final rollback in the .com environment, with completion targeted by COB Central time. We will advise when all maintenance activities are complete.

Time: Aug. 5, 2021, 6:41 p.m.

Status: Identified

Update: 6Connex has completed the rollback of the Aug 4 upgrade in the .us environment, and all testing was successful. No user impact was noted. 6Connex has commenced the rollback in the .eu environment, with completion targeted for mid-afternoon CDT. The .com rollback will commence once .eu is complete.

Time: Aug. 5, 2021, 3:37 p.m.

Status: Identified

Update: 6Connex has completed the rollback of the Aug 4 upgrade in the .us environment, and QA testing is underway. 6Connex intends to continue with the rollback in the .eu and .com environments once QA testing of the first rollback is complete

Time: Aug. 5, 2021, 1:47 p.m.

Status: Identified

Update: On August 4, 6Connex upgraded all environments to provide additional features and functionality in our virtual event platform. Based on client feedback received on August 5, 6Connex has decided to roll back those changes, and revert to the previous status. More information will be released once the rollback plan has been finalized, no later than 1030am CDT.

Time: April 6, 2021, 3:27 p.m.

Status: Resolved

Update: The incident has been resolved and the platform is working as expected.

Time: April 6, 2021, 3:12 p.m.

Status: Monitoring

Update: A fix has been implemented in publishing errors, we are currently monitoring before we mark the issue as resolved.

Time: April 6, 2021, 2:30 p.m.

Status: Investigating

Update: The investigation is ongoing with members of our engineering and leadership team actively troubleshooting. Our team is also in the process of engaging 3rd party vendors to quickly work toward a solution.

Time: April 6, 2021, 12:53 p.m.

Status: Investigating

Update: We are continuing to investigate this issue.

Time: April 6, 2021, 12:51 p.m.

Status: Investigating

Update: We are investigating publishing errors within our .com environment and will provide additional updates soon.