Historial de interrupciones de Affirm

1. 29 de septiembre de 2026 a las 19:26 UTCinvestigating

   Somos conscientes de un problema en el que los métodos de pago no se muestran en la aplicación móvil para los usuarios de CA. Nuestro equipo está investigando y proporcionaremos actualizaciones adicionales lo antes posible.

2. 29 de septiembre de 2026 a las 20:01 UTCidentified

   Hemos identificado la causa y seguimos trabajando en una solución para la cuestión. Proporcionaremos más actualizaciones a medida que vengan.

3. 29 de septiembre de 2026 a las 20:52 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 12 de agosto de 2026 a las 21:12 UTCidentified

   Actualmente estamos experimentando un rendimiento degradado en todos los servicios de Affirm. Nuestro equipo de ingeniería ha identificado la causa raíz y está trabajando activamente para implementar una solución. Proporcionaremos otra actualización tan pronto como se resuelva el problema o se disponga de más información.

2. 12 de agosto de 2026 a las 21:24 UTCidentified

   Seguimos trabajando en una solución para esta cuestión.

3. 12 de agosto de 2026 a las 21:39 UTCmonitoring

   Se ha aplicado una solución y actualmente estamos viendo la recuperación y seguiremos vigilando de cerca el rendimiento del sistema para garantizar la plena estabilidad.

4. 12 de agosto de 2026 a las 22:00 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 22 de junio de 2026 a las 14:36 UTCmonitoring

   Hemos visto una degradación de nuestro flujo de control como resultado de nuestro proveedor de CDN y creemos que ha sido mitigado. Nuestros equipos continúan monitoreando antes de confirmar la recuperación completa.

2. 22 de junio de 2026 a las 15:06 UTCresolved

   Se ha resuelto la degradación del flujo de control causada por nuestro proveedor de CDN. Nuestros equipos han confirmado la recuperación completa y se ha reanudado el servicio normal.

Traducido automáticamente desde la actualización oficial del incidente.

1. 17 de junio de 2026 a las 23:22 UTCinvestigating

   We are currently investigating an issue with the confirm_loan endpoint in the Affirm US sandbox. We will update further as scope and root cause are uncovered.

2. 18 de junio de 2026 a las 0:05 UTCinvestigating

   We are continuing to investigate the root cause of this issue. We are comparing successful and non-successful sandbox loan confirmations to understand potential mitigations.

3. 18 de junio de 2026 a las 0:16 UTCmonitoring

   A fix has been implemented and we are now monitoring the results.

4. 18 de junio de 2026 a las 0:44 UTCresolved

   This incident has been resolved.

1. 10 de junio de 2026 a las 15:06 UTCinvestigating

   We are experiencing a degradation in our checkout flow for users in Canada.

2. 10 de junio de 2026 a las 15:07 UTCinvestigating

   We are continuing to investigate this issue.

3. 10 de junio de 2026 a las 15:35 UTCinvestigating

   Our teams are still investigating the root cause of the issue. We will provide an update as soon as possible.

4. 10 de junio de 2026 a las 15:45 UTCmonitoring

   The errors within the checkout flow have resolved and the issue has been mitigated. Our teams are continuing to monitor before confirming full recovery.

5. 10 de junio de 2026 a las 15:58 UTCresolved

   The checkout service has remained operational. This incident is now resolved.

1. 4 de junio de 2026 a las 8:01 UTCinvestigating

   The Affirm team has observed degradation in some US checkouts and is currently investigating.

2. 4 de junio de 2026 a las 9:15 UTCmonitoring

   A fix has been implemented and we are monitoring recovery.

3. 4 de junio de 2026 a las 9:35 UTCmonitoring

   Services have been restored.

4. 4 de junio de 2026 a las 9:36 UTCresolved

   Services have been restored.

1. 3 de junio de 2026 a las 19:00 UTCidentified

   We have identified the cause of the disruption to our Sandbox APIs and we are currently attempting to fix the issue.

2. 3 de junio de 2026 a las 19:47 UTCidentified

   We are continuing to work on a fix for this issue.

3. 3 de junio de 2026 a las 20:36 UTCmonitoring

   We have implemented a fix and have seen a recovery in the availability of our Sandbox APIs. We will continue to monitor the situation to ensure that our systems are fully operational.

4. 3 de junio de 2026 a las 20:49 UTCresolved

   Our team has deployed a fix and have seen the errors subside. All services are now functioning as expected.

1. 8 de mayo de 2026 a las 0:12 UTCinvestigating

   We are currently experiencing elevated latency across our services leading to timeouts and errors. We are actively investigating the issue.

2. 8 de mayo de 2026 a las 0:30 UTCidentified

   We are currently experiencing elevated latency to our services. This has been traced to an issue with our cloud service provider, and our team is actively working toward resolution.

3. 8 de mayo de 2026 a las 0:58 UTCidentified

   We continue to experience elevated latency across our services. Error rates have decreased, though response times remain slower than normal. This is due to an issue with our cloud service provider, who is actively working toward a full resolution.

