Incidents reported on status page for EVERTRUST https://status.evertrust.io/ https://d1lppblt9t2x15.cloudfront.net/logos/8f8c80483913991c7f55c093b4296294.png https://status.evertrust.io/ en https://status.evertrust.io/incident/538097 Tue, 01 Apr 2025 15:30:20 +0000 https://status.evertrust.io/incident/538097#9c0326e885b800c0d2177d02a879e37350cd9aa18fc40f5d79123526f95e06f8 Maintenance completed https://status.evertrust.io/incident/538097 Tue, 01 Apr 2025 15:30:20 -0000 https://status.evertrust.io/incident/538097#6d996a406c4a3cef334010e333f9eb9ad7c4ec3e909c93a88c86590fa80a598b We are improving our mail sending capabilities. Starting April 1st, 2025 for staging instances and April 15, 2025 for production instances, platforms that use [the default SMTP server](https://docs.evertrust.fr/cloud/cloud-docs/mailing) will use AWS SES to deliver email notifications to users. These modifications will increase availability and simplify the setup flow for customizing your sending domain. Additionally, in order to prevent any confusion regarding email notification emails, instances that use the default sending address will enforce that notifications are sent from `noreply@cloud.evertrust.io`. If the instance uses a custom domain, nothing will change. However, if you used another address ending in `evertrust.fr`, such as `ops@evertrust.fr`, you have until June 1st, 2025, to migrate your notifications to the new address, `noreply@cloud.evertrust.io`. On that date, notifications that still use the legacy address will be automatically migrated to the new address. In the meantime, notifications will continue to be delivered as usual. It is expected that the migration won’t have any impact, except if you used rules that relied on the originating server or email address. In any case, you can open a ticket on [the support portal](https://support.evertrust.fr) to request more information on how to handle the migration Cheers, The EVERTRUST Cloud team https://status.evertrust.io/incident/538097 Tue, 01 Apr 2025 15:30:20 +0000 https://status.evertrust.io/incident/538097#9c0326e885b800c0d2177d02a879e37350cd9aa18fc40f5d79123526f95e06f8 Maintenance completed https://status.evertrust.io/incident/538097 Tue, 01 Apr 2025 15:30:20 -0000 https://status.evertrust.io/incident/538097#6d996a406c4a3cef334010e333f9eb9ad7c4ec3e909c93a88c86590fa80a598b We are improving our mail sending capabilities. Starting April 1st, 2025 for staging instances and April 15, 2025 for production instances, platforms that use [the default SMTP server](https://docs.evertrust.fr/cloud/cloud-docs/mailing) will use AWS SES to deliver email notifications to users. These modifications will increase availability and simplify the setup flow for customizing your sending domain. Additionally, in order to prevent any confusion regarding email notification emails, instances that use the default sending address will enforce that notifications are sent from `noreply@cloud.evertrust.io`. If the instance uses a custom domain, nothing will change. However, if you used another address ending in `evertrust.fr`, such as `ops@evertrust.fr`, you have until June 1st, 2025, to migrate your notifications to the new address, `noreply@cloud.evertrust.io`. On that date, notifications that still use the legacy address will be automatically migrated to the new address. In the meantime, notifications will continue to be delivered as usual. It is expected that the migration won’t have any impact, except if you used rules that relied on the originating server or email address. In any case, you can open a ticket on [the support portal](https://support.evertrust.fr) to request more information on how to handle the migration Cheers, The EVERTRUST Cloud team https://status.evertrust.io/incident/511759 Wed, 19 Feb 2025 16:00:48 +0000 https://status.evertrust.io/incident/511759#9de056826e78f4a6238c2cce519ab0e7b42c0ef35e598a0397c7ae5295e87339 Maintenance completed https://status.evertrust.io/incident/511759 Wed, 19 Feb 2025 13:00:48 -0000 https://status.evertrust.io/incident/511759#be92e91c9d7e35276d1d669818fb00e9a1ff9472ef07380f5869b682001a3adb ## Overview We’ll be conducting routing maintenance on production environments, to improve our platform overall reliability. In the process, we’ll also upgrade Horizon and Stream to the latest LTS versions. ## Impact It is expected that a few minutes of downtime might cause some enrollments to fail during the maintenance. This downtime will be limited to a few minutes per instance, not to the whole maintenance window. Additionally, for compatibility reasons, we will drop support for reaching Stream from an Horizon instance using the `http://stream:9000` endpoint. Instead, the public endpoint (`stream.customer.cloud.evertrust.io`) should be used. This update will require no change from your end, as a database upgrade script will run and automatically update the affected PKI connectors. If you automated PKI connectors provisioning, you’ll have to update your provisioning script to prevent the update from being rolled back. ## Post-Maintenance Once the maintenance is complete, all services will automatically resume with the updated configurations. If you experience any issues after the maintenance, please contact our support team. We appreciate your patience during this maintenance window. These updates will help ensure a more robust and consistent runtime environment. https://status.evertrust.io/incident/511655 Mon, 09 Dec 2024 08:00:00 -0000 https://status.evertrust.io/incident/511655#24c04abb403bba722311e47ddf6aabb4bf856049e12f31f501f1c1ec5c6c8f64 A fix has been implemented. CRL and AIA are now accessible for all customers. https://status.evertrust.io/incident/511655 Sun, 08 Dec 2024 23:20:00 -0000 https://status.evertrust.io/incident/511655#99ab5b86f1667b4216e0daa14246bf81912da6b45001c6d4445473552678e08d A small portion of customers are unable to access their CRL and AIA distribution points, facing DNS resolution issues.