← HonkWatch.com

Is Circle (USDC) down in Svalbard and Jan Mayen?

Circle (USDC) has problems

Svalbard and Jan Mayen No reports in the last hour checked 3 min ago
Partial outage reported by Circle (USDC) 3 of 341 parts affected: Circle Cross-Chain Transfer Protocol / CRONOS - Cross-Chain Minting and Burning, Circle Testnet Faucet / Public Faucet – NOBLE Testnet, 3rd Party Infrastructure & Systems. Going on for 5 d 6 h. Updated 7 Nov, 16:59 UTC, 3 min ago · Official status page
Report a problem
Change country

Reports from people in Svalbard and Jan Mayen

Last 24 hours · Svalbard and Jan Mayen · times in UTC

0 reports

No community reports in the last 24 hours from Svalbard and Jan Mayen. Having trouble? Add your report.

024 18:0000:0006:0012:00

Bars: reports every 15 minutes. Reports alone do not confirm an outage; a flat chart does not prove everything works.

Report totals as of 7 Nov, 17:02 UTC

Report a problem with Circle (USDC)

Choose where you are, then tap what isn't working. Tapping a problem sends your report; no account needed.

What isn't working? Tap one to send

Anonymous · one report per service per hour. This adds your experience to the chart; the provider is not contacted.

Compare worldwide reports · Other services in Svalbard and Jan Mayen

Where this status comes from

Provider updates and website checks — Worldwide

The evidence below covers the provider and our available checks. It is not a separate verdict for Svalbard and Jan Mayen. The report chart above is filtered to Svalbard and Jan Mayen.

Our own checks of circle.com

Every 5 minutes, from our probes

Our checks from 35 cities: all fine.

Warsaw: loaded in 192 ms New Jersey: loaded in 226 ms Amsterdam: loaded in 287 ms Querétaro: loaded in 200 ms Madrid: loaded in 142 ms Port Louis: loaded in 144 ms Seattle: loaded in 262 ms Singapore: loaded in 154 ms London: loaded in 313 ms Bangalore: loaded in 334 ms Frankfurt: loaded in 132 ms Jakarta: loaded in 131 ms Hong Kong: loaded in 488 ms Portsmouth: loaded in 244 ms Los Angeles: loaded in 333 ms Santiago: loaded in 143 ms Cape Town: loaded in 503 ms Atlanta: loaded in 129 ms Tel Aviv: loaded in 555 ms São Paulo: loaded in 148 ms Melbourne: loaded in 270 ms Toronto: loaded in 170 ms Dallas: loaded in 409 ms Doha: loaded in 992 ms Hamina: loaded in 229 ms Sydney: loaded in 171 ms St. Louis: loaded in 196 ms Mumbai: loaded in 182 ms Tokyo: loaded in 209 ms Johannesburg: loaded in 279 ms Seoul: loaded in 377 ms Osaka: loaded in 138 ms Delhi: loaded in 132 ms New York: loaded in 152 ms Lauterbourg: loaded in 183 ms
  • WarsawReachable192 ms, just now
  • New JerseyReachable226 ms, just now
  • AmsterdamReachable287 ms, just now
  • QuerétaroReachable200 ms, just now
  • MadridReachable142 ms, just now
  • Port LouisReachable144 ms, just now
  • SeattleReachable262 ms, just now
  • SingaporeReachable154 ms, just now
  • LondonReachable313 ms, just now
  • BangaloreReachable334 ms, just now
  • FrankfurtReachable132 ms, just now
  • JakartaReachable131 ms, just now
  • Hong KongReachable488 ms, just now
  • PortsmouthReachable244 ms, just now
  • Los AngelesReachable333 ms, just now
  • SantiagoReachable143 ms, just now
  • Cape TownReachable503 ms, just now
  • AtlantaReachable129 ms, just now
  • Tel AvivReachable555 ms, 1 min ago
  • São PauloReachable148 ms, 4 min ago
  • MelbourneReachable270 ms, 4 min ago
  • TorontoReachable170 ms, 4 min ago
  • DallasReachable409 ms, 4 min ago
  • DohaReachable992 ms, 4 min ago
  • HaminaReachable229 ms, 5 min ago
  • SydneyReachable171 ms, 5 min ago
  • St. LouisReachable196 ms, 5 min ago
  • MumbaiReachable182 ms, 5 min ago
  • TokyoReachable209 ms, 5 min ago
  • JohannesburgReachable279 ms, 5 min ago
  • SeoulReachable377 ms, 5 min ago
  • OsakaReachable138 ms, 5 min ago
  • DelhiReachable132 ms, 5 min ago
  • New YorkReachable152 ms, 5 min ago
  • LauterbourgReachable183 ms, 5 min ago