4. 8 de mayo de 2026 a las 1:31 UTCidentified

   We continue to experience elevated latency across our services, though error rates remain decreased. Our cloud service provider is actively working toward a full resolution.

5. 8 de mayo de 2026 a las 2:19 UTCidentified

   We continue to experience elevated latency across our services, with sporadic increases in error rates throughout the duration of this incident. Our cloud service provider is actively working toward a full resolution.

6. 8 de mayo de 2026 a las 2:43 UTCmonitoring

   We are seeing improved latency across our services and response times are trending back toward normal. We are continuing to monitor while we await final resolution confirmation from our cloud service provider.

7. 8 de mayo de 2026 a las 3:26 UTCmonitoring

   We experienced a slight increase in errors and latency, which has since subsided. We are continuing to monitor while we await final resolution confirmation from our cloud service provider.

8. 8 de mayo de 2026 a las 8:00 UTCmonitoring

   Latency has continued to improve across our services and overall performance has stabilized. We are continuing to monitor while we await final resolution confirmation from our cloud service provider.

9. 8 de mayo de 2026 a las 8:50 UTCmonitoring

   Latency and overall performance remain stabilized. We are continuing to monitor while we await final resolution confirmation from our cloud service provider.

10. 8 de mayo de 2026 a las 9:59 UTCmonitoring

    We are experiencing an increase in errors and latency. We are continuing to monitor while we await final confirmation of resolution from our cloud service provider.

11. 8 de mayo de 2026 a las 11:11 UTCmonitoring

    Latency and overall performance remain stabilized. We are continuing to monitor while our cloud service provider fully resolves the issue.

12. 8 de mayo de 2026 a las 13:38 UTCmonitoring

    Latency and overall performance remain stable. We are continuing to monitor while our cloud service provider fully resolves the issue.

13. 8 de mayo de 2026 a las 15:30 UTCmonitoring

    Affirm Latency and overall performance remain stable. We are still awaiting full confirmation from our cloud service provider before declaring the incident resolved.

14. 8 de mayo de 2026 a las 16:39 UTCmonitoring

    We continue to receive positive signal from our cloud service provider. Affirm latency and performance remain stable. We are awaiting full confirmation from our cloud service provider before declaring the incident resolved.

15. 8 de mayo de 2026 a las 17:31 UTCmonitoring

    Affirm latency and performance remain stable. We are awaiting full confirmation from our cloud service provider before declaring the incident resolved.

16. 8 de mayo de 2026 a las 19:31 UTCmonitoring

    We are maintaining a monitoring posture on this incident as we await a statement of permanent resolution from our cloud cloud service provider. Affirm latency and performance remain stable.

17. 8 de mayo de 2026 a las 21:55 UTCmonitoring

    Our cloud service provider has notified us that full resolution will require some time to finalize. As Affirm's latency and performance have remained stable throughout the day, we will update on Affirm's status when we receive an all-clear signal from the service provider or we see a regression in service health.

18. 9 de mayo de 2026 a las 3:20 UTCresolved

    Our cloud service provider has confirmed operations are fully restored and we are seeing continued healthy observability on our end. Incident resolved.

1. 18 de abril de 2026 a las 2:15 UTCinvestigating

   We are currently investigating an increase in our SMS PIN retry rate affecting Affirm Checkout in the US

2. 18 de abril de 2026 a las 2:43 UTCidentified

   We have identified the cause of the SMS retry rate and are investigating potential mitigations.

3. 18 de abril de 2026 a las 3:03 UTCidentified

   We are still observing elevated PIN retry rates for users in US. There is a central point of failure effecting multiple 3rd party SMS providers. Users who retry are successfully completing checkouts. We will continue to monitor the situation and update as it progresses.

4. 18 de abril de 2026 a las 4:15 UTCidentified

   PIN retry rates for users in US remain unchanged. There is a central point of failure effecting multiple 3rd party SMS providers. Users who retry are successfully completing checkouts. We will continue to monitor the situation and update as it progresses.

5. 18 de abril de 2026 a las 5:37 UTCmonitoring

   We were able to cutover traffic to a recovered SMS service and have observed recovery. We will continue to monitor before resolving the incident.

6. 18 de abril de 2026 a las 16:31 UTCresolved

   This incident has been resolved.

1. 4 de marzo de 2026 a las 23:36 UTCinvestigating

   We are currently investigating a degradation to loan authorization rate, indicating an issue in the checkout flow. We will update with new findings as soon as possible

2. 4 de marzo de 2026 a las 23:47 UTCidentified

   We have performed a mitigation and have observed checkout availability recovery for all merchants. We will monitor to ensure stability.

3. 5 de marzo de 2026 a las 0:38 UTCmonitoring

   We have maintained normal availability since the mitigation. We are continuing to dig into root causes on this issue.

4. 5 de marzo de 2026 a las 1:15 UTCmonitoring

   Affirm's systems remain stable and we are making progress determining root cause. More updates will come shortly.

