Foleon Outage History

Foleon is up right now

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

There were 3 Foleon outages since October 23, 2025 totaling 3h 4m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.foleon.com

Notice September 9, 2026

Public Preview Access Issue

Detected by Pingoru
Sep 09, 2026, 02:59 PM UTC
Resolved
Sep 09, 2026, 04:26 PM UTC
Duration
1h 26m
Affected: Foleon Docs
Timeline · 3 updates
  1. investigating Sep 09, 2026, 02:59 PM UTC

    We are experiencing issues while accessing public previews. Our team is actively working on identifying the root cause, and we'll share an update as soon as we have more information.

  2. identified Sep 09, 2026, 03:55 PM UTC

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

  3. resolved Sep 09, 2026, 04:26 PM UTC

    This incident has been resolved.

Read the full incident report →

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 →