miLibris Outage History

miLibris is up right now

Pingoru has recorded 56 incidents for miLibris: 1 in the last 12 months and 0 in the last 90 days.

Source: status.milibris.com

56incidents recorded
1last 12 months
0last 90 days
7 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking miLibris in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 513 (0%)

Incidents, newest first

Minor January 14, 2026 Latences de services / Service latency 7h Publication

Started Jan 14, 2026, 09:30 PM UTC· resolved Jan 15, 2026, 04:31 AM UTC

  1. investigating Jan 14, 2026, 09:30 PM UTC

    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.

  2. monitoring Jan 14, 2026, 09:44 PM UTC

    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.

  3. resolved Jan 15, 2026, 04:31 AM UTC

    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.

Read the full incident report →

Notice September 14, 2025 Maintenance : surveillance des publications 1d 17h Publication

Started Sep 14, 2025, 05:00 PM UTC· resolved Sep 16, 2025, 10:18 AM UTC

  1. monitoring Sep 14, 2025, 05:26 PM UTC

    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.

  2. monitoring Sep 15, 2025, 04:23 AM UTC

    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.

  3. monitoring Sep 15, 2025, 06:50 PM UTC

    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.

  4. resolved Sep 16, 2025, 10:18 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 13, 2025 Maintenance miLibris 16h 44m v4.x, FR, Console, US and 7 more

Started Sep 13, 2025, 06:00 PM UTC· resolved Sep 14, 2025, 10:44 AM UTC

  1. investigating Sep 13, 2025, 06:01 PM UTC

    Maintenance miLibris imminente --- miLibris Maintenance About to Begin

  2. investigating Sep 13, 2025, 06:07 PM UTC

    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.

  3. investigating Sep 13, 2025, 09:02 PM UTC

    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.

  4. monitoring Sep 14, 2025, 12:12 AM UTC

    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.

  5. monitoring Sep 14, 2025, 01:14 AM UTC

    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.

  6. monitoring Sep 14, 2025, 05:20 AM UTC

    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.

  7. resolved Sep 14, 2025, 10:44 AM UTC

    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.

Read the full incident report →

Notice September 8, 2025 Problème DNS en cours – Static

Started Sep 08, 2025, 12:54 PM UTC· resolved Sep 08, 2025, 12:54 PM UTC

  1. resolved Sep 08, 2025, 12:54 PM UTC

    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.

Read the full incident report →

Minor July 18, 2025 Reader incident 8h 20m Publication

Started Jul 18, 2025, 10:33 AM UTC· resolved Jul 18, 2025, 06:54 PM UTC

  1. investigating Jul 18, 2025, 10:33 AM UTC

    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.

  2. identified Jul 18, 2025, 10:34 AM UTC

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

  3. identified Jul 18, 2025, 03:16 PM UTC

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

  4. monitoring Jul 18, 2025, 06:03 PM UTC

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

  5. resolved Jul 18, 2025, 06:54 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 21, 2025 Incident on API V4 8h 12m v4.x

Started May 21, 2025, 07:46 AM UTC· resolved May 21, 2025, 03:58 PM UTC

  1. investigating May 21, 2025, 07:46 AM UTC

    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.

  2. investigating May 21, 2025, 07:48 AM UTC

    We are continuing to investigate this issue.

  3. investigating May 21, 2025, 07:49 AM UTC

    We are continuing to investigate this issue.

  4. resolved May 21, 2025, 03:58 PM UTC

    The service has been restored at 10.15 am

Read the full incident report →

Major May 16, 2025 API issue 1h 39m v4.x, Publication, v5.x

Started May 16, 2025, 07:38 AM UTC· resolved May 16, 2025, 09:17 AM UTC

  1. investigating May 16, 2025, 07:38 AM UTC

    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.

  2. resolved May 16, 2025, 09:17 AM UTC

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

Read the full incident report →

Critical May 15, 2025 Ongoing Incident – API 1d 1h v4.x, Console, Publication, Multimedia Editor and 2 more

Started May 15, 2025, 07:20 AM UTC· resolved May 16, 2025, 09:15 AM UTC

  1. investigating May 15, 2025, 07:20 AM UTC

    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.

  2. investigating May 15, 2025, 07:21 AM UTC

    We are continuing to investigate this issue.

  3. investigating May 15, 2025, 07:22 AM UTC

    We are continuing to investigate this issue.

  4. monitoring May 15, 2025, 08:04 AM UTC

    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.

  5. resolved May 16, 2025, 09:15 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 25, 2025 Current incident on API V4 2h 16m v4.x

Started Apr 25, 2025, 07:56 AM UTC· resolved Apr 25, 2025, 10:12 AM UTC

  1. investigating Apr 25, 2025, 07:56 AM UTC

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

  2. monitoring Apr 25, 2025, 08:20 AM UTC

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

  3. resolved Apr 25, 2025, 10:12 AM UTC

    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.

Read the full incident report →