Skip to content
PulseWatchOUTAGE.INTEL
dLocal logo

Payments

Is dLocal down right now?

UnknownOfficial status last polled Oct 12, 2026 12:55 UTCdlocal.comOfficial status page

Are you on the dLocal team and see something inaccurate? Report it to us. We respond within one business day.

Is dLocal down right now?

Unknown. dLocal does not have a conclusive current status. A single-runtime HTTP reachability check succeeded; no fresh official status confirms whole-service health.

Status as of Oct 12, 2026 19:30 UTC

Unknown

dLocal: status unknown

As of Oct 12, 2026 19:30 UTC

No product check is currently qualified to corroborate an incident for this service. Overall service status has not been established.

Reports 24h

0

Last incident

Oct 5, 2026 19:59 UTC

Trend

0/15m

Monitoring

Coverage gap

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for dLocal.

17

Incident days

13

No recorded incident

160h 55m

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical
Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.
Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for dLocal. Hover a day for detail.

Sep 13Sep 18Sep 23Sep 28Oct 3Oct 801234

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

17

Days with incidents

3 incidents

Busiest day

160h 55m

Recorded duration

Report volume

0 reports in last 24H

07:30 PM11:00 PM02:30 AM06:00 AM09:30 AM01:00 PM04:30 PM00.511.52baseline 1

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

dLocal: vendor-reported minor incident on October 2 (tracked 2d 22h)

Oct 2, 09:20 PM → Oct 5, 07:59 PM · 2d 22h · medium

dLocal reported a minor-impact incident on its own status page. PulseWatch followed the vendor's status page and did not independently confirm the incident. PulseWatch tracked this incident for 2d 22h, closing it on 2026-10-05T19:59:56.241Z.

Duration
2d 22h
tracked by PulseWatch

Impact

PulseWatch recorded no user reports for this incident and therefore cannot describe what users experienced. The incident is known from dLocal's own status page.

Incident timeline

  1. Oct 2, 09:20 PM

    The vendor reported a minor-impact incident on its own status page; PulseWatch began tracking it

  2. Oct 2, 09:20 PM

    Status updated: possible issue

  3. Oct 5, 07:59 PM

    PulseWatch closed the incident

Official updates

  1. Oct 2, 09:20 PM

    dLocal reported the incident on its status page.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on the vendor's own status page.

Reliability

Not measured

30-day uptime

n/a

90-day uptime

n/a

Not calculated: dLocal is unknown, so there is no incident history to measure and no uptime figure is shown.

Other payments services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

500 characters left

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →
ResolvedMedium

dLocal: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

10/2/2026, 9:20:54 PM · 2d 22h

09:20 PM07:59 PM
Detection10/2/2026, 9:20:54 PM · 9d ago

Detected — medium severity

dLocal: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedMedium

dLocal: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

10/2/2026, 12:20:55 AM · 1h 33m

12:20 AM01:54 AM
Detection10/2/2026, 12:20:55 AM · 10d ago

Detected — medium severity

dLocal: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedMedium

dLocal: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

10/1/2026, 12:21:11 PM · 10h 30m

12:21 PM10:51 PM
Detection10/1/2026, 12:21:11 PM · 11d ago

Detected — medium severity

dLocal: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedMedium

dLocal: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

10/1/2026, 12:24:46 AM · 4h 52m

12:24 AM05:16 AM
Detection10/1/2026, 12:24:46 AM · 11d ago

Detected — medium severity

dLocal: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedMedium

dLocal: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

9/30/2026, 10:50:32 AM · 4h 6m

10:50 AM02:56 PM
Detection9/30/2026, 10:50:32 AM · 12d ago

Detected — medium severity

dLocal: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

DetectionPeakStatus updateResolvedCrowd warning

Subscribe to updates

Get an email the moment dLocal enters an incident — and again when it's resolved. No account required.

Free for anyone. Unsubscribe anytime from any email we send.

Signal quality

Live signal

Status
Unknown
Monitoring
A single-runtime HTTP reachability check succeeded; no fresh official status confirms whole-service health.
Coverage
Verified against the vendor's own incident history
Reports (24h)
0
Baseline / hour
5
Open threshold
3x

Official site

dlocal.com