DataFalcon Outage History

DataFalcon is up right now

DataFalcon had 3 outages in the last 2 years totaling 20h 35m of downtime, averaging 0.1 incidents per month.

There were 3 DataFalcon outages since December 5, 2024 totaling 20h 35m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: datafalcon.statuspage.io

Critical June 12, 2025

Service Downtime Caused by Cloud Infrastructure Provider Issue

Detected by Pingoru
Jun 12, 2025, 12:55 AM UTC
Resolved
Jun 12, 2025, 07:15 PM UTC
Duration
18h 20m
Affected: Web Application
Timeline · 2 updates
  1. investigating Jun 13, 2025, 12:55 AM UTC

    We are currently investigating this issue.

  2. resolved Jun 13, 2025, 12:57 AM UTC

    Our web application experienced a temporary outage due to an issue with our cloud infrastructure provider. The disruption began earlier today and has since been resolved. Service was fully restored. We appreciate your patience and understanding.

Read the full incident report →

Major December 12, 2024

Some AI services have high latency

Detected by Pingoru
Dec 12, 2024, 12:11 AM UTC
Resolved
Dec 12, 2024, 01:36 AM UTC
Duration
1h 24m
Affected: AI Services
Timeline · 4 updates
  1. identified Dec 12, 2024, 12:11 AM UTC

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

  2. monitoring Dec 12, 2024, 01:27 AM UTC

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

  3. monitoring Dec 12, 2024, 01:29 AM UTC

    We are continuing to monitor for any further issues.

  4. resolved Dec 12, 2024, 01:36 AM UTC

    This incident has been resolved.

Read the full incident report →

Major December 5, 2024

AI service has a high error rate

Detected by Pingoru
Dec 05, 2024, 12:43 AM UTC
Resolved
Dec 05, 2024, 01:34 AM UTC
Duration
50m
Affected: AI Services
Timeline · 3 updates
  1. investigating Dec 05, 2024, 12:43 AM UTC

    We are currently investigating this issue.

  2. identified Dec 05, 2024, 12:50 AM UTC

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

  3. resolved Dec 05, 2024, 01:34 AM UTC

    This incident has been resolved.

Read the full incident report →