Completed -
The scheduled maintenance has been completed.
Feb 28, 09:00 CET
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 23, 09:00 CET
Scheduled -
Dear Customer,
we are going to update the a9s platform during the scheduled timeframe.
Unsupport a9s Postgresql
a9s PostgresSQL: End of Support: With the current release v56.0.0 (released end of December 2024), we finally end support for the following deprecated a9s Data Service version: a9s PostgreSQL v11: PostgreSQL 11
a9s Prometheus Grafana
a9s Prometheus Grafana: With the current release v56.0.0 (released end of December 2024), we finally end support for the following deprecated a9s Data Service versions: a9s Prometheus Grafana 5 a9s Prometheus Grafana 8
Upcoming: a9s MySQL
a9s MySQL: End of Support: Terminate support, starting from anynines deployment v59.0.0 (expected end of March), we plan to end support for the following deprecated a9s Data Service version: a9s MySQL v10.4
a9s RabbitMQ
a9s RabbitMQ: End of Support: Terminate support, starting from anynines deployment v57.0.0 (expected end of January 2025), we finally end support for the following deprecated a9s Data Service version: a9s Messaging v3.10: RabbitMQ 3.10
a9s MongoDB
a9s MongoDB: End of Support: Terminate support, starting from anynines deployment v60.0.0 (expected end of April 2025), we plan to end support for the following deprecated a9s Data Service version: a9s MongoDB 5
The creation of new a9s Data Service instances for the deprecated versions will be disabled by default in the a9s data service bundle and we will not provide regular support for this versions. The corresponding documentation will also be removed.
To inquire about extended support for a deprecated version, please get in contact with our sales department at sales@anynines.com. 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.