Sui: Degraded affecting swap routes — resolved

Summary

CryptoRoute's route monitoring observed degraded conditions on Sui. The incident is resolved; this page records the affected routes, the observed impact and the timeline.

What happened

CryptoRoute continuously probes the health of its swap routes. On Thu, Aug 27, 2026 7:06 AM UTC, our monitoring flagged Sui as degraded based on a drop in synthetic quote success and/or elevated latency.

Update: the incident was resolved on Thu, Aug 27, 2026 8:37 AM UTC and Sui returned to operational.

Why it matters for swaps

While the incident was active, routes touching Sui may have quoted more slowly, failed more often, or been temporarily unavailable. Swaps are non-custodial and refundable, but it is always worth checking status before sending funds.

Alternatives

These routes that also touch Sui were operational at the time of writing — they share the same network, so check the live status before using them:

• wNEAR → ZEC

• USDC → SUI

The safest option is usually to wait for status to return to operational, or to use a route that avoids the affected network entirely (a different destination chain or asset).

What to check before you swap

• Confirm the current status on the Sui status page.

• Verify your recipient address is correct for the destination network.

• Do not resend a transaction while a previous one is still processing.

Sources & methodology

Source: CryptoRoute internal route monitoring. Status and impact are derived from synthetic quote probes and real swap outcomes; see our methodology. Numbers are shown only when the sample size supports them.