Cargobase Outage History

Cargobase is up right now

Cargobase had 2 outages in the last 2 years totaling 14m of downtime — averaging 0.1 incidents per month.

There were 2 Cargobase outages since June 27, 2024 totaling 14m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.cargobase.com

Minor May 7, 2026

Delayed Creation of Requests and Comments

Detected by Pingoru
May 07, 2026, 06:27 AM UTC
Resolved
May 07, 2026, 06:41 AM UTC
Duration
14m
Affected: Cargobase platformCargobase Mobile Apps
Timeline · 2 updates
  1. investigating May 07, 2026, 06:27 AM UTC

    We are currently investigating an issue surrounding the delayed creation of shipments and appearance of comments. We have identified a root-cause and are working hard to resolve this quickly.

  2. resolved May 07, 2026, 06:41 AM UTC

    Problem has been resolved and service resumes as normal. Unfortunately, some manually posted comments between 05:45 and 06:15am UTC might have been lost. Apologies for the inconvenience.

Read the full incident report →

Minor September 9, 2024

Cargobase Platform Slowness

Detected by Pingoru
Sep 09, 2024, 05:01 AM UTC
Resolved
Sep 06, 2024, 08:30 AM UTC
Duration
—
Timeline · 2 updates
  1. resolved Sep 09, 2024, 05:01 AM UTC

    Cargobase Platform experienced slowness on 6th September 2024 4:30 pm SGT. The issue is resolved at 5:15 pm SGT. We are investigating the root cause.

  2. postmortem Sep 26, 2024, 07:26 AM UTC

    **Platform System Slowness** **Root Cause Analysis** **Date & Time** Issue Found: 06 Sep 2024 1630 SGT Issue Resolved: 06 Sep 2024 1715 SGT **Issue Details** On 6 Sep 2024, our software platform experienced slowness, impacting the user experience. The root cause was identified as a database query taking longer than expected to complete. **Root Cause** The slowness was traced back to an inefficient database query that took longer than expected to complete. This caused delays in the system’s ability to process user requests in a timely manner. **Corrective Action** · The problematic database query was reviewed and optimized to reduce execution time. · Post-optimization, the system’s performance returned to expected levels. **Preventive Action** Monitoring tools have been put in place to proactively identify and address any future performance issues related to database queries.

Read the full incident report →