We use sonar-scanner on CI with sonar.host.url being set to https://sonarcloud.io. Since that was unreasonably slow at times, we did a JFR recording to see if there are any memory/CPU bottlenecks. However, it seems at least some of the slowness is caused the CI server connecting to a server in an AWS data center on the west coast of the US:
The longest recorded socket read took 43.864 s to read 5 B from the host at 2600:9000:2035:ec00:1c:8b9e:3f40:93a1
see 2600:9000:2035:ec00:1c:8b9e:3f40:93a1 | Seattle, AS16509, VPN Not Detected | IPinfo
A DNS lookup also shows IPs in the US being used for sonarcloud.io:
$ dig @1.1.1.1 sonarcloud.io AAAA
; <<>> DiG 9.10.6 <<>> @1.1.1.1 sonarcloud.io AAAA
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 43634
;; flags: qr rd ra; QUERY: 1, ANSWER: 8, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;sonarcloud.io. IN AAAA
;; ANSWER SECTION:
sonarcloud.io. 15 IN AAAA 2600:9000:225e:2e00:1c:8b9e:3f40:93a1
sonarcloud.io. 15 IN AAAA 2600:9000:225e:aa00:1c:8b9e:3f40:93a1
sonarcloud.io. 15 IN AAAA 2600:9000:225e:2400:1c:8b9e:3f40:93a1
sonarcloud.io. 15 IN AAAA 2600:9000:225e:6400:1c:8b9e:3f40:93a1
sonarcloud.io. 15 IN AAAA 2600:9000:225e:de00:1c:8b9e:3f40:93a1
sonarcloud.io. 15 IN AAAA 2600:9000:225e:1000:1c:8b9e:3f40:93a1
sonarcloud.io. 15 IN AAAA 2600:9000:225e:ce00:1c:8b9e:3f40:93a1
sonarcloud.io. 15 IN AAAA 2600:9000:225e:e00:1c:8b9e:3f40:93a1
;; Query time: 35 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Mon Jun 15 11:17:12 CEST 2026
;; MSG SIZE rcvd: 266
According to your documentation, sonarcloud.io is supposed to be hosted in the EU. Why is the scanner then sending data to a server in the US?