Dear Customer,
we are going to update the a9s platform during the scheduled timeframe.
This update introduces the new Java Buildpack version 5.x. This buildpack is now packaged using the same approach as for all other buildpacks. In case you face any issues with the buildpack please provide feedback, so it can be worked on by the community.
For more information have a look into the official release notes
cflinuxfs3 buildpacks
Due to cflinuxfs3 being out of support for several years now the support for new buildpacks for cflinuxfs3 has been discontinued. That means beginning with v1.75.0 no new buildpack versions will be available anymore for cflinuxfs3.
Please find below an overview to which versions the different buildpacks are pinned.
buildpack version
binary-buildpack 1.1.26
dotnet-core-buildpack 2.4.50
go-buildpack 1.10.46
java-buildpack 4.77.0
nginx-buildpack 1.2.32
nodejs-buildpack 1.8.37
php-buildpack 4.6.28
python-buildpack 1.9.0
ruby-buildpack 1.11.0
staticfile-buildpack 1.6.37
Data Services (e.g. removal, deprecation, unsupported, new services)
RabbitMQ 37 removal
Due to compilation issues with certain components we removed the RabbitMQ37 offering which was still running on Bionic Stemcells which are EOL for many years already. According to our usage information none of our customers is actively using RabbitMQ 37 and should be affected by this change.
The update procedure is structured into 3 stages:
Stage 1: Update of the Runtime
Stage 2: Update of the a9s Data Service Framework
Stage 3: Update of all existing a9s Data Service instances
The stages have the following impact:
Stage 1:
- Restart of all applications. For slow starting applications with a single instance configuration this might introduce a downtime of up to 5 minutes in addition to application startup time.
- Restart of the API. Single requests to the API might fail but subsequent requests shall pass.
Stage 2:
- Creation, update and deletion of new or existing a9s Data Services instances will be unavailable for up to 5 minutes.
- The availability of existing a9s Data Service instances will not be affected by this.
Stage 3:
- All a9s Data Service instances will be restarted which causes single instances to be not available for up to 5 minutes.
- You may see your app reconnecting to the master node while the service instance gets updated.
We'll provide an update as soon as we finish the respective stage.
Best regards,
The anynines Team
Posted on
May 20, 2026 - 13:41 CEST