Seald Status https://status.seald.io/ 2026-04-21T10:22:23+00:00 Seald Status <![CDATA[TLS certificate issue]]> http://status.seald.io/incident/95/ One node has an expired certificate that has not been renewed automatically. It has been fixed at 11:40AM.

]]> 2026-04-16T07:55:00+00:00 Seald Status <![CDATA[Partial service disruption]]> http://status.seald.io/incident/92/ One of the workers had a certificate expiration.

12:06 : First reports of issues. 12:20 : The IP has been re-routed to another worker while we investigate the root cause of the renewal failure.

]]> 2026-03-04T08:20:00+00:00 Seald Status <![CDATA[Temporary partial service disruption]]> http://status.seald.io/incident/91/ We experienced network-related errors that caused temporary service disruptions. The issue has been identified and resolved.

]]> 2026-01-30T13:00:00+00:00 Seald Status <![CDATA[500 errors on many endpoints]]> http://status.seald.io/incident/90/ It seems many endpoints end up in 500 errors. We are investigating. The error seems to originate in a connection error between the application servers and the databases. It seems other customers of our hosting provider complain that hostnames for the databases cannot be resolved. We have opened a support ticket, OVHCloud status page does not reflect the incident yet.

UPDATE: A similar incident has been reported on OVHCloud's status page: https://public-cloud.status-ovhcloud.com/incidents/9qmxv0gbky43

UPDATE: OVH announces that the incident should be fixed, but are still monitoring.

UPDATE: Our internal monitoring shows that errors are reduced a lot, but not down to zero yet.

UPDATE: Our internal monitoring does not show any errors anymore.

]]> 2025-11-05T05:45:00+00:00 Seald Status <![CDATA[502 on static assets]]> http://status.seald.io/incident/89/ Between 10h25 and 10h30 Paris time, static assets were unreachable (dashboard).

API was not impacted.

]]> 2025-09-25T08:25:00+00:00 Seald Status <![CDATA[Seald upgrade]]> http://status.seald.io/incident/88/ Service impact is expected to last few minutes.

]]> 2025-09-16T20:47:02+00:00 Seald Status <![CDATA[Seald upgrade]]> http://status.seald.io/incident/87/ Service impact is expected to last few minutes.

]]> 2025-09-12T09:46:16+00:00 Seald Status <![CDATA[Intermittent errors]]> http://status.seald.io/incident/86/ When trying a potential fix for the 502 errors, one of the workers got stuck in an unexpected state, which made it return 404 errors.

This is now fixed.

]]> 2025-08-29T13:43:00+00:00 Seald Status <![CDATA[Intermittent 502 / 504 errors]]> http://status.seald.io/incident/85/ We have observed a small but unusual number of requests ending in 502 and 504 errors on both Staging and Production environments.

We are investigating to find the root cause.

There may be a few unavailabilities on the Staging environment while we investigate.

]]> 2025-08-27T20:00:00+00:00 Seald Status <![CDATA[Seald upgrade]]> http://status.seald.io/incident/84/ Service impact is expected to last few minutes.

]]> 2025-08-25T08:05:00+00:00 Seald Status <![CDATA[Partial outage of the staging environment]]> http://status.seald.io/incident/83/ It seems some of the requests made to api.staging-0.seald.io are getting timeouts. We are investigating.

The incident does not affect the production environment.

23/07/2025 13:20: Fixed

]]> 2025-07-23T10:15:00+00:00 Seald Status <![CDATA[Staging load balander migration]]> http://status.seald.io/incident/82/ Following continuous infrastructure improvement, we need to migrate the gateway into most recent infrastructure. Some issues such as short downtimes (~15 seconds) might be experienced. The migration of is planned at the 2025-06-30 07:00 UTC

]]> 2025-06-10T14:32:33+00:00 Seald Status <![CDATA[Staging environment is unavailable]]> http://status.seald.io/incident/81/ Staging environement is currently unavailable. Investigating.

