# Login Incident Updates

**URL:** https://discourse.shapr3d.com/t/login-incident-updates/21193
**Category:** Modeling Questions
**Created:** [August 31, 2022, 3:55pm UTC](https://discourse.shapr3d.com/t/login-incident-updates/21193 "2022-08-31T15:55:51Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![KPeter](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.shapr3d.com/kpeter/32/7644_2.png) [@KPeter](https://discourse.shapr3d.com/u/KPeter)
#### Post date: [August 31, 2022, 3:55pm UTC](https://discourse.shapr3d.com/t/login-incident-updates/21193/1 "2022-08-31T15:55:51Z")

</div>

**public incident update #1:**

We are aware of an ongoing incident in our production systems that results in users being logged out, unable to log back in.

Our engineers are looking at the problem and we are working on the mitigation. Please stay tuned for updates and we apologize for the inconvenience.

---

<div class="post-metadata">

### Author: ![KPeter](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.shapr3d.com/kpeter/32/7644_2.png) [@KPeter](https://discourse.shapr3d.com/u/KPeter)
#### Post date: [August 31, 2022, 3:56pm UTC](https://discourse.shapr3d.com/t/login-incident-updates/21193/2 "2022-08-31T15:56:46Z")

</div>



---

<div class="post-metadata">

### Author: ![KPeter](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.shapr3d.com/kpeter/32/7644_2.png) [@KPeter](https://discourse.shapr3d.com/u/KPeter)
#### Post date: [August 31, 2022, 4:27pm UTC](https://discourse.shapr3d.com/t/login-incident-updates/21193/3 "2022-08-31T16:27:45Z")

</div>

**Update #2:**

We have identified the source of the problem in our services responsible for authentication and we are actively working to resolve it.

Mitigation steps were taken. As a result, login attempts are served slower, but with a higher chance of succeeding.

---

<div class="post-metadata">

### Author: ![KPeter](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.shapr3d.com/kpeter/32/7644_2.png) [@KPeter](https://discourse.shapr3d.com/u/KPeter)
#### Post date: [August 31, 2022, 5:19pm UTC](https://discourse.shapr3d.com/t/login-incident-updates/21193/4 "2022-08-31T17:19:15Z")

</div>

**Update #3:**

A set of fixes and capacity increases were deployed. They brought back operational stability for our authentication system.

We are keeping an eye on the situation.

---

<div class="post-metadata">

### Author: ![KPeter](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.shapr3d.com/kpeter/32/7644_2.png) [@KPeter](https://discourse.shapr3d.com/u/KPeter)
#### Post date: [August 31, 2022, 5:35pm UTC](https://discourse.shapr3d.com/t/login-incident-updates/21193/5 "2022-08-31T17:35:31Z")

</div>

**Update #4:**

The fixes have been validated, the incident has been resolved.

We apologize for the inconvenience caused.

---

<div class="post-metadata">

### Author: ![KPeter](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.shapr3d.com/kpeter/32/7644_2.png) [@KPeter](https://discourse.shapr3d.com/u/KPeter)
#### Post date: [September 1, 2022, 6:06am UTC](https://discourse.shapr3d.com/t/login-incident-updates/21193/6 "2022-09-01T06:06:55Z")

</div>


