PulseWatch manages 5 data types including abuse signals. Helps you organize, track, and share your work in 1 place for teams and solo users.

How does PulseWatch know if Ledger is down?

PulseWatch evaluates user reports and replay-approved automated evidence for Ledger. Canonical source identity prevents duplicate pipelines from being counted as independent corroboration.

How many people have reported Ledger issues today?

As of Sep 28, 2026 10:37 UTC, 0 users had reported issues with Ledger in the previous 24 hours.

How can I report a Ledger outage?

Click the "Report an issue" button on this page to submit an outage report. Reports are evaluated with moderation, baseline, and corroboration controls before they can support an incident.

Other

Is Ledger down right now?

Vendor-reported issueOfficial status last polled Sep 28, 2026 10:32 UTCwww.ledger.com Official status page

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

Is Ledger down right now?

Vendor-reported issue. Ledger: Stellar (XLM) Mainnet Degraded Service Affected scope is described in the vendor notice; service-wide impact is not established. Independent corroboration has not been established.

Status as of Sep 28, 2026 10:37 UTC

Vendor-reported issueVendor-reported issue

Ledger: vendor reports an issue

As of Sep 28, 2026 10:37 UTC

Stellar (XLM) Mainnet Degraded Service Affected scope is described in the vendor notice; service-wide impact is not established. Independent corroboration has not been established.

Recent qualified checks passed for Stellar Mainnet oldest available transaction read. These results cover only those operations; they do not establish overall service health.

Reports 24h

Last incident

Sep 28, 2026 08:41 UTC

Trend

0/15m

Monitoring

Operation checks passing

Observed health

100/100

2 of 2 assessed samples succeeded within their latency target.

5/5 responses validated in the last 15 minutes. 3 successful samples have no qualified latency target.

Evidence strength

Vendor-reported

An official notice is available; independent agreement is unproven.

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 Ledger.

Incident days

No recorded incident

453h 53m

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 Ledger. Hover a day for detail.

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

Days with incidents

3 incidents

Busiest day

453h 53m

Recorded duration

Report volume

0 reports in last 24H

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Ledger outage on September 25 2d 20h disruption

Sep 25, 12:17 PM → Sep 28, 08:41 AM · 2d 20h · medium

On September 25, 2026, the Ledger service experienced a disruption. This incident was detected via automated monitoring and resolved on September 28, 2026.

Peak reports

in 15 min

Total reports

during outage

Duration

2d 20h

until recovery

Impact

The Ledger service experienced a medium-severity disruption for 2 days and 20 hours. This incident was detected through automated signals, including the vendor's own status page. No user-reported data was collected for this incident, and therefore no specific user-visible features, regions, or issue types were identified.

Outage timeline

Sep 25, 12:17 PM
PulseWatch detected the incident from automated vendor and probe signals (medium severity)
Sep 25, 12:17 PM
Status updated: possible issue
Sep 28, 08:41 AM
Signals cleared — incident resolved

Official updates

Sep 25, 12:17 PM
Ledger status page acknowledged the incident.
View official source

Reliability

Detected by PulseWatch

30-day uptime

35.1%

90-day uptime

67.7%

Calculated from Ledger's detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.

Other other services we monitor

Browse all

Community reports

0 comments

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

Be the first to post a report.