# PropelAuth Status - Incident history

## Maintenance
### cmixvas680jx4u8b0d88wbg0w
**Date:** 2025-12-20 15:45:00 GMT+0  
**Type:** Maintenance  
**Duration:** 30 minutes  
**Affected Components:** Authentication  
**Updates:**  
- **Identified** (Dec 20, 15:45:00 GMT+0): We're performing critical updates to our infrastructure. We will do our best to minimize downtime and don't expect it to take the full 30 minutes.  
- **Completed** (Dec 20, 16:15:06 GMT+0): Maintenance has completed successfully.

### cm55rql8e006j11kjd4mtdbiz
**Date:** 2024-12-28 20:00:00 GMT+0  
**Type:** Maintenance  
**Duration:** 1 hour  
**Affected Components:** Authentication  
**Updates:**  
- **Identified** (Dec 28, 20:00:00 GMT+0): We have planned infrastructure upgrades during this time. No downtime is anticipated.  
- **Identified** (Dec 28, 20:00:01 GMT+0): Maintenance is now in progress.  
- **Completed** (Dec 28, 21:00:00 GMT+0): Maintenance has completed successfully.

## Incident
### cm2ods7tl00018nitc0o129vx
**Date:** 2024-10-25 06:58:33 GMT+0  
**Type:** Incident  
**Duration:** 5 minutes  
**Affected Components:** Authentication  
**Updates:**  
- **Investigating** (Oct 25, 06:58:33 GMT+0): We are currently investigating this incident.  
- **Resolved** (Oct 25, 07:02:00 GMT+0): This incident has been resolved.

### cm2o9ct0s0005e0f5pu05pl7v
**Date:** 2024-10-25 04:54:36 GMT+0  
**Type:** Incident  
**Duration:** 24 minutes  
**Affected Components:** Authentication  
**Updates:**  
- **Investigating** (Oct 25, 04:54:36 GMT+0): We are currently investigating this incident.  
- **Monitoring** (Oct 25, 05:12:12 GMT+0): We implemented a fix and are currently monitoring the result.  
- **Resolved** (Oct 25, 05:19:00 GMT+0): This incident has been resolved.

### cm1y68ab3003znzlggepbdbml
**Date:** 2024-10-06 22:45:06 GMT+0  
**Type:** Incident  
**Duration:** 8 minutes  
**Affected Components:** Authentication  
**Updates:**  
- **Monitoring** (Oct 6, 22:45:06 GMT+0): We implemented a fix and are currently monitoring the result.  
- **Resolved** (Oct 6, 22:52:47 GMT+0): This incident has been resolved.

### clx1ehywc20971bfocb8x29e5b
**Date:** 2024-09-17 01:20:00 GMT+0  
**Type:** Incident  
**Duration:** 10 minutes  
**Affected Components:** Authentication  
**Updates:**  
- **Investigating** (Sep 17, 01:20:00 GMT+0): We are currently investigating this incident.  
- **Resolved** (Sep 17, 01:30:00 GMT+0): This incident has been resolved.

### clzxcdlpc0057wiyu0v952960
**Date:** 2024-08-17 15:30:00 GMT+0  
**Type:** Maintenance  
**Duration:** 16 minutes  
**Affected Components:** Authentication  
**Updates:**  
- **Identified** (Aug 17, 15:30:00 GMT+0): We are going to be making some infrastructure upgrades. We anticipate that this will not be disruptive, but there may be a short period of failed requests.  
- **Identified** (Aug 17, 15:30:01 GMT+0): Maintenance is now in progress.  
- **Completed** (Aug 17, 15:45:49 GMT+0): Maintenance has completed successfully.

### cldxe1pbt20537icmx4zwfk9or
**Date:** 2024-06-05 05:27:00 GMT+0  
**Type:** Incident  
**Duration:** 7 minutes  
**Affected Components:** Authentication  
**Updates:**  
- **Identified** (Jun 5, 05:27:00 GMT+0): .  
- **Resolved** (Jun 5, 05:34:00 GMT+0): This incident has been resolved.  
- **Monitoring** (Jun 5, 05:32:00 GMT+0): A fix has been implemented and we are monitoring.

### cliiekd0b520896awn8kmlfe6mq
**Date:** 2023-06-05 05:19:43 GMT+0  
**Type:** Incident  
**Duration:** 21 minutes  
**Affected Components:** Authentication  
**Updates:**  
- **Investigating** (Jun 5, 05:19:43 GMT+0): We are currently investigating this incident.  
- **Resolved** (Jun 5, 05:40:26 GMT+0): This incident has been resolved.

### clwwzmewc7860bsob21pamwg3
**Date:** 2024-06-02 03:00:00 GMT+0  
**Type:** Incident  
**Duration:** 37 minutes  
**Affected Components:** Authentication  
**Updates:**  
- **Monitoring** (Jun 2, 03:00:00 GMT+0): Some APIs experienced intermittent timeouts. A fix is live, we are now monitoring. The issue should be resolved shortly.  
- **Resolved** (Jun 2, 03:37:00 GMT+0): This incident has been resolved.