dLocal incident

[Easypaisa payment method] Apparent incident with payment processing in Pakistan

Minor Resolved View vendor source →

dLocal experienced a minor incident on October 2, 2026 affecting Pakistan - Payment Processors, lasting 5d 21h. The incident has been resolved; the full update timeline is below.

Started
Oct 02, 2026, 10:32 PM UTC
Resolved
Oct 08, 2026, 08:28 PM UTC
Duration
5d 21h
Detected by Pingoru
Oct 02, 2026, 10:32 PM UTC

Affected components

Pakistan - Payment Processors

Update timeline

  1. investigating Oct 02, 2026, 10:33 PM UTC

    We have identified some processing issues with Easypaisa payment method payment method in Pakistan. We have contacted the processor and we will provide an update as soon as it becomes available.

  2. investigating Oct 03, 2026, 01:45 AM UTC

    We are continuing to investigate this issue.

  3. investigating Oct 03, 2026, 09:24 AM UTC

    We are continuing to investigate this issue.

  4. investigating Oct 03, 2026, 12:15 PM UTC

    We are continuing to investigate the issue and will share an update as soon as possible.

  5. investigating Oct 03, 2026, 05:16 PM UTC

    We are continuing to investigate the issue and will share an update as soon as possible.

  6. investigating Oct 04, 2026, 02:31 AM UTC

    We are still investigating processing issues with easypaisa. We remain in contact with the processor and will provide an update as soon as more information becomes available.

  7. identified Oct 04, 2026, 01:14 PM UTC

    We are still investigating the issue and will provide an update as soon as possible.

  8. identified Oct 05, 2026, 12:26 AM UTC

    We are continuing to investigate the issue and will share an update as soon as possible.

  9. identified Oct 05, 2026, 04:45 AM UTC

    We are currently working with our internal team to investigate this issue and will provide an update as soon as possible. Thank you for your patience.

  10. identified Oct 06, 2026, 02:17 AM UTC

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

  11. identified Oct 06, 2026, 09:02 AM UTC

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

  12. identified Oct 06, 2026, 05:11 PM UTC

    We are working to resolve this issue and remain in close contact with the processor. We will provide an update as soon as more information becomes available. Thank you for your patience and understanding while we work toward a resolution.

  13. identified Oct 07, 2026, 12:49 AM UTC

    We are working to resolve this issue and remain in close contact with the processor. We will provide an update as soon as more information becomes available. Thank you for your patience and understanding while we work toward a resolution.

  14. identified Oct 07, 2026, 04:28 AM UTC

    We are working to resolve this issue and remain in close contact with the processor. We will provide an update as soon as more information becomes available. Thank you for your patience and understanding while we work toward a resolution.

  15. identified Oct 08, 2026, 02:14 AM UTC

    We remain in close contact with the processor and are awaiting further updates regarding the resolution. We will provide another update as soon as more information becomes available.

  16. identified Oct 08, 2026, 07:52 AM UTC

    We remain in close contact with the processor; however, there are no further updates regarding the resolution at this time. We are continuing to follow up and will provide another update as soon as more information becomes available.

  17. resolved Oct 08, 2026, 08:28 PM UTC

    This incident has been resolved.