Live  /  Circle  /  Incident

Circle: xReserve: Delayed Withdrawals on Stacks Mainnet

Circle · circle.comMajor incidentResolved2026-10-27 14:45 UTC
Public — what happened

Summary

Circle said withdrawals through xReserve on Stacks Mainnet were delayed, a problem it began investigating on October 26, 2026 at 19:01 UTC and rated as major. About two hours later, Circle said it had found the cause, which it described as a problem with the data its systems use to check Stacks transactions, and that this could occasionally slow Stacks withdrawals. Circle said all affected withdrawals had been processed by then while it worked on a fix to prevent a repeat. The incident was marked resolved on October 27 at 14:45 UTC.

Affected

Circle xReserve - Stacks - Mainnet

As listed on Circle’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Circle against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Circle: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Circle report →

More from Circle

Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.

The full archive is on the Circle status & history page.

Related: Circle status & history. SquidGrid is not affiliated with Circle.