Status dLocal Status
System status
Incident overview
Total incidents
100
Active now
0
Resolved
100
Avg. resolution
1h 11m
Recent incidents
View all →[Doku] Apparent incident with payment processing in Indonesia
[Nequi] Apparent incident with payment processing in Colombia
[Fawry] Apparent incident with payment processing in Egypt
[NBE | Egypt] Apparent incident with payment processing in Egypt
[Interswitch] Apparent incident with payment processing in Nigeria
Apparent incident with payment processing in Dominican Republic
[Firstdata] Apparent incident with payment processing in Brazil
[Banorte, Hey Banregio, Kushki] Apparent incident with payment processing in Mexico
[Didi BNPL) Apparent incident with payment processing in Mexico
[Interswitch] Apparent incident with payment processing in Nigeria
Frequently asked questions
Is Status dLocal down right now?
Status dLocal is currently maintenance. DevHelm monitors Status dLocal's official status page continuously and updates this page every 5 minutes.
What is Status dLocal's current uptime?
Status dLocal has a measured 30-day uptime of 100.00%. Over the last 24 hours, uptime is 100.00%, and over 7 days it is 100.00%. These figures are computed from Status dLocal's official status page data.
How many incidents has Status dLocal had recently?
Status dLocal has experienced 100 incidents in the recent monitoring window. Resolved incidents were fixed in an average of 1h 11m. All incidents are currently resolved.
What components does Status dLocal monitor?
DevHelm tracks 67 individual components for Status dLocal, including Bangladesh - Payment Processors, Bahrain - Payment Processors, Sandbox - dLocal Merchant Dashboard, Argentina - Payment Processors, dLocal API, and 62 more. Each component has its own status and 90-day uptime history shown above.
How can I get notified about Status dLocal outages?
You can subscribe to Status dLocal's incident feed via Atom/RSS at devhelm.io/status/dlocal/feed.xml for use in any feed reader. For real-time alerts via Slack, email, PagerDuty, or webhooks, add Status dLocal as a dependency in your DevHelm workspace.
About Status dLocal status monitoring
This page provides real-time operational status for Status dLocal, powered by DevHelm's continuous monitoring infrastructure. We track Status dLocal's official status page and aggregate component-level data into uptime percentages, incident timelines, and historical trends.
Status dLocal status data is refreshed every 5 minutes. We currently track 67 individual components, each with its own operational status and 90-day uptime history.
Uptime percentages represent the proportion of time all monitored components reported operational status. Incident data comes from vendor-published incident timelines and includes status updates, affected components, and resolution times.
Track Status dLocal in your stack
Get alerted when Status dLocal has issues — before your users notice. Set up in 30 seconds.