Live  /  Circle  /  Incident

Circle: CCTP Re-attestations - Delays/Degraded Performance

Circle · circle.comMinor incidentResolved2026-10-22 19:24 UTC
Public — what happened

Summary

Circle said that starting at 23:26 UTC on October 21, 2026, re-attestation requests on its Cross-Chain Transfer Protocol (CCTP) service were slow or partly unavailable for some customers. The company rated the issue as minor and said its team was looking into the root cause while working to get the service back to normal. The incident is now marked resolved as of 19:24 on October 22, and the text provided does not say what caused it.

Affected

Attestation Service

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 44, 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.