On 13th December a change to SonarQube Cloud resulted in a temporary service disruption for a small set of customers, which was quickly resolved. We are writing to provide transparency regarding this event and to request action from those utilizing strict network restrictions.
What Happened
- During infrastructure maintenance, new IP addresses were added to our Unified Connectivity VPCs. A small number of customers using IP allow-listing experienced intermittent communication failures.
Impact
-
Symptoms: Intermittent “Something went wrong” errors during GitHub Actions runs when retrieving Pull Request data (endpoint: /api/alm_integration/show_pullrequest).
-
Affected users: SonarQube Cloud EU and US instance users utilizing GitHub Enterprise and other DevOps integrations with IP allow-listing.
-
Scope: Customers with IP address filtering may have observed failures until December 16th, 2025.
Action Required: Update network configurations to allow the following IP addresses.
Current IP Addresses (EU instance):
-
3.77.79.176/28
-
3.253.125.212/30
-
18.97.201.0/29
Current IP Addresses (US instance):
-
44.215.145.4/30
-
18.97.29.56/29
Note: If you have selected the “Enable IP allow list configuration for installed GitHub Apps” option in your GitHub organization, these updates may apply automatically.
For the latest official list of IP Addresses, refer to our documentation: SonarQube Cloud and SonarQube Cloud US instance
We apologize for the disruption and the oversight.