In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 31, 2024 - 00:00 UTC
May 31, 2024 - 00:00 UTC
Scheduled - As part of our ongoing efforts to improve the performance and stability of our platform, Divio will be implementing CPU and memory limits on the 31st of May 2024.
To learn more about the reasons behind this decision and how it may impact you and your applications, please read our blog post at https://www.divio.com/blog/divio-starts-enforcing-cpu-and-memory-limits
Need help or have questions? Our support team is ready to assist you!
May 31, 2024 00:00-01:00 UTC
To learn more about the reasons behind this decision and how it may impact you and your applications, please read our blog post at https://www.divio.com/blog/divio-starts-enforcing-cpu-and-memory-limits
Need help or have questions? Our support team is ready to assist you!
May 31, 2024 00:00-01:00 UTC
Customer Sites (US AWS)
Operational
Deployment
?
Operational
Hosting
?
Operational
Media Files (S3)
?
Operational
Divio Single Sign-On
Operational
Elasticsearch
Operational
Customer Sites (EU AWS)
Operational
Deployment
?
Operational
Hosting
?
Operational
Media Files (S3)
?
Operational
Divio Single Sign-On
Operational
Elasticsearch
Operational
Customer Sites (UK AWS)
Operational
Deployment
Operational
Hosting
Operational
Media Files (S3)
Operational
Divio Single Sign-On
Operational
Elasticsearch
Operational
Customer Sites (CH)
Operational
Deployment
Operational
Hosting
Operational
Media files (pithos)
Operational
Divio Single Sign-On
Operational
Divio Control Panel (control.divio.com)
?
Operational
Divio CLI
Operational
Divio Static
?
Operational
Divio Website
?
Operational
Divio Support (support.divio.com)
Operational
django CMS demos
Operational
Infrastructure Providers
Operational
AWS ec2-us-east-1
Operational
AWS rds-us-east-1
Operational
AWS route53
Operational
AWS rds-eu-west-1
Operational
Datacenter Zürich
?
Operational
Exoscale
Operational
External Services
Operational
Python Infrastructure pypi.python.org
Operational
GitHub
Operational
DNSimple Name Servers
Operational
@getsentry API
Operational
Intercom Intercom APIs
Operational
Intercom Intercom message delivery
Operational
Intercom Intercom web application
Operational
Intercom Intercom Mobile APIs
Operational
Let's Encrypt
Operational
PagerDuty Integration API
Operational
PagerDuty Notification Delivery
Operational
PagerDuty REST API & Web Application
Operational
Datadog Alerting Engine
Operational
Datadog API
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
RabbitMQ service upgrade - Swiss Region (Exoscale)
Feb 25, 2025 07:00-08:00 UTC
As part of our ongoing efforts to improve the performance and stability of our platform, we will perform an upgrade on our RabbitMQ services to version 3.13, in the Swiss Region (Exoscale).
Deployments and other Divio services in this region will not be fully available during the upgrade.
Only applications using a message queue (RabbitMQ service - e.g. celery or laravel queues) will be impacted.
During the maintenance window and the upgrade process, the RabbitMQ service will be intermittently unavailable. For running applications using a message queue, it means that sending or receiving messages will fail for a few minutes at a time.
Furthermore, as the message queue will restart multiple times during the upgrade process, any messages held in non-durable queues will be lost and will need to be recreated.
The full upgrade process is expected to take less than 1 hour, with service unavailability periods between 2 and 4 minutes.
To ensure that the impact on your application is minimal, please ensure that:
- Durable queues are enabled and persistent messages are used. This is essential if your application cannot afford to lose messages.
- Your application can automatically reconnect to RabbitMQ and react properly on connection errors to the message queue.
Note that most frameworks, such as Celery, should handle that for you.
If you need help or have questions, our support team is ready to assist you!
Posted on Jan 27, 2025 - 14:59 UTC
Deployments and other Divio services in this region will not be fully available during the upgrade.
Only applications using a message queue (RabbitMQ service - e.g. celery or laravel queues) will be impacted.
During the maintenance window and the upgrade process, the RabbitMQ service will be intermittently unavailable. For running applications using a message queue, it means that sending or receiving messages will fail for a few minutes at a time.
Furthermore, as the message queue will restart multiple times during the upgrade process, any messages held in non-durable queues will be lost and will need to be recreated.
The full upgrade process is expected to take less than 1 hour, with service unavailability periods between 2 and 4 minutes.
To ensure that the impact on your application is minimal, please ensure that:
- Durable queues are enabled and persistent messages are used. This is essential if your application cannot afford to lose messages.
- Your application can automatically reconnect to RabbitMQ and react properly on connection errors to the message queue.
Note that most frameworks, such as Celery, should handle that for you.
If you need help or have questions, our support team is ready to assist you!
Posted on Jan 27, 2025 - 14:59 UTC
RabbitMQ service upgrade - Open Cloud (UK)
Mar 3, 2025 07:00-08:00 UTC
As part of our ongoing efforts to improve the performance and stability of our platform, we will perform an upgrade on our RabbitMQ services to version 3.13, in the AWS UK Region.
Deployments and other Divio services in this region will not be fully available during the upgrade.
Only applications using a message queue (RabbitMQ service - e.g. celery or laravel queues) will be impacted.
During the maintenance window and the upgrade process, the RabbitMQ service will be intermittently unavailable. For running applications using a message queue, it means that sending or receiving messages will fail for a few minutes at a time.
Furthermore, as the message queue will restart multiple times during the upgrade process, any messages held in non-durable queues will be lost and will need to be recreated.
The full upgrade process is expected to take less than 1 hour, with service unavailability periods between 2 and 4 minutes.
To ensure that the impact on your application is minimal, please ensure that:
- Durable queues are enabled and persistent messages are used. This is essential if your application cannot afford to lose messages.
- Your application can automatically reconnect to RabbitMQ and react properly on connection errors to the message queue.
Note that most frameworks, such as Celery, should handle that for you.
If you need help or have questions, our support team is ready to assist you!
Posted on Jan 27, 2025 - 15:03 UTC
Deployments and other Divio services in this region will not be fully available during the upgrade.
Only applications using a message queue (RabbitMQ service - e.g. celery or laravel queues) will be impacted.
During the maintenance window and the upgrade process, the RabbitMQ service will be intermittently unavailable. For running applications using a message queue, it means that sending or receiving messages will fail for a few minutes at a time.
Furthermore, as the message queue will restart multiple times during the upgrade process, any messages held in non-durable queues will be lost and will need to be recreated.
The full upgrade process is expected to take less than 1 hour, with service unavailability periods between 2 and 4 minutes.
To ensure that the impact on your application is minimal, please ensure that:
- Durable queues are enabled and persistent messages are used. This is essential if your application cannot afford to lose messages.
- Your application can automatically reconnect to RabbitMQ and react properly on connection errors to the message queue.
Note that most frameworks, such as Celery, should handle that for you.
If you need help or have questions, our support team is ready to assist you!
Posted on Jan 27, 2025 - 15:03 UTC
RabbitMQ service upgrade - Open Cloud (US)
Mar 11, 2025 07:00-08:00 UTC
As part of our ongoing efforts to improve the performance and stability of our platform, we will perform an upgrade on our RabbitMQ services to version 3.13, in the AWS US Region.
Deployments and other Divio services in this region will not be fully available during the upgrade.
Only applications using a message queue (RabbitMQ service - e.g. celery or laravel queues) will be impacted.
During the maintenance window and the upgrade process, the RabbitMQ service will be intermittently unavailable. For running applications using a message queue, it means that sending or receiving messages will fail for a few minutes at a time.
Furthermore, as the message queue will restart multiple times during the upgrade process, any messages held in non-durable queues will be lost and will need to be recreated.
The full upgrade process is expected to take less than 1 hour, with service unavailability periods between 2 and 4 minutes.
To ensure that the impact on your application is minimal, please ensure that:
- Durable queues are enabled and persistent messages are used. This is essential if your application cannot afford to lose messages.
- Your application can automatically reconnect to RabbitMQ and react properly on connection errors to the message queue.
Note that most frameworks, such as Celery, should handle that for you.
If you need help or have questions, our support team is ready to assist you!
Posted on Jan 27, 2025 - 15:06 UTC
Deployments and other Divio services in this region will not be fully available during the upgrade.
Only applications using a message queue (RabbitMQ service - e.g. celery or laravel queues) will be impacted.
During the maintenance window and the upgrade process, the RabbitMQ service will be intermittently unavailable. For running applications using a message queue, it means that sending or receiving messages will fail for a few minutes at a time.
Furthermore, as the message queue will restart multiple times during the upgrade process, any messages held in non-durable queues will be lost and will need to be recreated.
The full upgrade process is expected to take less than 1 hour, with service unavailability periods between 2 and 4 minutes.
To ensure that the impact on your application is minimal, please ensure that:
- Durable queues are enabled and persistent messages are used. This is essential if your application cannot afford to lose messages.
- Your application can automatically reconnect to RabbitMQ and react properly on connection errors to the message queue.
Note that most frameworks, such as Celery, should handle that for you.
If you need help or have questions, our support team is ready to assist you!
Posted on Jan 27, 2025 - 15:06 UTC
RabbitMQ service upgrade - Open Cloud (EU)
Mar 13, 2025 07:00-08:00 UTC
As part of our ongoing efforts to improve the performance and stability of our platform, we will perform an upgrade on our RabbitMQ services to version 3.13, in the AWS EU Region.
Deployments and other Divio services in this region will not be fully available during the upgrade.
Only applications using a message queue (RabbitMQ service - e.g. celery or laravel queues) will be impacted.
During the maintenance window and the upgrade process, the RabbitMQ service will be intermittently unavailable. For running applications using a message queue, it means that sending or receiving messages will fail for a few minutes at a time.
Furthermore, as the message queue will restart multiple times during the upgrade process, any messages held in non-durable queues will be lost and will need to be recreated.
The full upgrade process is expected to take less than 1 hour, with service unavailability periods between 2 and 4 minutes.
To ensure that the impact on your application is minimal, please ensure that:
- Durable queues are enabled and persistent messages are used. This is essential if your application cannot afford to lose messages.
- Your application can automatically reconnect to RabbitMQ and react properly on connection errors to the message queue.
Note that most frameworks, such as Celery, should handle that for you.
If you need help or have questions, our support team is ready to assist you!
Posted on Jan 27, 2025 - 15:05 UTC
Deployments and other Divio services in this region will not be fully available during the upgrade.
Only applications using a message queue (RabbitMQ service - e.g. celery or laravel queues) will be impacted.
During the maintenance window and the upgrade process, the RabbitMQ service will be intermittently unavailable. For running applications using a message queue, it means that sending or receiving messages will fail for a few minutes at a time.
Furthermore, as the message queue will restart multiple times during the upgrade process, any messages held in non-durable queues will be lost and will need to be recreated.
The full upgrade process is expected to take less than 1 hour, with service unavailability periods between 2 and 4 minutes.
To ensure that the impact on your application is minimal, please ensure that:
- Durable queues are enabled and persistent messages are used. This is essential if your application cannot afford to lose messages.
- Your application can automatically reconnect to RabbitMQ and react properly on connection errors to the message queue.
Note that most frameworks, such as Celery, should handle that for you.
If you need help or have questions, our support team is ready to assist you!
Posted on Jan 27, 2025 - 15:05 UTC