CryptoRoute

Polygon: Degraded affecting swap routes — resolved

Published Jul 13, 2026 · updated Jul 13, 2026 · source: CryptoRoute route monitoring

View live status →

Summary

CryptoRoute's route monitoring observed degraded conditions on Polygon. 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 Mon, Jul 13, 2026 6:02 PM UTC, our monitoring flagged Polygon as degraded based on a drop in synthetic quote success and/or elevated latency.

Update: the incident was resolved on Mon, Jul 13, 2026 8:16 PM UTC and Polygon returned to operational.

Why it matters for swaps

While the incident was active, routes touching Polygon 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.

Affected routes

  • USDT → USDC — major outage (100% quote success (n=12, last 90m))

  • USDT → USDT — major outage (100% quote success (n=12, last 90m))

Alternatives

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

  • wNEAR → ETH

  • wNEAR → AURORA

  • USDC → USDC

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