Foleon Outage History

Foleon is up right now

Foleon had 3 outages in the last 2 years totaling 1h 55m of downtime — averaging 0.1 incidents per month.

There were 3 Foleon outages since August 5, 2025 totaling 1h 55m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.foleon.com

Notice December 17, 2025

Media Library Issue

Detected by Pingoru
Dec 17, 2025, 12:31 PM UTC
Resolved
Dec 17, 2025, 01:34 PM UTC
Duration
1h 2m
Affected: Foleon Docs
Timeline · 3 updates
  1. investigating Dec 17, 2025, 12:31 PM UTC

    We are currently experiencing intermittent issues in the Media Library that could cause the page to show an error when you select an asset. We are investigating the root cause.

  2. identified Dec 17, 2025, 12:58 PM UTC

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

  3. resolved Dec 17, 2025, 01:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 23, 2025

Technical Issue

Detected by Pingoru
Oct 23, 2025, 09:20 AM UTC
Resolved
Oct 23, 2025, 09:55 AM UTC
Duration
34m
Affected: Foleon DocsPlatform
Timeline · 2 updates
  1. investigating Oct 23, 2025, 09:20 AM UTC

    We are experiencing an issue that may be affecting the performance and stability of the editor.

  2. resolved Oct 23, 2025, 09:55 AM UTC

    This incident has been resolved.

Read the full incident report →

Major August 5, 2025

Ongoing Maintenance Affecting Editor and Dashboard

Detected by Pingoru
Aug 05, 2025, 05:10 AM UTC
Resolved
Aug 05, 2025, 05:28 AM UTC
Duration
18m
Affected: PlatformFoleon AnalyticsPublishing queueAPI
Timeline · 4 updates
  1. identified Aug 05, 2025, 05:10 AM UTC

    We’re currently addressing an unexpected issue that occurred during a routine maintenance operation. As a result, the editor and dashboard may remain temporarily unavailable longer than initially expected. Published content remains fully online and accessible. We’re working to resolve this as quickly as possible and will continue to provide updates here. Thank you for your patience and understanding.

  2. identified Aug 05, 2025, 05:10 AM UTC

    We are continuing to work on a fix for this issue.

  3. monitoring Aug 05, 2025, 05:24 AM UTC

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

  4. resolved Aug 05, 2025, 05:28 AM UTC

    This incident has been resolved.

Read the full incident report →