Fasterize had 18 outages in the last 2 years totaling 41h 26m of downtime — averaging 0.7 incidents per month.
There were 18 Fasterize outages since June 6, 2024 totaling 41h 26m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating an issue affecting website status checks in the console. Some websites may incorrectly appear with the status “Ping blocked” or “Sonde bloquée”. This does not necessarily mean that your website is unavailable. We will share an update as soon as possible.
This incident has been resolved.
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.
The issue affecting flush operations through the API and dashboard has been fixed. Flush actions are now working normally again.
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.
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.
The Fasterzie Console is currently slow. We’re investigating.
The issue has been identified, our team is working on resolving it
The incident has been resolved, everything is now operating normally
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.
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.
This incident has been resolved.
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.
We encountered a minor issue affecting the purge of image metadata and CSS/JS bundles. While the purge process experienced some disruptions, this had no noticeable impact on website functionality. Pages and static files were purged correctly.
Timeframe: 9:30 AM to 10:15 AM During this period, pages were served without optimization by the platform. There was no downtime, and traffic continued to be served seamlessly with original (non-optimized) pages. Cause: The issue was triggered by a recent release that unexpectedly introduced a high load on the platform. Resolution: We promptly identified the issue and rolled back the release to restore normal operations. We sincerely apologize for any inconvenience this may have caused and appreciate your understanding.
The platform experienced an outage from 10:13 AM to 10:20 AM (Paris timezone) caused by a DDOS attack. Traffic was automatically routed to origins from 10:17AM to 10:20AM. The attack volume was around 30x the normal trafic. Even if our anti DDOS system blocked 97.6% of the attack, the attack was too heavy for our frontals servers.
There is a delay in indexing CDN logs due to network maintenance. The CDN log indexing platform is behind, and the currently available logs date back to before Wednesday, June 5, 2024 at 1:45 PM. As a result, last night's log extractions for the June 5 logs are incomplete. This delay will be caught up in the next few hours. We will keep you informed.