# SonarCloud.io cannot be resolved **URL:** \ **Category:** SonarQube Cloud\ **Tags:** incident\ **Created:** [January 26, 2023, 12:51pm UTC](https://community.sonarsource.com/t/sonarcloud-io-cannot-be-resolved/82444 "2023-01-26T12:51:10Z")\ **Posts on this page:** 18\ **Page:** 1
**Author:** ![ganncamp](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ganncamp/32/1261_2.png) [@ganncamp](https://community.sonarsource.com/u/ganncamp)\ **Post date:** [January 26, 2023, 12:51pm UTC](https://community.sonarsource.com/t/sonarcloud-io-cannot-be-resolved/82444/1 "2023-01-26T12:51:11Z")
[12:02 p.m. EST] This incident has been resolved. Our DNS provider has resolved an issue on its side and our monitoring shows that normal traffic has resumed. We apologize for the inconvenience. * * * [11:02 a.m. EST] **Current status** : We have expanded our DNS name service level and are seeing positive indications. Please respond here with your CI provider and region, if available, if you are still experiencing failures **Root causes** : We are continuing to investigate root causes, but our DNS provider has just reported a major incident. **Symptoms** : DNS for some CI providers was failing to resolve [SonarCloud.io](http://SonarCloud.io), which caused analysis to fail.   Again, please respond here if you’re still experiencing problems. It will be helpful to know your CI provider and region. * * * [7:51 a.m. EST] Hi all, [SonarCloud.io](http://sonarcloud.io/) cannot be resolved by some of our customers. As a consequence, static analysis cannot be performed. Our engineering teams are currently troubleshooting this issue with top priority. Preliminary investigations are pointing to a DNS issue. I have consolidated reports of this outage here in this thread so there is a single, central place to go for updates. As we know more, we’ll add it here. Please use the bell (🔔) icon to subscribe to updates on this thread. You can also watch [https://sonarcloud.statuspage.io/](https://sonarcloud.statuspage.io/)   Ann ---
**Author:** ![Ludovic\_Havet](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ludovic_havet/32/28349_2.png) [@Ludovic\_Havet](https://community.sonarsource.com/u/Ludovic_Havet)\ **Post date:** [January 26, 2023, 9:29am UTC](https://community.sonarsource.com/t/sonarcloud-io-cannot-be-resolved/82444/2 "2023-01-26T09:29:38Z")
Hello, Our CI is down with this message: ERROR: SonarCloud server [[https://sonarcloud.io]](https://sonarcloud.io%5D/) can not be reached Sonar cloud status page is green. The website seems to work fine. Is there an issue? Regards Ludovic ---
**Author:** ![Daniel\_Vockler](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/daniel_vockler/32/41218_2.png) [@Daniel\_Vockler](https://community.sonarsource.com/u/Daniel_Vockler)\ **Post date:** [January 26, 2023, 9:32am UTC](https://community.sonarsource.com/t/sonarcloud-io-cannot-be-resolved/82444/3 "2023-01-26T09:32:01Z")
Hi together, since about yesterday afternoon, we see constantly the issue that SonarCloud can not be reached: ```auto Using docker image sonarsource/sonar-scanner-cli:latest ... [30](#L30)$ sonar-scanner [31](#L31)INFO: Scanner configuration file: /opt/sonar-scanner/conf/sonar-scanner.properties [32](#L32)INFO: Project root configuration file: /builds/xyz/MASKED/sonar-project.properties [33](#L33)INFO: SonarScanner 4.8.0.2856 [34](#L34)INFO: Java 11.0.18 Alpine (64-bit) [35](#L35)INFO: Linux 5.4.109+ amd64 [36](#L36)INFO: User cache: /builds/xyz/MASKED/.sonar/cache [37](#L37)ERROR: SonarCloud server https://sonarcloud.io can not be reached ``` If anyone can help - would be happy to have an answer! ---
**Author:** ![aminebensalem](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/aminebensalem/32/41337_2.png) [@aminebensalem](https://community.sonarsource.com/u/aminebensalem)\ **Post date:** [January 26, 2023, 10:12am UTC](https://community.sonarsource.com/t/sonarcloud-io-cannot-be-resolved/82444/4 "2023-01-26T10:12:10Z")
Witnessing the same thing. It started yesterday in sync with the AZURE networking outage I believe. Then it came back up, but I guess it’s back to being “down” this morning. Not sure why the status page is not reporting anything. ---
**Author:** ![aminebensalem](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/aminebensalem/32/41337_2.png) [@aminebensalem](https://community.sonarsource.com/u/aminebensalem)\ **Post date:** [January 26, 2023, 10:13am UTC](https://community.sonarsource.com/t/sonarcloud-io-cannot-be-resolved/82444/5 "2023-01-26T10:13:58Z")
We are witnessing the same thing when trying to run scans from jenkins. ---
**Author:** ![aminebensalem](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/aminebensalem/32/41337_2.png) [@aminebensalem](https://community.sonarsource.com/u/aminebensalem)\ **Post date:** [January 26, 2023, 10:20am UTC](https://community.sonarsource.com/t/sonarcloud-io-cannot-be-resolved/82444/6 "2023-01-26T10:20:34Z")
We are witnessing issues when running sonar scans as part of our CI pipelines. The scanner fails with the following error: ```auto 10:00:23.131 DEBUG: Extract sonar-scanner-api-batch in temp... 10:00:23.136 DEBUG: Get bootstrap index... 10:00:23.136 DEBUG: Download: https://sonarcloud.io/batch/index 10:00:29.196 ERROR: SonarCloud server [https://sonarcloud.io] can not be reached 10:00:29.197 INFO: ------------------------------------------------------------------------ 10:00:29.197 INFO: EXECUTION FAILURE 10:00:29.197 INFO: ------------------------------------------------------------------------ 10:00:29.198 INFO: Total time: 6.627s 10:00:29.219 INFO: Final Memory: 8M/887M 10:00:29.219 INFO: ------------------------------------------------------------------------ 10:00:29.219 ERROR: Error during SonarScanner execution org.sonarsource.scanner.api.internal.ScannerException: Unable to execute SonarScanner analysis at org.sonarsource.scanner.api.internal.IsolatedLauncherFactory.lambda$createLauncher$0(IsolatedLauncherFactory.java:85) at java.base/java.security.AccessController.doPrivileged(Native Method) at org.sonarsource.scanner.api.internal.IsolatedLauncherFactory.createLauncher(IsolatedLauncherFactory.java:74) at org.sonarsource.scanner.api.internal.IsolatedLauncherFactory.createLauncher(IsolatedLauncherFactory.java:70) at org.sonarsource.scanner.api.EmbeddedScanner.doStart(EmbeddedScanner.java:185) at org.sonarsource.scanner.api.EmbeddedScanner.start(EmbeddedScanner.java:123) at org.sonarsource.scanner.cli.Main.execute(Main.java:74) at org.sonarsource.scanner.cli.Main.main(Main.java:62) Caused by: java.lang.IllegalStateException: Fail to get bootstrap index from server at org.sonarsource.scanner.api.internal.BootstrapIndexDownloader.getIndex(BootstrapIndexDownloader.java:42) at org.sonarsource.scanner.api.internal.JarDownloader.getScannerEngineFiles(JarDownloader.java:58) at org.sonarsource.scanner.api.internal.JarDownloader.download(JarDownloader.java:53) at org.sonarsource.scanner.api.internal.IsolatedLauncherFactory.lambda$createLauncher$0(IsolatedLauncherFactory.java:76) ... 7 more Caused by: java.net.UnknownHostException: sonarcloud.io: Temporary failure in name resolution at java.base/java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method) at java.base/java.net.InetAddress$PlatformNameService.lookupAllHostAddr(Unknown Source) at java.base/java.net.InetAddress.getAddressesFromNameService(Unknown Source) at java.base/java.net.InetAddress$NameServiceAddresses.get(Unknown Source) at java.base/java.net.InetAddress.getAllByName0(Unknown Source) at java.base/java.net.InetAddress.getAllByName(Unknown Source) at java.base/java.net.InetAddress.getAllByName(Unknown Source) at org.sonarsource.scanner.api.internal.shaded.okhttp.Dns.lambda$static$0(Dns.java:39) at org.sonarsource.scanner.api.internal.shaded.okhttp.internal.connection.RouteSelector.resetNextInetSocketAddress(RouteSelector.java:171) at org.sonarsource.scanner.api.internal.shaded.okhttp.internal.connection.RouteSelector.nextProxy(RouteSelector.java:135) at org.sonarsource.scanner.api.internal.shaded.okhttp.internal.connection.RouteSelector.next(RouteSelector.java:84) at org.sonarsource.scanner.api.internal.shaded.okhttp.internal.connection.ExchangeFinder.findConnection(ExchangeFinder.java:187) at org.sonarsource.scanner.api.internal.shaded.okhttp.internal.connection.ExchangeFinder.findHealthyConnection(ExchangeFinder.java:108) at org.sonarsource.scanner.api.internal.shaded.okhttp.internal.connection.ExchangeFinder.find(ExchangeFinder.java:88) at org.sonarsource.scanner.api.internal.shaded.okhttp.internal.connection.Transmitter.newExchange(Transmitter.java:169) at org.sonarsource.scanner.api.internal.shaded.okhttp.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.java:41) at org.sonarsource.scanner.api.internal.shaded.okhttp.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:142) at org.sonarsource.scanner.api.internal.shaded.okhttp.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:117) at org.sonarsource.scanner.api.internal.shaded.okhttp.internal.cache.CacheInterceptor.intercept(CacheInterceptor.java:94) at org.sonarsource.scanner.api.internal.shaded.okhttp.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:142) at org.sonarsource.scanner.api.internal.shaded.okhttp.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:117) at org.sonarsource.scanner.api.internal.shaded.okhttp.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.java:93) at org.sonarsource.scanner.api.internal.shaded.okhttp.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:142) at org.sonarsource.scanner.api.internal.shaded.okhttp.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:88) at org.sonarsource.scanner.api.internal.shaded.okhttp.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:142) at org.sonarsource.scanner.api.internal.shaded.okhttp.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:117) at org.sonarsource.scanner.api.internal.shaded.okhttp.RealCall.getResponseWithInterceptorChain(RealCall.java:221) at org.sonarsource.scanner.api.internal.shaded.okhttp.RealCall.execute(RealCall.java:81) at org.sonarsource.scanner.api.internal.ServerConnection.callUrl(ServerConnection.java:115) at org.sonarsource.scanner.api.internal.ServerConnection.downloadString(ServerConnection.java:99) at org.sonarsource.scanner.api.internal.BootstrapIndexDownloader.getIndex(BootstrapIndexDownloader.java:39) ``` The status page is not reporting any incidents and it seems that other people in the communicty are facing the same issues. Any idea of what’s happening or what was recently upgraded ? Thanks, Amine ---
**Author:** ![AlxO](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/alxo/32/3225_2.png) [@AlxO](https://community.sonarsource.com/u/AlxO)\ **Post date:** [January 26, 2023, 11:17am UTC](https://community.sonarsource.com/t/sonarcloud-io-cannot-be-resolved/82444/7 "2023-01-26T11:17:32Z")
Hi @aminebensalem Indeed the error message indicates some DNS issues somewhere: `Caused by: java.net.UnknownHostException: sonarcloud.io: Temporary failure in name resolution` At the time I write `sonarcloud.io` is taking requests normally, both UI and APIs. ---
**Author:** ![afmjr](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/afmjr/32/41344_2.png) [@afmjr](https://community.sonarsource.com/u/afmjr)\ **Post date:** [January 26, 2023, 11:35am UTC](https://community.sonarsource.com/t/sonarcloud-io-cannot-be-resolved/82444/8 "2023-01-26T11:35:58Z")
We are also experiencing that issue, running the action sonarsource/sonarqube-scan-action on GitHub and getting the following exception: Caused by: java.net.UnknownHostException: [sonarcloud.io](http://sonarcloud.io): Try again However, when we run it from Gradle using the sonarqube plugin, pointing to the same url anda different project, it works fine. ---
**Author:** ![Sandro\_Lange](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/sandro_lange/32/41348_2.png) [@Sandro\_Lange](https://community.sonarsource.com/u/Sandro_Lange)\ **Post date:** [January 26, 2023, 11:59am UTC](https://community.sonarsource.com/t/sonarcloud-io-cannot-be-resolved/82444/9 "2023-01-26T11:59:41Z")
We have the same issues in our gitlab pipelines. We let the gitlab support staff check our pipelines and they verified a DNS configuration issue on sonarcloud’s side. However, it seems that when we use different gitlab runners running in AWS they don’t seem to have troubles connecting to [sonarcloud.io](http://sonarcloud.io) while the google cloud based gitlab shared runners do have problems. ---
**Author:** ![Matous\_til](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/matous_til/32/41346_2.png) [@Matous\_til](https://community.sonarsource.com/u/Matous_til)\ **Post date:** [January 26, 2023, 12:04pm UTC](https://community.sonarsource.com/t/sonarcloud-io-cannot-be-resolved/82444/10 "2023-01-26T12:04:09Z")
Same here in GitLab cloud pipelines. Also badges from SonarCloud are not working in GitLab ---
**Author:** ![aminebensalem](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/aminebensalem/32/41337_2.png) [@aminebensalem](https://community.sonarsource.com/u/aminebensalem)\ **Post date:** [January 26, 2023, 12:04pm UTC](https://community.sonarsource.com/t/sonarcloud-io-cannot-be-resolved/82444/11 "2023-01-26T12:04:37Z")
Did the DNS configuration for [sonarcloud.io](http://sonarcloud.io) change recently? I am able to resolve [sonarcloud.io](http://sonarcloud.io) on my laptop, I can access the UI and I can ping the API. However, the dns resolution fails in our Kubernetes clusters hosted in Azure. I believe not only Azure infrastructure is affected, as people are facing the same issue on different cloud providers. So I can only assume this is from sonarcloud’s side. ---
**Author:** ![OBINNA](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/obinna/32/41351_2.png) [@OBINNA](https://community.sonarsource.com/u/OBINNA)\ **Post date:** [January 26, 2023, 12:07pm UTC](https://community.sonarsource.com/t/sonarcloud-io-cannot-be-resolved/82444/12 "2023-01-26T12:07:26Z")
the same issue we are facing on GitHub Actions Managed Runners. It is not resolving ```shell ERROR: SonarCloud server [https://sonarcloud.io] can not be reached INFO: ------------------------------------------------------------------------ INFO: EXECUTION FAILURE INFO: ------------------------------------------------------------------------ INFO: Total time: 5.347s INFO: Final Memory: 3M/17M ERROR: Error during SonarScanner execution INFO: ------------------------------------------------------------------------ org.sonarsource.scanner.api.internal.ScannerException: Unable to execute SonarScanner analysis at org.sonarsource.scanner.api.internal.IsolatedLauncherFactory.lambda$createLauncher$0(IsolatedLauncherFactory.java:85) at java.base/java.security.AccessController.doPrivileged(Native Method) at org.sonarsource.scanner.api.internal.IsolatedLauncherFactory.createLauncher(IsolatedLauncherFactory.java:74) at org.sonarsource.scanner.api.internal.IsolatedLauncherFactory.createLauncher(IsolatedLauncherFactory.java:70) at org.sonarsource.scanner.api.EmbeddedScanner.doStart(EmbeddedScanner.java:185) at org.sonarsource.scanner.api.EmbeddedScanner.start(EmbeddedScanner.java:123) at org.sonarsource.scanner.cli.Main.execute(Main.java:73) at org.sonarsource.scanner.cli.Main.main(Main.java:61) Caused by: java.lang.IllegalStateException: Fail to get bootstrap index from server at org.sonarsource.scanner.api.internal.BootstrapIndexDownloader.getIndex(BootstrapIndexDownloader.java:42) at org.sonarsource.scanner.api.internal.JarDownloader.getScannerEngineFiles(JarDownloader.java:58) at org.sonarsource.scanner.api.internal.JarDownloader.download(JarDownloader.java:53) at org.sonarsource.scanner.api.internal.IsolatedLauncherFactory.lambda$createLauncher$0(IsolatedLauncherFactory.java:76) ... 7 more ``` ---
**Author:** ![ganncamp](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ganncamp/32/1261_2.png) [@ganncamp](https://community.sonarsource.com/u/ganncamp)\ **Post date:** [January 26, 2023, 12:52pm UTC](https://community.sonarsource.com/t/sonarcloud-io-cannot-be-resolved/82444/13 "2023-01-26T12:52:50Z")
Hi all, Thanks for your reports of this issue. They helped us spot the problem and begin to understand the scope. I’ve consolidated all the reports in this new thread I created so there’s one place to go for updates. As we know more, we’ll update it here.   Ann ---
**Author:** ![ganncamp](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ganncamp/32/1261_2.png) [@ganncamp](https://community.sonarsource.com/u/ganncamp)\ **Post date:** [January 26, 2023, 12:55pm UTC](https://community.sonarsource.com/t/sonarcloud-io-cannot-be-resolved/82444/14 "2023-01-26T12:55:22Z")
---
**Author:** ![Mikkel](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/mikkel/32/10222_2.png) [@Mikkel](https://community.sonarsource.com/u/Mikkel)\ **Post date:** [January 26, 2023, 1:27pm UTC](https://community.sonarsource.com/t/sonarcloud-io-cannot-be-resolved/82444/15 "2023-01-26T13:27:02Z")
Hi, According to your status page the API is suppose to be “Operational”, however when calling an endpoint like: [POST] [https://sonarcloud.io/api/projects/create?name=\*\*\*&organization=\*\*\*&project=\*\*\*&visibility=private](https://sonarcloud.io/api/projects/create?name= ***&organization=*** &project=***&visibility=private) Then: “No such host is known.” is returned. I assume it is releated? Other api endpoints like: [GET] [https://sonarcloud.io/api/components/show?organization=\*\*\*&component=\*\*\*&qualifiers=TRK](https://sonarcloud.io/api/components/show?organization= ***&component=*** &qualifiers=TRK) is working. ---
**Author:** ![ganncamp](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ganncamp/32/1261_2.png) [@ganncamp](https://community.sonarsource.com/u/ganncamp)\ **Post date:** [January 26, 2023, 4:03pm UTC](https://community.sonarsource.com/t/sonarcloud-io-cannot-be-resolved/82444/16 "2023-01-26T16:03:47Z")
Hi all, I’ve updated the inital post with this, but I’m also adding it as a reply so notifications are sent: * * * **Current status** : We have expanded our DNS name service level and are seeing positive indications. Please respond here with your CI provider and region, if available, if you are still experiencing failures **Root causes** : We are continuing to investigate root causes, but our DNS provider has just reported a major incident. **Symptoms** : DNS for some CI providers was failing to resolve [SonarCloud.io](http://SonarCloud.io), which caused analysis to fail.   Again, please respond here if you’re still experiencing problems. It will be helpful to know your CI provider and region.   Thx, Ann ---
**Author:** ![ganncamp](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ganncamp/32/1261_2.png) [@ganncamp](https://community.sonarsource.com/u/ganncamp)\ **Post date:** [January 26, 2023, 5:05pm UTC](https://community.sonarsource.com/t/sonarcloud-io-cannot-be-resolved/82444/17 "2023-01-26T17:05:07Z")
Hi all, Here’s a final update: * * * [12:02 p.m. EST] This incident has been resolved. Our DNS provider has resolved an issue on its side and our monitoring shows that normal traffic has resumed. We apologize for the inconvenience.   Ann, the SonaCloud team & all of Sonar ---
**Author:** ![ganncamp](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ganncamp/32/1261_2.png) [@ganncamp](https://community.sonarsource.com/u/ganncamp)\ **Post date:** [January 26, 2023, 6:44pm UTC](https://community.sonarsource.com/t/sonarcloud-io-cannot-be-resolved/82444/18 "2023-01-26T18:44:26Z")
A post was split to a new topic: [500 error trying to get pull request](https://community.sonarsource.com/t/500-error-trying-to-get-pull-request/82479)