История сбоев Milibris

Notre plateforme rencontre actuellement des latences sur certains services, ce qui peut impacter la publication. Nos équipes sont mobilisées et travaillent activement à la mise en place d’un correctif dans les plus brefs délais. --- Our platform is currently experiencing latency on certain services, which may impact publishing. Our teams are mobilized and are actively working to deploy a fix as quickly as possible.

Un correctif a été mis en place et la situation a été corrigée. Nos équipes demeurent en surveillance de nos systèmes, mais les publications effectuées après 22h30 ne devraient plus être impactées. --- A fix has been deployed and the situation has been resolved. Our teams remain monitoring our systems, but publications made after 10:30 PM should no longer be impacted.

Le correctif déployé à 22h30 a résolu la latence observée. Après une nuit de surveillance sans nouvel événement, nous procédons à la clôture de cet incident. --- The fix deployed at 10:30 PM resolved the observed latency. Following an overnight monitoring period with no further issues, we are proceeding with closing this incident.

Nos équipes restent en surveillance cette nuit pour s’assurer du bon déroulement des publications --- Our teams will remain on standby tonight to ensure that the publications process runs properly.

Nous rencontrons un problème de publication ce matin. Nos équipes sont mobilisées. --- We are experiencing a publishing issue this morning. Our teams are working on it.

Plusieurs correctifs ont été déployés cet après-midi sur notre infrastructure. Nos équipes resteront en surveillance pendant la nuit et jusqu’à la publication des éditions. --- Several fixes were deployed this afternoon on our infrastructure. Our teams will remain on monitoring duty throughout the night and until the editions are published.

This incident has been resolved.

Maintenance miLibris imminente --- miLibris Maintenance About to Begin

Maintenance miLibris : Pour rappel tous les services miLibris seront interrompus à partir de 23H CET (UTC+2) / 17H EDT/AST (UTC−4) pour une durée de 3 heures environ . Les kiosques web, les applications, le backoffice, les APIS, le ftp seront indisponibles. Merci pour votre compréhension. --- miLibris Maintenance: As a reminder, all miLibris services will be interrupted starting at 11:00 PM CET (UTC+2) / 5:00 PM EDT/AST (UTC−4) for approximately 3 hours . The web kiosks, applications, back office, APIs, and FTP will be unavailable. Thank you for your understanding.

Maintenance en cours : Le service miLibris est interrompu pour une durée estimée de 3 heures . Merci pour votre compréhension. --- Maintenance in progress: The miLibris service is unavailable for an estimated duration of 3 hours . Thank you for your understanding.

miLibris a migré vers sa nouvelle infrastructure. Nos équipes procèdent actuellement aux tests de vérification du service. La réouverture se fait de manière progressive. --- miLibris has migrated to its new infrastructure. Our teams are currently performing service verification tests. The reopening is being carried out progressively.

La maintenance miLibris est terminée. Le service est à nouveau opérationnel. Nos équipes restent mobilisées. Nouvelle url pour le backoffice : https://manager.milibris.com/. Vos identifiants et mots de passe ne changent pas --- miLibris maintenance is complete. The service is operational again. Our teams remain mobilized. New backoffice URL: https://manager.milibris.com/. Your login and password remain unchanged.

Des processus de traitement sont encore en cours pour certains titres. Nos équipes sont mobilisées afin de les publier dans les meilleurs délais. --- Processing is still ongoing for some titles. Our teams are actively working to publish them as quickly as possible.

Les processus de traitement des publications manquantes sont terminés. Nos équipes restent en surveillance. --- The publication processing procedures missing have been completed. Our teams remain on standby.

Un bref incident sur nos services DNS a affecté le chargement des contenus sur nos kiosques. La cause a été identifiée et un correctif appliqué. Le service reprendra pleinement au cours des prochaines minutes. --- A brief incident with our DNS services affected content loading on our kiosks. The cause has been identified and a fix applied. Service will be fully restored within the next few minutes.

We’re currently experiencing an issue with our Reader. Our technical team has been working on it and is actively working on a fix. Thank you for your understanding.

The issue has been identified and a fix is being implemented.

Our team is still working hard and doing everything possible to ensure that the service will be secure tomorrow.

The Service has been reestablished. We remain focused on ensuring that everything is working properly.

This incident has been resolved.

We’re currently experiencing an issue with our API. Our technical team has been working on it since 9:00 AM and is actively working on a fix. Thank you for your understanding.

We are continuing to investigate this issue.

The service has been restored at 10.15 am

We’re currently experiencing an issue with our API. Our technical team has been working on it since 8:00 AM and is actively working on a fix. Thank you for your understanding.

The service has now been restored. Our technical team is continuing to monitor the situation to ensure stability.

We’re currently experiencing an issue with our API. Our technical team has been working on it since 8:00 AM and is actively working on a fix. Thank you for your understanding.

We are continuing to investigate this issue.

The service has now been restored. Our technical team is continuing to monitor the situation to ensure stability. Thank you for your patience and understanding.

This incident has been resolved.

The service is experiencing instabilities. Our technical team is currently working to isolate the problem and restore service.

The service has returned to normal since 10 a.m. but our tech team remains on call to ensure that it is sustainable.

The incident is closed. The miLibis push service will remain down this weekend for early-week maintenance. We apologize for the inconvenience this morning, lasting a few dozen minutes.

Our technical team is working to restore service as quickly as possible.

The situation has just returned to normal, and our teams are continuing to monitor developments.

This incident has been resolved.

