Fasterize Outage History

Fasterize is up right now

Fasterize had 12 outages in the last 2 years totaling 15h 25m of downtime — averaging 0.5 incidents per month.

There were 12 Fasterize outages since May 28, 2025 totaling 15h 25m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.fasterize.com

Minor May 20, 2026

Issue on the flush on the dashboard and API

Detected by Pingoru
May 20, 2026, 08:00 AM UTC
Resolved
May 20, 2026, 08:08 AM UTC
Duration
7m
Affected: API
Timeline · 2 updates
  1. identified May 20, 2026, 08:00 AM UTC

    We are currently fixing an issue affecting flush operations through the API and dashboard. Our team is working to restore normal behaviour as quickly as possible. We will share an update once the issue is resolved.

  2. resolved May 20, 2026, 08:08 AM UTC

    The issue affecting flush operations through the API and dashboard has been fixed. Flush actions are now working normally again.

Read the full incident report →

Notice April 10, 2026

Performance degradation

Detected by Pingoru
Apr 10, 2026, 10:49 PM UTC
Resolved
Apr 10, 2026, 08:30 PM UTC
Duration
Timeline · 1 update
  1. resolved Apr 10, 2026, 10:49 PM UTC

    We experienced some issues with our European infrastructure. Service has been restored since 00:20. This has affected loading speeds. Some pages or websites have experienced slowdowns.

Read the full incident report →

Minor February 9, 2026

INP Data Inaccuracy on Safari (iPhone)

Detected by Pingoru
Feb 09, 2026, 05:46 PM UTC
Resolved
Feb 05, 2026, 12:00 PM UTC
Duration
Timeline · 1 update
  1. resolved Feb 09, 2026, 05:46 PM UTC

    We have identified an issue affecting the accuracy of INP data collected between Thursday, 5 February and Monday, 9 February. During this period, INP metrics were incorrectly reported for Safari on iPhone when the navigation type was back-forward cache (BFCache). This behaviour is related to a known issue in WebKit, which causes inflated INP values in this specific scenario. More details are available in the related Safari bug report: https://bugs.webkit.org/show_bug.cgi?id=305251 The issue has been identified and mitigated on our side. Only the INP metric is impacted; other performance metrics remain unaffected. We apologise for any confusion this may have caused and recommend caution when analysing INP data for Safari iPhone traffic over this time window. If you have any questions, our team remains available.

Read the full incident report →

Minor November 24, 2025

Fasterize Console is slow

Detected by Pingoru
Nov 24, 2025, 02:50 PM UTC
Resolved
Nov 24, 2025, 03:43 PM UTC
Duration
52m
Affected: APIDashboard
Timeline · 3 updates
  1. investigating Nov 24, 2025, 02:50 PM UTC

    The Fasterzie Console is currently slow. We’re investigating.

  2. identified Nov 24, 2025, 03:22 PM UTC

    The issue has been identified, our team is working on resolving it

  3. resolved Nov 24, 2025, 03:43 PM UTC

    The incident has been resolved, everything is now operating normally

Read the full incident report →

Notice September 25, 2025

Some origin requests got a wrong Client IP header between 09:52 – 10:34 (Paris time)

Detected by Pingoru
Sep 25, 2025, 09:07 AM UTC
Resolved
Sep 25, 2025, 08:00 AM UTC
Duration
Timeline · 1 update
  1. resolved Sep 25, 2025, 09:07 AM UTC

    A network maintenance caused a regression in the service responsible for extracting the True-Client-IP header from the X-Forwarded-For header. Around 6% of the platform trafic has been impacted. The issue has now been resolved. We apologize for the inconvenience.

Read the full incident report →

Critical September 9, 2025

Platform has been unavailable

Detected by Pingoru
Sep 09, 2025, 01:11 PM UTC
Resolved
Sep 09, 2025, 01:51 PM UTC
Duration
39m
Affected: CDN
Timeline · 2 updates
  1. monitoring Sep 09, 2025, 01:11 PM UTC

    Between 14:49 and 14:52 (Paris time), our services were briefly disrupted due to a Distributed Denial of Service (DDoS) attack. The issue has been fully resolved, and systems are operating normally. We appreciate your patience and understanding. Sorry for the inconvenience.

  2. resolved Sep 09, 2025, 01:51 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 28, 2025

Temporary Service Disruption : Error 502

Detected by Pingoru
May 28, 2025, 07:53 AM UTC
Resolved
May 28, 2025, 07:00 AM UTC
Duration
Timeline · 1 update
  1. resolved May 28, 2025, 07:53 AM UTC

    What happened: This morning at 8:52, we made planned adjustments to our infrastructure in order to improve the reliability of the connection between our platform and CDN. During the transition, the service experienced a short disruption due to unexpected load balancer restart. Impact: The site was briefly unavailable for approximately one minute generating error 502. Resolution: The situation was quickly identified and resolved by 08:52 (GMT+2) . Everything is now back to normal and fully operational. We’re sorry for the inconvenience and are taking steps to prevent this from happening again.

Read the full incident report →