This is separate from the status page: we request circle.com and note whether it answers. These automated checks do not sign in or use the app's features.

Parts of Circle (USDC)

Circle

Circle Testnet Faucet

  • Public Faucet – NOBLE TestnetMajor outage

Circle Cross-Chain Transfer Protocol

  • CRONOS - Cross-Chain Minting and BurningPartial outage

Other parts

  • 3rd Party Infrastructure & SystemsPartial outage

338 other parts are working.

Incidents and maintenance

Open incidents

  • Circle is discontinuing support for USDC and CCTP V1 on Noble in a phased transition (monitoring) Since 10 Sep 2026, 16:02 UTC. Affects NOBLE - Cross-Chain Minting and Burning, USDC - NOBLE - Minting, USDC - NOBLE - Redeeming · Details
  • Noble Testnet network outage (investigating) Since 17 Sep 2026, 13:07 UTC. Affects Circle CCTP - Sandbox, Circle Mint - Sandbox, Public Faucet – NOBLE Testnet, 3rd Party Infrastructure & Systems · Details
  • Circle is discontinuing support for USDC on TRON in a phased transition (monitoring) Since 20 Feb 2024, 12:00 UTC · Details

Maintenance

  • Stellar Testnet Reset Q4 - Dec 17 2026 (planned) 17 Dec 2026, 19:38 UTC to 17 Dec 2026, 20:38 UTC. Affects Circle Mint - Sandbox, 3rd Party Infrastructure & Systems, Public Faucet – XLM Testnet · Details
Outage history

Last 9030 days

0.00% of the time without a reported outage, since 2 Nov

Of the last 90 days, 6 had a partial or major outage, 0 had maintenance only and 84 have no data. Recent problems are listed in a table further down.

90 days ago30 days agoToday

No problems Partial outage Major outage Maintenance No data yet

Last 24 hours

Every 15 minutes, hours in UTC

Bars: the share of our own checks of circle.com that failed (9,837 checks). Shaded: when Circle (USDC)'s status page reported a problem. Community reports appear separately above, alongside our checks and provider updates.

0%5%10% 18:0000:0006:0012:00 0% of 85 checks failed0% of 107 checks failed0% of 96 checks failed0% of 89 checks failed0% of 102 checks failed0% of 104 checks failed0% of 99 checks failed0% of 76 checks failed0% of 112 checks failed0% of 101 checks failed0% of 82 checks failed0% of 96 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 86 checks failed0% of 99 checks failed0% of 105 checks failed0% of 101 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 106 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 1 checks failed

Recent problems

2 Nov, 10:47 UTCPartial outagegoing on, 5 d 6 h3 of 341 parts affected: Circle Cross-Chain Transfer Protocol / CRONOS - Cross-Chain Minting and Burning, Circle Testnet Faucet / Public Faucet – NOBLE Testnet, 3rd Party Infrastructure & Systems
What can I try?

Having trouble with Circle (USDC)?

  1. Compare reports from Svalbard and Jan Mayen and check the latest update above. A quiet chart does not rule out a new or local problem.
  2. Try the service on another device or switch between WiFi and mobile data, if available. If other sites also fail, check your internet provider.
  3. Report a problem with the feature that is failing and the country where you are affected. Submit once; your report appears in the chart.

Reports describe people's experiences. One report alone does not confirm an outage.

Questions about these results

Questions

Is Circle (USDC) down, or is it just me?

Circle (USDC) itself reports a problem right now, so it is probably not just you.

How do we know?

We read the official Circle (USDC) status page and load circle.com from our own probes in several cities. People can also report problems here. Their reports appear separately and may reveal issues before a provider update.

How often do we check?

The status page every 7.5 minutes, day and night, and the website every 5 minutes. We keep 90 days of history: a day we have no reading for shows as "no data yet", never as working.

More in Payments and shops

See the live outage feed for Svalbard and Jan Mayen · Find another service