EDIT : fixed at 17:03

]]> 2025-06-04T14:30:00+00:00 Seald Status <![CDATA[Seald upgrade]]> http://status.seald.io/incident/80/ Service impact is expected to last few minutes.

]]> 2025-05-05T13:02:57+00:00 Seald Status <![CDATA[Caching service down]]> http://status.seald.io/incident/79/ Our caching service, which is used for certain operations, has crashed in a way that was not detected by our automated healthchecks.

This has affected operations such as sending emails & SMS messages.

We are working on re-establishing service.

Update: Service seems re-established since 09:41. The issue was caused by a network problem at OVH which in turned caused a database update failure. We are still verifying the state of the database.

]]> 2025-04-17T01:07:00+00:00 Seald Status <![CDATA[Staging infrastructure upgrade]]> http://status.seald.io/incident/78/ Only for staging environment. Service impact is expected to last few minutes.

]]> 2025-02-28T09:17:29+00:00 Seald Status <![CDATA[Seald upgrade]]> http://status.seald.io/incident/77/ Service impact is expected to last few minutes.

]]> 2025-02-20T09:15:14+00:00 Seald Status <![CDATA[Infrastructure update]]> http://status.seald.io/incident/76/ No service should be impacted.

]]> 2025-02-17T14:16:02+00:00 Seald Status <![CDATA[Infrastructure update]]> http://status.seald.io/incident/75/ No service should be impacted.

]]> 2025-02-12T15:18:40+00:00 Seald Status <![CDATA[Seald upgrade]]> http://status.seald.io/incident/74/ Service impact is expected to last few minutes.

]]> 2025-01-08T14:08:43+00:00 Seald Status <![CDATA[Seald staging environment migration]]> http://status.seald.io/incident/73/ Service impact is expected to last few minutes, only for staging environment. Production is not impacted.

]]> 2024-12-05T08:57:29+00:00 Seald Status <![CDATA[Seald staging environment migration]]> http://status.seald.io/incident/72/ Service impact is expected to last few minutes, only for staging environment. Production is not impacted.

]]> 2024-12-04T12:22:14+00:00 Seald Status <![CDATA[Seald upgrade]]> http://status.seald.io/incident/71/ Service impact is expected to last few minutes.

]]> 2024-11-05T15:54:39+00:00 Seald Status <![CDATA[Staging environment was temporarily inaccessible]]> http://status.seald.io/incident/70/ Staging environment was temporarily inaccessible. All is back to normal.

]]> 2024-11-05T09:30:00+00:00 Seald Status <![CDATA[Instability on Staging environment]]> http://status.seald.io/incident/69/ We are experiencing some instability related to the load balancer on the Staging environment. Production is unaffected.

]]> 2024-10-23T08:00:00+00:00 Seald Status <![CDATA[Seald upgrade]]> http://status.seald.io/incident/68/ Service impact is expected to last few minutes.

]]> 2024-10-21T08:22:37+00:00 Seald Status <![CDATA[Seald upgrade]]> http://status.seald.io/incident/67/ Service impact is expected to last few minutes.

]]> 2024-10-11T13:02:00+00:00 Seald Status <![CDATA[CORS issues in the production environment for web clients]]> http://status.seald.io/incident/66/ 10/09/2024 8:21AM CET: we detected an issue that web requests to the main API were not working through one of our customer's message at

10/09/2024 9:07AM CET: we identified at that the issue was related to CORS, but could not reproduce in our automated tests

10/09/2024 9:36AM CET: we found that the issue only affects the /is_alive/ endpoint from a web client that is not on a *.seald.io domain, this falsely leads customers who use this endpoint to believe that the API is down when it is in fact up

10/09/2024 10:00AM CET: we successfully tested a fix in our testing environment at 10:00AM, and diagnosed that the issue dates back from last night's deployment at 10:23PM CET

