Pearl Organisation Outage History

Pearl Organisation is up right now

Pingoru has recorded 23 incidents for Pearl Organisation: 3 in the last 12 months and 0 in the last 90 days.

Source: pearlorganisation.statuspage.io

23incidents recorded
3last 12 months
0last 90 days
2 daystypical duration

Incidents, newest first

Major July 15, 2026 WhatsApp Notifications Not Receiving 5d 12h Pearl Client Workspace (Web), Global ERP Systems, Pearl Client Workspace (ios App), Pearl Client Workspace (Android App) and 3 more

Started Jul 15, 2026, 03:48 PM UTC· resolved Jul 21, 2026, 04:07 AM UTC

  1. identified Jul 15, 2026, 03:48 PM UTC

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

  2. monitoring Jul 17, 2026, 11:48 AM UTC

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

  3. resolved Jul 21, 2026, 04:07 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 5, 2026 Servers Upgradation Under Process 13h 1m Pearl Client Workspace (Web), Pearl Client Workspace (ios App), Pearl Client Workspace (Android App), PearlChat and 1 more

Started Feb 05, 2026, 04:46 PM UTC· resolved Feb 06, 2026, 05:48 AM UTC

  1. identified Feb 05, 2026, 04:46 PM UTC

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

  2. monitoring Feb 06, 2026, 05:19 AM UTC

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

  3. monitoring Feb 06, 2026, 05:19 AM UTC

    We are continuing to monitor for any further issues.

  4. resolved Feb 06, 2026, 05:48 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical December 27, 2024 Pearl Calls Failure 2d 22h Pearl Client Workspace (Web), Global ERP Systems, Pearl Client Workspace (ios App), Pearl Client Workspace (Android App) and 1 more

Started Dec 27, 2024, 08:06 AM UTC· resolved Dec 30, 2024, 06:39 AM UTC

  1. investigating Dec 27, 2024, 08:06 AM UTC

    We are currently investigating this issue.

  2. investigating Dec 27, 2024, 08:10 AM UTC

    We are continuing to investigate this issue.

  3. identified Dec 27, 2024, 08:18 AM UTC

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

  4. monitoring Dec 30, 2024, 06:26 AM UTC

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

  5. monitoring Dec 30, 2024, 06:26 AM UTC

    We are continuing to monitor for any further issues.

  6. resolved Dec 30, 2024, 06:39 AM UTC

    This incident has been resolved.

Read the full incident report →