All Systems Operational
About This Site
Find information about the vitality of anynines related services.
API
Operational
Customer Panel
Operational
Services
Operational
Customer applications
Operational
Website
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
[CAUTION: Important Announcement] Scheduled Maintenance: Platform Update Oct 19, 2026 09:00 - Oct 24, 2026 09:00 CEST
Dear Customer,
we are going to update the a9s platform during the scheduled time frame.
Runtime
a9s Dashboard API removal
Breaking change: The a9s Dashboard API component and its dependencies have been removed. It previously served version 0 of the a9s Public API, so direct integrations using the old /service-instances/:guid endpoints break after the upgrade. Migrate API consumers to the authenticated a9s Public API v1 with the /v1/instances/{serviceInstanceId} base path. The former GET /service-instances/:guid/config and GET /service-instances/:guid/paas endpoints are removed; the instance overview provides the tenant_name and subtenant_name values previously supplied by the PaaS endpoint. The a9s Service Dashboard remains available through the a9s Public API and is now served by its colocated nginx; no separate Dashboard API component or related deployment configuration is required.
Data Services (e.g. removal, deprecation, unsupported, new services)
a9s Prometheus
The a9s-prometheus3 offering is now available as a Beta (non-GA) service. It contains Prometheus 3 and Grafana 13.
a9s Prometheus 3: Credentials not forwarded on cross-host redirects
Breaking change: Starting with Prometheus 3 (offering a9s-prometheus3, Beta, non-GA), credentials such as the Authorization header, basic auth, bearer token, OAuth2 and configured headers are no longer forwarded when following a redirect to a different host. Authentication fails if remote_write or custom scrape_configs target an endpoint behind a load balancer or proxy that answers with a 302 redirect to another host.
Action required: Before migrating from a9s Prometheus 2 to a9s Prometheus 3, point remote_write and custom scrape_configs directly at the final target host, or make sure no cross-host redirect occurs.
a9s Prometheus 2: Planned End of Support
Announcement: Support for a9s Prometheus 2 is planned to end with anynines deployment v79.0.0, expected at the end of November 2026, because the underlying Prometheus 2 software has been end-of-life by its vendor since July 2025.
Please organize the migration of existing a9s Prometheus 2 Service Instances to a more up-to-date version of a9s Prometheus. After v79.0.0, regular support will no longer be provided. Running Service Instances are not intentionally broken, and support requests will not be rejected, but no new features, bug fixes, or security updates will be delivered for this version.
For more information, see a9s Data Service Life-Cycle Stages and the a9s Data Services Major Updates and Deprecation Roadmap.
a9s Redis: End of Support
The a9s Redis Data Service is no longer supported. Creation of new a9s Redis Service Instances is disabled by default, and regular support and documentation are no longer provided.
Migrate existing a9s Redis Service Instances to a9s KeyValue by using the Disaster Recovery feature or the manual migration procedure. Existing instances are not intentionally broken, but their operation after this update cannot be guaranteed.
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 Oct 07, 2026 - 10:06 CEST
we are going to update the a9s platform during the scheduled time frame.
Runtime
a9s Dashboard API removal
Breaking change: The a9s Dashboard API component and its dependencies have been removed. It previously served version 0 of the a9s Public API, so direct integrations using the old /service-instances/:guid endpoints break after the upgrade. Migrate API consumers to the authenticated a9s Public API v1 with the /v1/instances/{serviceInstanceId} base path. The former GET /service-instances/:guid/config and GET /service-instances/:guid/paas endpoints are removed; the instance overview provides the tenant_name and subtenant_name values previously supplied by the PaaS endpoint. The a9s Service Dashboard remains available through the a9s Public API and is now served by its colocated nginx; no separate Dashboard API component or related deployment configuration is required.
Data Services (e.g. removal, deprecation, unsupported, new services)
a9s Prometheus
The a9s-prometheus3 offering is now available as a Beta (non-GA) service. It contains Prometheus 3 and Grafana 13.
a9s Prometheus 3: Credentials not forwarded on cross-host redirects
Breaking change: Starting with Prometheus 3 (offering a9s-prometheus3, Beta, non-GA), credentials such as the Authorization header, basic auth, bearer token, OAuth2 and configured headers are no longer forwarded when following a redirect to a different host. Authentication fails if remote_write or custom scrape_configs target an endpoint behind a load balancer or proxy that answers with a 302 redirect to another host.
Action required: Before migrating from a9s Prometheus 2 to a9s Prometheus 3, point remote_write and custom scrape_configs directly at the final target host, or make sure no cross-host redirect occurs.
a9s Prometheus 2: Planned End of Support
Announcement: Support for a9s Prometheus 2 is planned to end with anynines deployment v79.0.0, expected at the end of November 2026, because the underlying Prometheus 2 software has been end-of-life by its vendor since July 2025.
Please organize the migration of existing a9s Prometheus 2 Service Instances to a more up-to-date version of a9s Prometheus. After v79.0.0, regular support will no longer be provided. Running Service Instances are not intentionally broken, and support requests will not be rejected, but no new features, bug fixes, or security updates will be delivered for this version.
For more information, see a9s Data Service Life-Cycle Stages and the a9s Data Services Major Updates and Deprecation Roadmap.
a9s Redis: End of Support
The a9s Redis Data Service is no longer supported. Creation of new a9s Redis Service Instances is disabled by default, and regular support and documentation are no longer provided.
Migrate existing a9s Redis Service Instances to a9s KeyValue by using the Disaster Recovery feature or the manual migration procedure. Existing instances are not intentionally broken, but their operation after this update cannot be guaranteed.
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 Oct 07, 2026 - 10:06 CEST