10/09/2024 10:19AM CET: the production environment has been fixed.

]]> 2024-09-09T20:25:00+00:00 Seald Status <![CDATA[Seald upgrade]]> http://status.seald.io/incident/65/ Service impact is expected to last few minutes.

]]> 2024-09-05T13:27:14+00:00 Seald Status <![CDATA[Seald upgrade]]> http://status.seald.io/incident/64/ Service impact is expected to last few minutes.

]]> 2024-09-02T13:22:45+00:00 Seald Status <![CDATA[Asynchronous tasks blocked]]> http://status.seald.io/incident/63/ Some asynchronous tasks were failing to launch for about 4 hours. Everything is back to normal now.

]]> 2024-07-24T08:40:00+00:00 Seald Status <![CDATA[Seald upgrade]]> http://status.seald.io/incident/62/ Service impact is expected to last few minutes.

]]> 2024-06-28T13:27:10+00:00 Seald Status <![CDATA[Seald upgrade]]> http://status.seald.io/incident/61/ Service impact is expected to last few minutes.

]]> 2024-06-07T12:36:40+00:00 Seald Status <![CDATA[Seald upgrade]]> http://status.seald.io/incident/60/ Service impact is expected to last few minutes.

]]> 2024-06-05T20:10:29+00:00 Seald Status <![CDATA[Seald upgrade]]> http://status.seald.io/incident/59/ Service impact is expected to last few minutes.

]]> 2024-05-30T08:32:52+00:00 Seald Status <![CDATA[Seald upgrade]]> http://status.seald.io/incident/58/ Service impact is expected to last few minutes.

]]> 2024-03-12T12:57:18+00:00 Seald Status <![CDATA[Redis database failure]]> http://status.seald.io/incident/57/ One of the Redis databases changed IP due to an OVH migration.

Some authentications failed until the DNS cache was invalidated (~10min).

]]> 2024-02-13T06:20:00+00:00 Seald Status <![CDATA[Seald upgrade]]> http://status.seald.io/incident/56/ Service impact is expected to last few minutes.

]]> 2024-01-22T14:03:37+00:00 Seald Status <![CDATA[Staging environment unstable]]> http://status.seald.io/incident/55/ Due to one HA node relaunched, staging environment might have been unreachable for some users. It is fixed now.

]]> 2024-01-04T10:20:00+00:00 Seald Status <![CDATA[Seald Upgrade]]> http://status.seald.io/incident/54/ Service impact is expected to last few minutes.

]]> 2023-11-29T15:00:37+00:00 Seald Status <![CDATA[Redis database failure]]> http://status.seald.io/incident/53/ One of the Redis databases used is down due to an OVH outage since Nov 16, 2023 - 01:52 UTC, OVH detected it since Nov 16, 2023 - 01:55 UTC : https://public-cloud.status-ovhcloud.com/incidents/6sd9lwym7zdt.

Most API calls fail due to an authentication error.

On Nov 16, 2023 - 7:34 UTC : our team identified the issue, reported it to OVH, and started working on swapping the database.

