by HonkWatch

Is JFrog down in Svalbard and Jan Mayen?

Planned maintenance at JFrog

Svalbard and Jan Mayen No reports in the last hour checked 2 min ago
JFrog has planned maintenance. Maintenance on Europe - West2 (London) - GCP / Artifactory. Updated 7 Nov, 02:27 UTC, 2 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 06:0012:0018:0000: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, 02:29 UTC

Report a problem with JFrog

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 JFrog

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

Free account required. JFrog 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 jfrog.io

Every 5 minutes, from our probes

Our checks from 35 cities: all fine.

Mumbai: loaded in 852 ms Frankfurt: loaded in 413 ms Los Angeles: loaded in 651 ms Jakarta: loaded in 1042 ms Melbourne: loaded in 884 ms São Paulo: loaded in 534 ms Warsaw: loaded in 516 ms St. Louis: loaded in 325 ms Bangalore: loaded in 1019 ms Santiago: loaded in 668 ms Tel Aviv: loaded in 570 ms Osaka: loaded in 718 ms Port Louis: loaded in 1697 ms Delhi: loaded in 1115 ms Tokyo: loaded in 646 ms London: loaded in 360 ms Sydney: loaded in 1342 ms Atlanta: loaded in 117 ms Johannesburg: loaded in 923 ms Hamina: loaded in 483 ms Madrid: loaded in 434 ms Cape Town: loaded in 1089 ms Doha: loaded in 1094 ms Querétaro: loaded in 375 ms Dallas: loaded in 406 ms Seattle: loaded in 327 ms Hong Kong: loaded in 816 ms New York: loaded in 76 ms Seoul: loaded in 775 ms Amsterdam: loaded in 366 ms New Jersey: loaded in 228 ms Singapore: loaded in 1017 ms Toronto: loaded in 164 ms Portsmouth: loaded in 399 ms Lauterbourg: loaded in 472 ms
  • MumbaiReachable852 ms, 2 min ago
  • FrankfurtReachable413 ms, 2 min ago
  • Los AngelesReachable651 ms, 2 min ago
  • JakartaReachable1042 ms, 2 min ago
  • MelbourneReachable884 ms, 2 min ago
  • São PauloReachable534 ms, 2 min ago
  • WarsawReachable516 ms, 2 min ago
  • St. LouisReachable325 ms, 2 min ago
  • BangaloreReachable1019 ms, 2 min ago
  • SantiagoReachable668 ms, 2 min ago
  • Tel AvivReachable570 ms, 2 min ago
  • OsakaReachable718 ms, 2 min ago
  • Port LouisReachable1697 ms, 2 min ago
  • DelhiReachable1115 ms, 2 min ago
  • TokyoReachable646 ms, 2 min ago
  • LondonReachable360 ms, 2 min ago
  • SydneyReachable1342 ms, 2 min ago
  • AtlantaReachable117 ms, 2 min ago
  • JohannesburgReachable923 ms, 2 min ago
  • HaminaReachable483 ms, 2 min ago
  • MadridReachable434 ms, 2 min ago
  • Cape TownReachable1089 ms, 2 min ago
  • DohaReachable1094 ms, 3 min ago
  • QuerétaroReachable375 ms, 3 min ago
  • DallasReachable406 ms, 3 min ago
  • SeattleReachable327 ms, 3 min ago
  • Hong KongReachable816 ms, 3 min ago
  • New YorkReachable76 ms, 3 min ago
  • SeoulReachable775 ms, 3 min ago
  • AmsterdamReachable366 ms, 3 min ago
  • New JerseyReachable228 ms, 3 min ago
  • SingaporeReachable1017 ms, 3 min ago
  • TorontoReachable164 ms, 3 min ago
  • PortsmouthReachable399 ms, 3 min ago
  • LauterbourgReachable472 ms, 3 min ago

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

Parts of JFrog

JFrog Cloud

Europe - West2 (London) - GCP

  • ArtifactoryMaintenance

401 other parts are working.

Incidents and maintenance

Maintenance

  • Planned Cloud Maintenance on Azure Canada Central (planned) 8 Nov, 07:00 UTC to 8 Nov, 08:00 UTC. Affects Artifactory, Security - Xray, Security - JAS, Security - Curation and 6 more · Details
  • Planned Cloud Maintenance on Azure Australia East (planned) 8 Nov, 07:00 UTC to 8 Nov, 08:00 UTC. Affects Artifactory, Security - Xray, Security - JAS, Security - Curation and 6 more · Details
  • Planned Cloud Maintenance on Azure Brazil South (planned) 8 Nov, 07:00 UTC to 8 Nov, 08:00 UTC. Affects Artifactory, Security - Xray, Security - JAS, Security - Curation and 6 more · Details
  • Planned Cloud Maintenance on Azure Israel Central (planned) 8 Nov, 07:00 UTC to 8 Nov, 08:00 UTC. Affects Artifactory, Security - Xray, Security - JAS, Security - Curation and 6 more · Details
  • Planned Cloud Maintenance on Azure West US (planned) 8 Nov, 07:00 UTC to 8 Nov, 08:00 UTC. Affects Artifactory, Security - Xray, Security - JAS, Security - Curation and 6 more · Details
  • Planned Cloud Maintenance on Azure North Central US (planned) 8 Nov, 07:00 UTC to 8 Nov, 08:00 UTC. Affects Artifactory, Security - Xray, Security - JAS, Security - Curation and 6 more · Details
  • Planned Cloud Maintenance on Azure West US 3 (planned) 8 Nov, 07:00 UTC to 8 Nov, 08:00 UTC. Affects Artifactory, Security - Xray, Security - JAS, Security - Curation and 6 more · Details
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, 6 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 jfrog.io that failed (9,644 checks). Its status page reported no problem in this time. Community reports appear separately above, alongside our checks and provider updates.

0%7%14% 06:0012:0018:0000:00 0% of 105 checks failed3% of 113 checks failed9% of 129 checks failed12% of 139 checks failed7% of 123 checks failed14% of 124 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 failed1% 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 104 checks failed0% of 105 checks failed0% of 98 checks failed0% of 99 checks failed0% of 100 checks failed0% of 105 checks failed0% of 103 checks failed0% of 87 checks failed0% of 82 checks failed0% of 107 checks failed0% of 97 checks failed0% of 100 checks failed0% of 104 checks failed0% of 98 checks failed0% of 82 checks failed0% of 88 checks failed0% of 101 checks failed0% of 100 checks failed0% of 86 checks failed0% of 87 checks failed0% of 85 checks failed0% of 92 checks failed0% of 93 checks failed0% of 86 checks failed0% of 85 checks failed0% of 84 checks failed0% of 86 checks failed0% of 80 checks failed0% of 81 checks failed0% of 82 checks failed0% of 78 checks failed0% of 86 checks failed2% of 90 checks failed0% of 107 checks failed0% of 96 checks failed0% of 79 checks failed0% of 102 checks failed0% of 104 checks failed0% of 101 checks failed0% of 83 checks failed0% of 108 checks failed0% of 96 checks failed0% of 85 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 85 checks failed0% of 102 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 failed

Recent problems

No problems recorded since 2 Nov 2026.

What can I try?

Having trouble with JFrog?

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

JFrog is doing planned maintenance, so some parts may not work right now. It is probably not just you.

How do we know?

We read the official JFrog status page and load jfrog.io 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 Developer tools

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