English version will follow. Nous rencontrons actuellement des ralentissements dans le traitement et l'ingestion des contenus. Nos équipes techniques sont mobilisées et travaillent activement à résoudre cette situation dans les plus brefs délais. Nous vous remercions de votre patience et nous excusons pour tout désagrément causé. Nous vous tiendrons informés dès que la performance de notre service sera rétablie. --- We are currently experiencing slowdowns in processing and ingesting content. Our technical teams are mobilized and actively working to resolve this situation as quickly as possible. We thank you for your patience and apologize for any inconvenience caused. We will keep you informed as soon as the performance of our service is restored.

English message will follow Nous avons identifié la source du ralentissement du service et sommes en train de valider la reprise normale des activités sur nos serveurs. Les services de publication devraient reprendre progressivement au cours des prochaines minutes. --- We have identified the source of the service slowdown and are currently validating the resumption of normal activities on our servers. Publication services should gradually resume over the next few minutes.

English message will follow Nous rencontrons actuellement des ralentissements dans notre système d'ingestion de contenu. Nous avons identifié plus tôt la source de la perturbation et sommes progressivement en train de rétablir le service. Cependant, il pourrait encore falloir quelques heures pour que l'ensemble des publications en cours soient traitées et publiées. Nous vous remercions de votre patience et nous excusons sincèrement pour tout désagrément que cela peut engendrer. Nous vous tiendrons informés dès que la performance de notre service sera complètement restaurée. --- We are currently experiencing slowdowns in our content ingestion system. We identified the source of the disruption earlier and are gradually restoring the service. However, it may still take a few hours for all ongoing publications to be processed and published. We thank you for your patience and sincerely apologize for any inconvenience this may cause. We will keep you informed as soon as our service performance is fully restored.

English message will follow La situation se stabilise progressivement et la plupart des titres sont publiés ou en cours de publication. Nos équipes restent vigilantes et continuent de surveiller la situation de près. Nous sommes sincèrement désolés pour les désagréments occasionnés et vous assurons que des mesures sont en cours d'élaboration pour éviter que ce type de problème ne se reproduise. Merci de votre compréhension. --- The situation is gradually stabilizing, and most titles are either published or in the process of being published. Our teams remain vigilant and continue to closely monitor the situation. We sincerely apologize for any inconvenience caused and assure you that measures are being developed to prevent this type of issue from recurring. Thank you for your understanding.

We are continuing to monitor for any further issues.

English message will follow Nous sommes heureux de vous informer que la situation a été résolue avec succès. Tous les titres ont été publiés et nos équipes ont confirmé que le problème a été entièrement résolu. Nous tenons à exprimer notre gratitude pour votre patience et votre compréhension tout au long de cet incident. Soyez assurés que des mesures ont été prises pour prévenir toute récurrence de ce type de problème à l'avenir. Nous continuons à surveiller l'évolution de la situation. --- We are pleased to inform you that the situation has been successfully resolved. All titles have been published, and our teams have confirmed that the issue has been fully addressed. We would like to express our gratitude for your patience and understanding throughout this incident. Rest assured, measures have been implemented to prevent any recurrence of such issues in the future. We are continuing to monitor for any further issues. Thank you once again for your continued support.

Nous avons des intermittences dans le service d'appel à notre API, ce qui provoque des erreurs 500 sur nos kiosques. Nos équipes sont à l'œuvre pour stabiliser la situation et rétablir le service. --- We are experiencing intermittencies in the call service to our API, which is causing 500 errors on our kiosks. Our teams are working to stabilize the situation and restore the service.

Un nouveau correctif a été apporté par l'équipe, et la plateforme regagne en stabilité. Notre équipe reste en veille pour les prochaines heures afin de s'assurer de la continuité du service. --- A new patch has been implemented by the team, and the platform is regaining stability. Our team will remain on standby for the next few hours to ensure the continuity of the service.

Some routes of the API are failing, we are investigating the root cause of the problem. The service is partially impacted.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are currently investigating this issue.

A fix has been implemented and we are monitoring the results.

Everything is now up and running. Our core storage array started to malfunction around 4:00am this morning, making our data partially unavailable for the rest of our services. The root cause appears to be a hardware bug on the controller managing the array, and we are starting an in-depth analysis to determine the next corrective actions.

Our provider is experiencing a major network outage, all miLibris services are currently affected.

All the services are restored, we keep monitoring the situation to ensure that everything is working properly.

This incident has been resolved.

We are currently experiencing an outage on several services, we are working on solving this issue and will keep you updated. Affected servcies are : console management, ftp uploads and support website.

All services are back online and we are monitoring the situation

We are continuing to monitor for any further issues.

This incident has been resolved.

Our core database suffered a network outage for 50 minutes tonight, between 2:30 AM and 3:20 AM. The incident has been resolved, but we are still investigating disruption of our services.

At 4AM this night, our hoster lost one of its datacenter to fire. All backup components are up and running except the following services: * documentation website * FTP stats exports We are actively working to have those services back online as soon as possible. Thank your for your comprehension

The documentation website is back up and FTP service for the stats exports is back online. We have regenerated exports of the 09/03.

This incident has been resolved.

We are experiencing a shortage on our core API, we are investigating the root cause of this issue.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are experiencing a network outage affecting most of our services.

We are continuing to investigate this issue.

The root cause of the outage is a faulty network infrastructure in our hoster datacenters. Our services are coming back online and we are monitoring our servers to ensure all services are properly restored.

This incident has been resolved.