On Nov 16, 2023 - 8:32 UTC, we swapped the database, and are monitoring that everything is back to normal.

]]> 2023-11-16T01:50:00+00:00 Seald Status <![CDATA[Seald Upgrade]]> http://status.seald.io/incident/52/ Service impact is expected to last few minutes.

]]> 2023-10-23T13:48:14+00:00 Seald Status <![CDATA[Seald upgrade]]> http://status.seald.io/incident/50/ Service impact is expected to last few minutes.

]]> 2023-10-12T12:50:29+00:00 Seald Status <![CDATA[High response times]]> http://status.seald.io/incident/51/ Due to very high load, the API has higher than usual response times.

]]> 2023-10-12T11:30:00+00:00 Seald Status <![CDATA[Seald upgrade]]> http://status.seald.io/incident/49/ Service impact is expected to last few minutes.

]]> 2023-10-03T09:37:00+00:00 Seald Status <![CDATA[Seald upgrade]]> http://status.seald.io/incident/48/ Service impact is expected to last few minutes.

]]> 2023-09-13T17:36:50+00:00 Seald Status <![CDATA[Seald upgrade]]> http://status.seald.io/incident/47/ Service impact is expected to last few minutes.

]]> 2023-08-29T08:10:55+00:00 Seald Status <![CDATA[Seald instances unavailable]]> http://status.seald.io/incident/46/ Seald Webservices were unavailable for 10 minutes this morning because of an unexpected issue during the database update.

]]> 2023-08-29T07:20:00+00:00 Seald Status <![CDATA[Seald upgrade]]> http://status.seald.io/incident/45/ Service impact is expected to last few minutes.

]]> 2023-07-27T19:31:09+00:00 Seald Status <![CDATA[Seald upgrade]]> http://status.seald.io/incident/44/ Service impact is expected to last few minutes.

]]> 2023-07-21T13:01:54+00:00 Seald Status <![CDATA[Seald upgrade]]> http://status.seald.io/incident/43/ Service impact is expected to last few minutes.

]]> 2023-05-11T21:03:01+00:00 Seald Status <![CDATA[Seald upgrade]]> http://status.seald.io/incident/42/ Service impact is expected to last for no more than a few minutes.

]]> 2023-04-11T16:49:48+00:00 Seald Status <![CDATA[Seald upgrade]]> http://status.seald.io/incident/41/ Service impact is expected to last for no more than a few minutes.

]]> 2023-03-24T09:04:02+00:00 Seald Status <![CDATA[Seald SSKS upgrade]]> http://status.seald.io/incident/40/ Impact is expected only on SSKS for no more than a few minutes.

]]> 2023-03-06T09:07:59+00:00 Seald Status <![CDATA[Seald SSKS upgrade]]> http://status.seald.io/incident/39/ Impact is expected only on SSKS for no more than a few minutes.

]]> 2023-03-03T21:00:00+00:00 Seald Status <![CDATA[Seald upgrade]]> http://status.seald.io/incident/38/ Service impact is expected to last for no more than a few seconds.

]]> 2023-02-17T10:43:29+00:00 Seald Status <![CDATA[Seald upgrade]]> http://status.seald.io/incident/37/ Service impact is expected to last for no more than a few seconds.

]]> 2023-02-09T09:06:00+00:00 Seald Status <![CDATA[Seald upgrade]]> http://status.seald.io/incident/36/ Service impact is expected to last for no more than a few seconds.

]]> 2023-02-01T18:15:22+00:00 Seald Status <![CDATA[Seald upgrade]]> http://status.seald.io/incident/35/ Service impact is expected to last for no more than a few seconds.

]]> 2023-01-25T12:42:00+00:00 Seald Status <![CDATA[Seald upgrade]]> http://status.seald.io/incident/34/ Service impact is expected to last for no more than a few seconds.

]]> 2023-01-17T13:12:45+00:00 Seald Status <![CDATA[Seald upgrade]]> http://status.seald.io/incident/33/ Service impact is expected to last for no more than a few seconds.

]]> 2023-01-16T13:56:23+00:00 Seald Status <![CDATA[Seald upgrade]]> http://status.seald.io/incident/32/ Service impact is expected to last for no more than a few seconds.

]]> 2023-01-06T15:43:58+00:00 Seald Status <![CDATA[Seald upgrade]]> http://status.seald.io/incident/31/ Service impact is expected to last for no more than a few minutes.

]]> 2022-12-13T09:17:04+00:00 Seald Status <![CDATA[Slowdown of the production & staging environments]]> http://status.seald.io/incident/29/ Our infrastructure is currently experiencing some performance issues, it may impact response times of the servers. EDIT 15:50: the probable culprit has been identified, the asynchronous task manager was clogged, and it impacted asynchronous execution.

]]> 2022-11-29T09:00:00+00:00 Seald Status <![CDATA[Database update]]> http://status.seald.io/incident/28/ Database updatE. No downtime expected

]]> 2022-11-07T13:37:34+00:00 Seald Status <![CDATA[Partial outage due to connectivity issues with some ISPs]]> http://status.seald.io/incident/26/ Due to a network issue at our hosting provider, our webservices seem to be unavailable when connecting from certain ISPs. Update: 2:17PM UTC+2 : our hosting provider informed us that it should be back online.

]]> 2022-09-20T11:50:00+00:00 Seald Status <![CDATA[Seald update]]> http://status.seald.io/incident/25/ Server disruption is expected to last for no more than a few minutes.

]]> 2022-09-16T13:48:00+00:00 Seald Status <![CDATA[Failure to send SMS]]> http://status.seald.io/incident/24/ SSKS seems to fail to send SMS for authentication

