injixo Outage History

injixo is up right now

injixo had 12 outages in the last 2 years totaling 135h 47m of downtime — averaging 0.5 incidents per month.

There were 12 injixo outages since June 18, 2025 totaling 135h 47m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.injixo.com

Minor May 27, 2026

Adherence statuses not in sync

Detected by Pingoru
May 27, 2026, 10:50 AM UTC
Resolved
May 27, 2026, 12:44 PM UTC
Duration
1h 53m
Affected: Intraday
Timeline · 5 updates
  1. investigating May 27, 2026, 10:50 AM UTC

    Some customers experience Adherence statuses not being correct. We are investigating the issue.

  2. identified May 27, 2026, 11:12 AM UTC

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

  3. monitoring May 27, 2026, 11:13 AM UTC

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

  4. monitoring May 27, 2026, 11:21 AM UTC

    The fix seems to work, we see decreased refresh times. We are backfilling the historical adherence status.

  5. resolved May 27, 2026, 12:44 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 13, 2026

Logouts malfunctions in Shift Center

Detected by Pingoru
Mar 13, 2026, 02:39 PM UTC
Resolved
Mar 13, 2026, 08:48 PM UTC
Duration
6h 9m
Timeline · 2 updates
  1. identified Mar 13, 2026, 02:39 PM UTC

    There was a problem identified, resulting in agent logouts not being accepted in Shift Center (only). The fix is currently prepared, and since it requires your environment restart, it will be applied automatically during the nearest maintenance window.

  2. resolved Mar 13, 2026, 08:48 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 12, 2026

Delayed processing of queue data

Detected by Pingoru
Mar 12, 2026, 11:31 AM UTC
Resolved
Mar 12, 2026, 07:53 PM UTC
Duration
8h 22m
Affected: ForecastIntegrations
Timeline · 4 updates
  1. investigating Mar 12, 2026, 11:31 AM UTC

    We are currently investigating this issue.

  2. identified Mar 12, 2026, 01:28 PM UTC

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

  3. monitoring Mar 12, 2026, 04:52 PM UTC

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

  4. resolved Mar 12, 2026, 07:53 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 9, 2026

SSO login issues

Detected by Pingoru
Jan 09, 2026, 11:48 AM UTC
Resolved
Jan 09, 2026, 03:03 PM UTC
Duration
3h 15m
Affected: Account
Timeline · 3 updates
  1. investigating Jan 09, 2026, 11:48 AM UTC

    Currently, login via SSO is not possible. The login via user name and password still works as expected. We're investigating the situation.

  2. monitoring Jan 09, 2026, 12:03 PM UTC

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

  3. resolved Jan 09, 2026, 03:03 PM UTC

    This incident has been resolved.

Read the full incident report →

Major December 8, 2025

Optimization might fail with an error

Detected by Pingoru
Dec 08, 2025, 10:25 AM UTC
Resolved
Dec 09, 2025, 08:25 AM UTC
Duration
21h 59m
Affected: Plan
Timeline · 3 updates
  1. investigating Dec 08, 2025, 10:25 AM UTC

    This morning, we have received reports about optimization process failing for some customers. The problem is under investigation.

  2. monitoring Dec 08, 2025, 03:58 PM UTC

    We have found and fixed the problem. The fix will be deployed at a regular maintenance window. If the fix is needed earlier, please let us know.

  3. resolved Dec 09, 2025, 08:25 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical October 24, 2025

Forecast outage

Detected by Pingoru
Oct 24, 2025, 06:49 AM UTC
Resolved
Oct 24, 2025, 09:15 AM UTC
Duration
2h 25m
Affected: Forecast
Timeline · 3 updates
  1. investigating Oct 24, 2025, 06:49 AM UTC

    We are currently investigating this issue.

  2. monitoring Oct 24, 2025, 06:53 AM UTC

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

  3. resolved Oct 24, 2025, 09:15 AM UTC

    This incident has been resolved.

Read the full incident report →

Major September 18, 2025

Delayed processing of agent status data

Detected by Pingoru
Sep 18, 2025, 12:25 PM UTC
Resolved
Sep 18, 2025, 03:35 PM UTC
Duration
3h 10m
Affected: IntradayIntegrations
Timeline · 3 updates
  1. identified Sep 18, 2025, 12:25 PM UTC

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

  2. monitoring Sep 18, 2025, 01:22 PM UTC

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

  3. resolved Sep 18, 2025, 03:35 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical July 31, 2025

API Docs not available

Detected by Pingoru
Jul 31, 2025, 02:25 PM UTC
Resolved
Aug 01, 2025, 12:45 PM UTC
Duration
22h 20m
Affected: API Documentation
Timeline · 4 updates
  1. investigating Jul 31, 2025, 02:25 PM UTC

    Our public API documentation is currently not available. We are investigating the issue.

  2. identified Aug 01, 2025, 08:56 AM UTC

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

  3. monitoring Aug 01, 2025, 09:48 AM UTC

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

  4. resolved Aug 01, 2025, 12:45 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 18, 2025

Real-Time/Intraday adherence issues

Detected by Pingoru
Jun 18, 2025, 09:56 PM UTC
Resolved
Jun 20, 2025, 11:31 AM UTC
Duration
1d 13h
Affected: Intraday
Timeline · 3 updates
  1. investigating Jun 18, 2025, 09:56 PM UTC

    We received multiple Tickets about faulty Real-Time Adherence data, especially agents being shown offline, and Intraday data not being updated correctly. We are currently investigating the issues.

  2. monitoring Jun 20, 2025, 08:14 AM UTC

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

  3. resolved Jun 20, 2025, 11:31 AM UTC

    This incident has been resolved, we are working on backfilling the data that might have been wrongly imported during the outage.

Read the full incident report →