Störungsverlauf von Affirm

1. 29. September 2026 um 19:26 UTCinvestigating

   Uns ist ein Problem bekannt, bei dem Zahlungsmethoden in der Mobile App für CA-Benutzer nicht angezeigt werden. Unser Team untersucht derzeit, und wir werden so schnell wie möglich zusätzliche Updates bereitstellen.

2. 29. September 2026 um 20:01 UTCidentified

   Wir haben die Ursache identifiziert und arbeiten weiter an einer Lösung für das Problem. Wir werden weitere Updates bereitstellen, sobald sie kommen.

3. 29. September 2026 um 20:52 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 12. August 2026 um 21:12 UTCidentified

   Wir erleben derzeit eine verschlechterte Leistung bei Affirm-Diensten. Unser Engineering-Team hat die Ursache identifiziert und arbeitet aktiv daran, einen Fix zu implementieren. Wir werden ein weiteres Update bereitstellen, sobald das Problem behoben ist oder weitere Informationen verfügbar sind.

2. 12. August 2026 um 21:24 UTCidentified

   Wir arbeiten weiter an einer Lösung für dieses Problem.

3. 12. August 2026 um 21:39 UTCmonitoring

   Ein Fix wurde implementiert und wir sehen derzeit eine Wiederherstellung und werden die Systemleistung weiterhin genau überwachen, um volle Stabilität zu gewährleisten.

4. 12. August 2026 um 22:00 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 22. Juni 2026 um 14:36 UTCmonitoring

   Wir haben eine Verschlechterung unseres Checkout-Flows infolge unseres CDN-Anbieters gesehen und glauben, dass er gemildert wurde. Unsere Teams überwachen weiterhin, bevor sie die vollständige Genesung bestätigen.

2. 22. Juni 2026 um 15:06 UTCresolved

   Die von unserem CDN-Anbieter verursachte Degradation des Checkout-Flows wurde behoben. Unsere Teams haben die vollständige Genesung bestätigt und der normale Service wurde wieder aufgenommen.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 17. Juni 2026 um 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. Juni 2026 um 00: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. Juni 2026 um 00:16 UTCmonitoring

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

4. 18. Juni 2026 um 00:44 UTCresolved

   This incident has been resolved.

1. 10. Juni 2026 um 15:06 UTCinvestigating

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

2. 10. Juni 2026 um 15:07 UTCinvestigating

   We are continuing to investigate this issue.

3. 10. Juni 2026 um 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. Juni 2026 um 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. Juni 2026 um 15:58 UTCresolved

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

1. 4. Juni 2026 um 08:01 UTCinvestigating

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

2. 4. Juni 2026 um 09:15 UTCmonitoring

   A fix has been implemented and we are monitoring recovery.

3. 4. Juni 2026 um 09:35 UTCmonitoring

   Services have been restored.

4. 4. Juni 2026 um 09:36 UTCresolved

   Services have been restored.

1. 3. Juni 2026 um 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. Juni 2026 um 19:47 UTCidentified

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

3. 3. Juni 2026 um 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. Juni 2026 um 20:49 UTCresolved

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

1. 8. Mai 2026 um 00:12 UTCinvestigating

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

2. 8. Mai 2026 um 00: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. Mai 2026 um 00: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. Mai 2026 um 01: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. Mai 2026 um 02: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. Mai 2026 um 02: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. Mai 2026 um 03: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. Mai 2026 um 08: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. Mai 2026 um 08: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. Mai 2026 um 09: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. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 03: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. April 2026 um 02:15 UTCinvestigating

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

2. 18. April 2026 um 02:43 UTCidentified

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

3. 18. April 2026 um 03: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. April 2026 um 04: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. April 2026 um 05: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. April 2026 um 16:31 UTCresolved

   This incident has been resolved.

1. 4. März 2026 um 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. März 2026 um 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. März 2026 um 00:38 UTCmonitoring

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

4. 5. März 2026 um 01:15 UTCmonitoring

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

5. 5. März 2026 um 02: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. März 2026 um 03:11 UTCresolved

   This incident has been resolved.

1. 12. Februar 2026 um 18:20 UTCinvestigating

   We are currently investigating this issue

2. 12. Februar 2026 um 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. Februar 2026 um 19:43 UTCresolved

   This incident has been resolved.

1. 29. Januar 2026 um 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. Januar 2026 um 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. Januar 2026 um 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. Januar 2026 um 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. Januar 2026 um 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. Januar 2026 um 16:32 UTCresolved

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

1. 14. Januar 2026 um 17:48 UTCidentified

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

2. 14. Januar 2026 um 18:10 UTCmonitoring

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

3. 14. Januar 2026 um 23:08 UTCmonitoring

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

4. 15. Januar 2026 um 03:46 UTCresolved

   This incident has been resolved.

1. 7. Januar 2026 um 07:45 UTCidentified

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

2. 7. Januar 2026 um 07:49 UTCmonitoring

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

3. 7. Januar 2026 um 07:51 UTCresolved

   This incident has been resolved.

1. 11. Dezember 2025 um 18:30 UTCmonitoring

   We are currently in a monitoring state.

2. 12. Dezember 2025 um 18:22 UTCresolved

   This incident has been resolved.

1. 5. Dezember 2025 um 09: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. Dezember 2025 um 09:33 UTCmonitoring

   We are seeing recovery, but will continue to monitor.

3. 5. Dezember 2025 um 09:54 UTCresolved

   This incident has been resolved and we are fully recovered.

1. 4. Dezember 2025 um 02:19 UTCinvestigating

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

2. 4. Dezember 2025 um 02:36 UTCidentified

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

3. 4. Dezember 2025 um 03:05 UTCmonitoring

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

4. 4. Dezember 2025 um 05:20 UTCresolved

   This incident has been resolved.

1. 3. Dezember 2025 um 18:18 UTCinvestigating

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

2. 3. Dezember 2025 um 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. Dezember 2025 um 19:02 UTCmonitoring

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

4. 3. Dezember 2025 um 20:02 UTCresolved

   This incident is resolved now.

1. 18. November 2025 um 17:11 UTCinvestigating

   We have detected intermittent API latency and are actively investigating.

2. 18. November 2025 um 17:30 UTCresolved

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