eloomi Outage History

eloomi is up right now

eloomi had 6 outages in the last 2 years totaling 16h 33m of downtime — averaging 0.2 incidents per month.

There were 6 eloomi outages since June 12, 2025 totaling 16h 33m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.eloomi.com

Major December 5, 2025

Cloudflare Outage affecting eloomi instances

Detected by Pingoru
Dec 05, 2025, 09:00 AM UTC
Resolved
Dec 05, 2025, 10:10 AM UTC
Duration
1h 9m
Affected: eloomi Infinite web applicationeloomi People web applicationeloomi Infinite APIeloomi Infinite Mobile ApplicationSCORM playerSCORM player
Timeline · 3 updates
  1. investigating Dec 05, 2025, 09:00 AM UTC

    Our customers may be affected by a Cludflare outage that is affecting eloomi instances across multiple regions and products. We will continue to monitor and work closely with Cloudflare to ensure service is resumed ASAP

  2. monitoring Dec 05, 2025, 09:29 AM UTC

    Cloudflare has implemented a fix and eloomi environments are up and running again. We will continue to monitor this from our end to ensure optimal service availability

  3. resolved Dec 05, 2025, 12:05 PM UTC

    All systems are operational across all regions

Read the full incident report →

Minor October 13, 2025

Latency assigning learning to users

Detected by Pingoru
Oct 13, 2025, 04:55 PM UTC
Resolved
Oct 13, 2025, 07:30 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Oct 13, 2025, 04:55 PM UTC

    The issue causing latency when assigning learning to newly added users has now been resolved. New users should now appear correctly and without delay in assignment lists.

Read the full incident report →

Minor October 9, 2025

Degraded Performance across eloomi

Detected by Pingoru
Oct 09, 2025, 03:00 AM UTC
Resolved
Oct 09, 2025, 05:41 PM UTC
Duration
14h 41m
Affected: eloomi Infinite web application
Timeline · 3 updates
  1. investigating Oct 09, 2025, 03:14 PM UTC

    We are currently experiencing degraded performance within the Learning Service. Users may experience slower load times, delays when accessing courses or launching training, or intermittent timeouts.

  2. identified Oct 09, 2025, 03:17 PM UTC

    The issue creating degraded performance has been identified and an optimization is being developed to resolve this challenge.

  3. resolved Oct 09, 2025, 05:41 PM UTC

    A patch has been deployed to address the degraded performance experienced within the Learning Service. We are continuing to monitor performance to ensure that response times remain within acceptable limits.

Read the full incident report →

Minor October 8, 2025

Latency experienced

Detected by Pingoru
Oct 08, 2025, 07:53 AM UTC
Resolved
Oct 07, 2025, 09:30 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Oct 08, 2025, 07:53 AM UTC

    Some of our customers experienced Latency while accessing their Learning environments. Our team was able to identify the root cause and resolve this

Read the full incident report →

Major September 10, 2025

Incident Update - Latency Resolved

Detected by Pingoru
Sep 10, 2025, 08:00 PM UTC
Resolved
Sep 10, 2025, 08:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Sep 11, 2025, 09:47 AM UTC

    Between 22:05 and 22:30 CEST on September 10th, some users experienced latency on the eloomi platform due to database performance issues. The issue has been resolved by scaling and optimizing the database, and the platform is now operating normally. We will continue monitoring closely to ensure stability.

Read the full incident report →

Minor June 12, 2025

Platform Slowness

Detected by Pingoru
Jun 12, 2025, 08:13 PM UTC
Resolved
Jun 12, 2025, 08:55 PM UTC
Duration
42m
Affected: eloomi People web application
Timeline · 3 updates
  1. investigating Jun 12, 2025, 08:13 PM UTC

    Some customers may experience slow speeds or inaccessibility on their platforms. Our engineers are working hard to resolve the issue. We will send updates as the issue progresses.

  2. investigating Jun 12, 2025, 08:13 PM UTC

    We are continuing to investigate this issue.

  3. resolved Jun 12, 2025, 08:55 PM UTC

    This incident has been resolved.

Read the full incident report →