by HonkWatch

Is Iterable down in Svalbard and Jan Mayen?

No problems reported with Iterable right now

Svalbard and Jan Mayen No reports in the last hour checked just now
Iterable reports no current incident. Updated 6 Nov, 17:57 UTC, just now · 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:0018: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:57 UTC

Report a problem with Iterable

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 Iterable

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

Free account required. Iterable 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 iterable.com

Every 5 minutes, from our probes

Our checks from 35 cities: all fine.

Tel Aviv: loaded in 371 ms Frankfurt: loaded in 103 ms Dallas: loaded in 274 ms Tokyo: loaded in 557 ms Sydney: loaded in 24 ms Toronto: loaded in 75 ms Amsterdam: loaded in 30 ms Osaka: loaded in 26 ms Atlanta: loaded in 15 ms London: loaded in 43 ms Madrid: loaded in 217 ms Portsmouth: loaded in 38 ms Johannesburg: loaded in 24 ms Querétaro: loaded in 26 ms Lauterbourg: loaded in 615 ms Singapore: loaded in 23 ms Hong Kong: loaded in 208 ms Bangalore: loaded in 58 ms St. Louis: loaded in 70 ms Hamina: loaded in 43 ms Santiago: loaded in 66 ms Los Angeles: loaded in 88 ms Jakarta: loaded in 78 ms New York: loaded in 27 ms Mumbai: loaded in 23 ms Melbourne: loaded in 82 ms São Paulo: loaded in 47 ms Cape Town: loaded in 64 ms Warsaw: loaded in 90 ms Seoul: loaded in 28 ms New Jersey: loaded in 46 ms Seattle: loaded in 41 ms Port Louis: loaded in 242 ms Delhi: loaded in 16 ms Doha: loaded in 388 ms
  • Tel AvivReachable371 ms, just now
  • FrankfurtReachable103 ms, just now
  • DallasReachable274 ms, just now
  • TokyoReachable557 ms, just now
  • SydneyReachable24 ms, just now
  • TorontoReachable75 ms, just now
  • AmsterdamReachable30 ms, just now
  • OsakaReachable26 ms, just now
  • AtlantaReachable15 ms, just now
  • LondonReachable43 ms, 1 min ago
  • MadridReachable217 ms, 1 min ago
  • PortsmouthReachable38 ms, 1 min ago
  • JohannesburgReachable24 ms, 1 min ago
  • QuerétaroReachable26 ms, 2 min ago
  • LauterbourgReachable615 ms, 2 min ago
  • SingaporeReachable23 ms, 2 min ago
  • Hong KongReachable208 ms, 2 min ago
  • BangaloreReachable58 ms, 2 min ago
  • St. LouisReachable70 ms, 2 min ago
  • HaminaReachable43 ms, 2 min ago
  • SantiagoReachable66 ms, 2 min ago
  • Los AngelesReachable88 ms, 2 min ago
  • JakartaReachable78 ms, 2 min ago
  • New YorkReachable27 ms, 2 min ago
  • MumbaiReachable23 ms, 2 min ago
  • MelbourneReachable82 ms, 2 min ago
  • São PauloReachable47 ms, 2 min ago
  • Cape TownReachable64 ms, 2 min ago
  • WarsawReachable90 ms, 3 min ago
  • SeoulReachable28 ms, 3 min ago
  • New JerseyReachable46 ms, 3 min ago
  • SeattleReachable41 ms, 3 min ago
  • Port LouisReachable242 ms, 3 min ago
  • DelhiReachable16 ms, 3 min ago
  • DohaReachable388 ms, 6 min ago

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

Parts of Iterable

Iterable

All 488 listed parts are working.

Incidents and maintenance

No open incidents or planned maintenance.

Outage history

No problems recorded since 2 Nov 2026.

Last 9030 days

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

Of the last 90 days, 0 had a partial or major outage, 0 had maintenance only and 85 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 iterable.com that failed (9,660 checks). Its status page reported no problem in this time. Community reports appear separately above, alongside our checks and provider updates.

0%5%10% 18:0000:0006:0012:0018:00 0% of 94 checks failed0% of 104 checks failed0% of 105 checks failed0% of 105 checks failed0% of 96 checks failed0% of 102 checks failed0% of 89 checks failed0% of 105 checks failed0% of 99 checks failed0% of 95 checks failed0% of 106 checks failed0% of 106 checks failed0% of 105 checks failed0% of 105 checks failed0% of 102 checks failed0% of 105 checks failed0% of 107 checks failed0% of 103 checks failed0% of 107 checks failed0% of 104 checks failed0% of 104 checks failed0% of 105 checks failed0% of 108 checks failed0% of 104 checks failed0% of 104 checks failed0% of 106 checks failed0% of 105 checks failed0% of 106 checks failed0% of 105 checks failed0% of 104 checks failed0% of 105 checks failed0% of 106 checks failed0% of 106 checks failed0% of 103 checks failed0% of 106 checks failed0% of 105 checks failed0% of 105 checks failed0% of 103 checks failed0% of 108 checks failed0% of 104 checks failed0% of 105 checks failed0% of 104 checks failed0% of 105 checks failed0% of 105 checks failed0% of 107 checks failed0% of 103 checks failed0% of 105 checks failed0% of 105 checks failed0% of 106 checks failed0% of 104 checks failed0% of 105 checks failed0% of 106 checks failed0% of 103 checks failed0% of 107 checks failed0% of 104 checks failed0% of 103 checks failed0% of 109 checks failed0% of 103 checks failed0% of 106 checks failed0% of 105 checks failed0% of 104 checks failed0% of 103 checks failed0% of 104 checks failed0% of 97 checks failed0% of 104 checks failed0% of 99 checks failed0% of 103 checks failed0% of 107 checks failed0% of 90 checks failed0% of 83 checks failed0% of 102 checks failed0% of 101 checks failed0% of 100 checks failed0% of 101 checks failed1% of 102 checks failed0% of 92 checks failed0% of 87 checks failed0% of 94 checks failed0% of 98 checks failed0% of 95 checks failed0% of 86 checks failed0% of 91 checks failed0% of 85 checks failed0% of 100 checks failed0% of 87 checks failed0% of 86 checks failed0% of 89 checks failed0% of 84 checks failed0% of 87 checks failed0% of 78 checks failed0% of 86 checks failed0% of 93 checks failed0% of 97 checks failed0% of 90 checks failed0% of 105 checks failed0% of 104 checks failed

Recent problems

No problems recorded since 2 Nov 2026.

What can I try?

Having trouble with Iterable?

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

The Iterable status page reports no problem and our own checks reach iterable.com. This does not rule out problems with sign-in, payments, an app or a local network. Check the community reports above and report your experience.

How do we know?

We read the official Iterable status page and load iterable.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 2.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 Marketing

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