Cognitive3D Outage History

Cognitive3D is up right now

Cognitive3D had 3 outages in the last 2 years totaling 5h 49m of downtime — averaging 0.1 incidents per month.

There were 3 Cognitive3D outages since November 20, 2024 totaling 5h 49m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: http://status.cognitive3d.com

Notice May 29, 2026

Delayed Session

Detected by Pingoru
May 29, 2026, 04:21 PM UTC
Resolved
May 29, 2026, 04:44 PM UTC
Duration
23m
Affected: Cognitive3D Data Processing
Timeline · 2 updates
  1. investigating May 29, 2026, 04:21 PM UTC

    Session will be delayed by 15-20 minutes

  2. resolved May 29, 2026, 04:44 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 13, 2026

Delayed Session Processing

Detected by Pingoru
May 13, 2026, 12:42 PM UTC
Resolved
May 13, 2026, 04:13 PM UTC
Duration
3h 31m
Affected: Cognitive3D DashboardCognitive3D Scene ExplorerCognitive3D Data Processing
Timeline · 4 updates
  1. investigating May 13, 2026, 12:42 PM UTC

    We are investigating an issue causing a delay in session processing. Session data may take longer than usual to appear on the dashboard.

  2. identified May 13, 2026, 01:33 PM UTC

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

  3. monitoring May 13, 2026, 01:51 PM UTC

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

  4. resolved May 13, 2026, 04:13 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical November 20, 2024

Session Processing Delays

Detected by Pingoru
Nov 20, 2024, 07:43 PM UTC
Resolved
Nov 20, 2024, 09:37 PM UTC
Duration
1h 53m
Affected: Cognitive3D Data Processing
Timeline · 2 updates
  1. investigating Nov 20, 2024, 07:43 PM UTC

    We are investigating an issue causing delays in session processing. Some data may take longer than usual to appear on the dashboard. All data is still being collected.

  2. resolved Nov 20, 2024, 09:37 PM UTC

    This incident has been resolved.

Read the full incident report →