dLocal Outage History
Daily provider-status observations and published incident history for dLocal.
dLocal has an active component incident; no global outage is indicated. Verified . Official provider source.
Looking for an update now? Check the current status, or follow dLocal for future changes.
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
| Month | Issue-free days | Days Tracked | Days with issues |
|---|---|---|---|
| September 2026 | 0% | 28 | 28 |
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Incident History
[Numbers] Apparent incident with payment processing in Pakistan
View incident details and source
Started:
Iyzico- Apparent incident with payment processing in Turkey
View incident details and source
Started:
[COMMERCIAL INTERNATIONAL BANK (EGYPT) S.A.E.] Apparent incident with payment processing in Egypt
View incident details and source
Started:
Iyzico- Apparent incident with payment processing in Turkey
View incident details and source
Started:
Iyzico- Apparent incident with payment processing in Turkey
View incident details and source
Started:
[Iyzico] Apparent incident with payment processing in Turkey
View incident details and source
Started:
[ACH] Apparent incident with payment processing in Colombia
View incident details and source
Started:
[Pivot] Apparent incident with payment processing in Indonesia
View incident details and source
Started:
[Flutterwave] Apparent incident with payment processing in Nigeria
View incident details and source
Started:
[Peach-Nedbank] Apparent incident with payment processing in South Africa
View incident details and source
Started:
Legacy Incident Archive
824 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.