15/07/2022 8h18: Issue is fixed

]]> 2022-07-15T05:30:00+00:00 Seald Status <![CDATA[Seald update]]> http://status.seald.io/incident/23/ Server disruption is expected to last for no more than a few seconds.

]]> 2022-07-07T12:30:03+00:00 Seald Status <![CDATA[[Staging] SSKS Outage]]> http://status.seald.io/incident/22/ Outage of SSKS in staging environment from 9:25 to 11:50 (Paris time). No incident in production. Now fixed.

]]> 2022-07-01T07:25:00+00:00 Seald Status <![CDATA[Seald update]]> http://status.seald.io/incident/21/ Expected to last for a few seconds

]]> 2022-06-20T12:52:41+00:00 Seald Status <![CDATA[Seald update]]> http://status.seald.io/incident/20/ Expected to last for a few seconds

]]> 2022-06-10T08:09:00+00:00 Seald Status <![CDATA[Seald update]]> http://status.seald.io/incident/19/ Expected to last for a few seconds

]]> 2022-06-09T08:24:00+00:00 Seald Status <![CDATA[SSKS maintenance]]> http://status.seald.io/incident/18/ SSKS maintenance is planned. There should be no downtime.

]]> 2022-05-09T17:11:09+00:00 Seald Status <![CDATA[SSKS maintenance]]> http://status.seald.io/incident/17/ SSKS maintenance is planned. There should be no downtime.

]]> 2022-05-06T12:48:00+00:00 Seald Status <![CDATA[Request errors]]> http://status.seald.io/incident/16/ One of our servers experienced a DNS failure. Our high-availability setup re-routed its IP to another server, so there was no extended downtime, but a small number of users may have experienced a few request errors during a short period of time.

]]> 2022-05-04T08:20:00+00:00 Seald Status <![CDATA[Seald Database migration]]> http://status.seald.io/incident/14/ Operation on Seald database. Seald API should be unavailable for up to one hour

Update: migration finished at 8:15

]]> 2022-05-01T06:00:00+00:00 Seald Status <![CDATA[Seald update]]> http://status.seald.io/incident/15/ Expected to last for a few seconds

]]> 2022-04-26T12:37:25+00:00 Seald Status <![CDATA[Unable to send/receive SMS]]> http://status.seald.io/incident/12/ Due to an incident from our provider, SMS were not delivered for a short amount of time. More info on our SMS provider: https://web-cloud.status-ovhcloud.com/incidents/99hgwfggg4j8

]]> 2022-04-08T13:00:00+00:00 Seald Status <![CDATA[SSKS DNS update]]> http://status.seald.io/incident/11/ SSKS servers are being migrated to new IPs. As old IPs are kept during migration, there should be no downtime.

]]> 2022-04-05T17:32:11+00:00 Seald Status <![CDATA[SSKS minor outage]]> http://status.seald.io/incident/10/ Due to human error, the SSKS production service was down during approximately 2 min.

]]> 2022-04-04T07:43:00+00:00 Seald Status <![CDATA[SSKS Update]]> http://status.seald.io/incident/9/ Expected to last for a few seconds

]]> 2022-04-01T15:02:50+00:00 Seald Status <![CDATA[Seald Update]]> http://status.seald.io/incident/8/ Expected to last for a few seconds

]]> 2022-03-25T15:06:00+00:00 Seald Status <![CDATA[Seald update]]> http://status.seald.io/incident/7/ Seald update

]]> 2022-02-14T14:27:06+00:00 Seald Status <![CDATA[Seald Update]]> http://status.seald.io/incident/6/ Server update. Should have no noticeable downtime.

]]> 2021-12-10T09:10:00+00:00 Seald Status <![CDATA[Seald Update]]> http://status.seald.io/incident/5/ Server update. Should have no noticeable downtime.

]]> 2021-11-30T11:30:00+00:00 Seald Status <![CDATA[Seald Update]]> http://status.seald.io/incident/4/ Server update. Should have no noticeable downtime.

]]> 2021-10-25T09:25:00+00:00 Seald Status <![CDATA[Outage due to OVH availability]]> http://status.seald.io/incident/2/ Due to an human error from our hosting provider (OVH), Seald was unavailable for 1h30. It was fixed at 10:50

]]> 2021-10-13T07:20:00+00:00