by HonkWatch

Is Chainstack down in Svalbard and Jan Mayen?

Chainstack has problems

Svalbard and Jan Mayen No reports in the last hour checked 13 min ago
Partial outage reported by Chainstack Open incident: TON Mainnet - incomplete data on some historical trace queries. Going on for 3 d 8 h. Updated 6 Nov, 16:59 UTC, 13 min ago · Official status page
Report a problemFollow community reports
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 6 Nov, 17:12 UTC

Report a problem with Chainstack

Having trouble? Tap what isn't working. No account needed.

What isn't working?

Anonymous · one report per service per hour. This adds your experience to the chart, without contacting the provider or subscribing you to alerts.

Compare worldwide reports · Other services in Svalbard and Jan Mayen

Monitor the provider status with HonkWatch

Get monitoring alerts for Chainstack

HonkWatch watches the Chainstack status page for you and alerts you by email, Slack, Discord or Telegram when it reports a problem.

Free account required. Chainstack is selected on the next page. Review the monitor and choose where alerts go. Community reports do not trigger these monitoring alerts.

Start free Log in

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 chainstack.com

Every 5 minutes, from our probes

Our checks from 35 cities: all fine.

Cape Town: loaded in 109 ms São Paulo: loaded in 116 ms Singapore: loaded in 104 ms Amsterdam: loaded in 127 ms Madrid: loaded in 81 ms St. Louis: loaded in 400 ms Johannesburg: loaded in 74 ms Doha: loaded in 391 ms Melbourne: loaded in 122 ms London: loaded in 108 ms Sydney: loaded in 97 ms Delhi: loaded in 70 ms Seoul: loaded in 117 ms Los Angeles: loaded in 176 ms Portsmouth: loaded in 205 ms Warsaw: loaded in 81 ms Lauterbourg: loaded in 393 ms Toronto: loaded in 126 ms Tel Aviv: loaded in 73 ms Hong Kong: loaded in 86 ms Bangalore: loaded in 156 ms Atlanta: loaded in 102 ms Tokyo: loaded in 463 ms Osaka: loaded in 98 ms New York: loaded in 86 ms Querétaro: loaded in 74 ms Santiago: loaded in 76 ms Jakarta: loaded in 89 ms Seattle: loaded in 143 ms Port Louis: loaded in 124 ms New Jersey: loaded in 206 ms Frankfurt: loaded in 105 ms Mumbai: loaded in 88 ms Dallas: loaded in 124 ms Hamina: loaded in 122 ms
  • Cape TownReachable109 ms, just now
  • São PauloReachable116 ms, just now
  • SingaporeReachable104 ms, just now
  • AmsterdamReachable127 ms, just now
  • MadridReachable81 ms, 1 min ago
  • St. LouisReachable400 ms, 1 min ago
  • JohannesburgReachable74 ms, 2 min ago
  • DohaReachable391 ms, 2 min ago
  • MelbourneReachable122 ms, 2 min ago
  • LondonReachable108 ms, 2 min ago
  • SydneyReachable97 ms, 2 min ago
  • DelhiReachable70 ms, 2 min ago
  • SeoulReachable117 ms, 2 min ago
  • Los AngelesReachable176 ms, 2 min ago
  • PortsmouthReachable205 ms, 2 min ago
  • WarsawReachable81 ms, 2 min ago
  • LauterbourgReachable393 ms, 3 min ago
  • TorontoReachable126 ms, 3 min ago
  • Tel AvivReachable73 ms, 3 min ago
  • Hong KongReachable86 ms, 4 min ago
  • BangaloreReachable156 ms, 4 min ago
  • AtlantaReachable102 ms, 4 min ago
  • TokyoReachable463 ms, 4 min ago
  • OsakaReachable98 ms, 4 min ago
  • New YorkReachable86 ms, 4 min ago
  • QuerétaroReachable74 ms, 4 min ago
  • SantiagoReachable76 ms, 5 min ago
  • JakartaReachable89 ms, 5 min ago
  • SeattleReachable143 ms, 6 min ago
  • Port LouisReachable124 ms, 7 min ago
  • New JerseyReachable206 ms, 7 min ago
  • FrankfurtReachable105 ms, 8 min ago
  • MumbaiReachable88 ms, 9 min ago
  • DallasReachable124 ms, 10 min ago
  • HaminaReachable122 ms, 11 min ago

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

Parts of Chainstack

Solana Global Nodes

  • Solana MainnetMaintenance

Solana Trader Nodes

  • Solana Mainnet Full (Chainstack Cloud, Frankfurt)Maintenance
  • Solana Mainnet Full (Chainstack Cloud, New York)Maintenance

137 other parts are working.

Incidents and maintenance

Open incidents

  • TON Mainnet - incomplete data on some historical trace queries (identified) Since 27 Aug 2026, 10:35 UTC. Affects TON Mainnet API v3 · Details
Outage history

Last 9030 days

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

Of the last 90 days, 4 had a partial or major outage, 0 had maintenance only and 86 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 chainstack.com that failed (9,693 checks). Shaded: when Chainstack'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 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 95 checks failed0% of 110 checks failed0% of 104 checks failed0% of 105 checks failed0% of 100 checks failed0% of 104 checks failed0% of 95 checks failed0% of 105 checks failed0% of 94 checks failed0% of 100 checks failed0% of 107 checks failed0% of 105 checks failed1% of 108 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 104 checks failed0% of 104 checks failed0% of 97 checks failed0% of 103 checks failed0% of 103 checks failed0% of 102 checks failed0% of 104 checks failed0% of 87 checks failed0% of 77 checks failed0% of 108 checks failed0% of 99 checks failed0% of 103 checks failed0% of 99 checks failed0% of 99 checks failed0% of 83 checks failed0% of 91 checks failed0% of 88 checks failed0% of 106 checks failed0% of 87 checks failed0% of 90 checks failed0% of 98 checks failed0% of 102 checks failed0% of 99 checks failed0% of 84 checks failed0% of 80 checks failed0% of 96 checks failed0% of 79 checks failed0% of 100 checks failed0% of 76 checks failed0% of 85 checks failed0% of 85 checks failed0% of 88 checks failed

Recent problems

3 Nov, 08:34 UTCPartial outagegoing on, 3 d 8 hOpen incident: TON Mainnet - incomplete data on some historical trace queries
What can I try?

Having trouble with Chainstack?

  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 Chainstack down, or is it just me?

Chainstack itself reports a problem right now, so it is probably not just you.

How do we know?

We read the official Chainstack status page and load chainstack.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 15 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 Crypto and web3

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