5. 5 de marzo de 2026 a las 2:03 UTCmonitoring

   We are implementing a permanent fix to the mitigated issue. Checkout activity remains healthy. We will monitor the results and resolve the incident once efficacy of said fix has been confirmed.

6. 5 de marzo de 2026 a las 3:11 UTCresolved

   This incident has been resolved.

1. 12 de febrero de 2026 a las 18:20 UTCinvestigating

   We are currently investigating this issue

2. 12 de febrero de 2026 a las 19:18 UTCmonitoring

   We have identified the root cause of the incident and will continue monitoring our services to ensure that our services maintain operational.

3. 12 de febrero de 2026 a las 19:43 UTCresolved

   This incident has been resolved.

1. 29 de enero de 2026 a las 17:35 UTCinvestigating

   We are currently investigating an issue affecting order status updates for merchants using the Shopify Payments App. While customers can still complete the Affirm checkout flow, there is a delay in orders being marked as 'Authorized' or 'Confirmed' within the Shopify dashboard. Our engineering team is working to restore event processing.

2. 29 de enero de 2026 a las 18:16 UTCresolved

   The issue affecting Shopify order status updates has been resolved. All delayed events have been processed, and order statuses are now appearing correctly in the Shopify dashboard. We appreciate your patience.

1. 22 de enero de 2026 a las 15:40 UTCinvestigating

   We are currently experiencing a drop in checkout availability. We are working on identifying the root cause to return service as soon as possible. We will update as soon as we can.

2. 22 de enero de 2026 a las 15:52 UTCinvestigating

   We have seen a recovery in our services but we are still monitoring and investigating the root cause of the issue. We will provide an update as soon as possible.

3. 22 de enero de 2026 a las 16:22 UTCmonitoring

   We have identified the root cause of the incident and will continue monitoring our services to ensure that our services maintain operational.

4. 22 de enero de 2026 a las 16:32 UTCresolved

   Our services have maintained operational. This incident is now resolved.

1. 14 de enero de 2026 a las 17:48 UTCidentified

   We are observing authentication issues for some consumers related to ongoing nation-wide carrier disruptions.

2. 14 de enero de 2026 a las 18:10 UTCmonitoring

   We will continue to monitor the situation to ensure performance remains stable.

3. 14 de enero de 2026 a las 23:08 UTCmonitoring

   We are continuing to monitor the situation to ensure performance remains stable.

4. 15 de enero de 2026 a las 3:46 UTCresolved

   This incident has been resolved.

1. 7 de enero de 2026 a las 7:45 UTCidentified

   We've identified the source of the degradation in Affirm Checkout and we are working on a mitigation

2. 7 de enero de 2026 a las 7:49 UTCmonitoring

   We've deployed a mitigation, throughput is recovering and are actively monitoring.

3. 7 de enero de 2026 a las 7:51 UTCresolved

   This incident has been resolved.

1. 11 de diciembre de 2025 a las 18:30 UTCmonitoring

   We are currently in a monitoring state.

2. 12 de diciembre de 2025 a las 18:22 UTCresolved

   This incident has been resolved.

1. 5 de diciembre de 2025 a las 9:15 UTCidentified

   We are currently experiencing a degradation in all Affirm API's for users. Our engineering team is working to identify the root cause and implement a solution as soon as possible.

2. 5 de diciembre de 2025 a las 9:33 UTCmonitoring

   We are seeing recovery, but will continue to monitor.

3. 5 de diciembre de 2025 a las 9:54 UTCresolved

   This incident has been resolved and we are fully recovered.

1. 4 de diciembre de 2025 a las 2:19 UTCinvestigating

   We are investigating increased API error rates in the US-EAST-1 Region.

2. 4 de diciembre de 2025 a las 2:36 UTCidentified

   We have identified the root cause of the service disruption and are actively working on a mitigation.

3. 4 de diciembre de 2025 a las 3:05 UTCmonitoring

   We have not seen a recurrence since approximately 18:20 pm PT and are continuing to monitor our dashboards.

4. 4 de diciembre de 2025 a las 5:20 UTCresolved

   This incident has been resolved.

1. 3 de diciembre de 2025 a las 18:18 UTCinvestigating

   We are investigating increased API error rates in the US-EAST-1 Region.

2. 3 de diciembre de 2025 a las 18:19 UTCidentified

   We identified what's causing this increased API error rates in the US-EAST-1 Region and currently working to mitigate.

3. 3 de diciembre de 2025 a las 19:02 UTCmonitoring

   We are seeing recovery across all endpoints - we will keep monitoring for full resolution.

4. 3 de diciembre de 2025 a las 20:02 UTCresolved

   This incident is resolved now.

1. 18 de noviembre de 2025 a las 17:11 UTCinvestigating

   We have detected intermittent API latency and are actively investigating.

2. 18 de noviembre de 2025 a las 17:30 UTCresolved

   The latency was related to a disruption on a core infrastructure provider. We are observing full recovery.