May <var data-var='date'>22</var>, <var data-var='time'>17:18</var> CEST Resolved - Incident is closed since 11:30am but we keep on monitoring as the incident on our hosting provider is not fully resolved. May <var data-var='date'>22</var>, <var data-var='time'>11:53</var> CEST Update - We are continuing to monitor for any further issues. May <var data-var='date'>22</var>, <var data-var='time'>11:44</var> CEST Monitoring - Everything is back to normal but we're still monitoring. Root cause seems to be a power issue in a datacenter. May <var data-var='date'>22</var>, <var data-var='time'>11:33</var> CEST Investigating - We currently have some issues on our European infrastructure. Impact on acceleration. Some pages can have some slowdowns. We're investigating but seems to be due to our hosting provider partial outage https://status.scaleway.com/incidents/qkj49g6g3ykp

Performance degradation

May <var data-var='date'>21</var>, <var data-var='time'>07:38</var> CEST Resolved - This incident has been resolved. May <var data-var='date'>20</var>, <var data-var='time'>12:33</var> CEST Identified - 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.

Website status may incorrectly show as “Ping blocked”

May <var data-var='date'>20</var>, <var data-var='time'>10:08</var> CEST Resolved - The issue affecting flush operations through the API and dashboard has been fixed. Flush actions are now working normally again. May <var data-var='date'>20</var>, <var data-var='time'>10:00</var> CEST Identified - 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.

Issue on the flush on the dashboard and API

Apr <var data-var='date'>10</var>, <var data-var='time'>22:30</var> CEST Resolved - 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.

Feb <var data-var='date'> 5</var>, <var data-var='time'>13:00</var> CET Resolved - 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.

INP Data Inaccuracy on Safari (iPhone)

Feb <var data-var='date'> 3</var>, <var data-var='time'>17:09</var> CET Completed - The scheduled maintenance on the EdgeSEO platform has now been successfully completed at 3:00 pm (CET). During the operation, we unfortunately experienced a brief interruption of approximately one minute at 2:57 pm, caused by a restart of the underlying engine. The service was restored immediately afterwards. We sincerely apologise for any inconvenience this may have caused and thank you for your understanding. Our teams monitored the operation closely and can confirm that no data loss or corruption occurred. Feb <var data-var='date'> 3</var>, <var data-var='time'>13:40</var> CET In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jan <var data-var='date'>30</var>, <var data-var='time'>09:03</var> CET Scheduled - Hello, We would like to inform you of a scheduled maintenance operation on Tuesday, 3 February 2026, affecting a platform component used by EdgeSEO for website configuration management and data storage. 🕒 Maintenance window: 2 pm – 2:15 pm (CET) ⏱ Expected impact: a very brief interruption (up to ~3 minutes) on EdgeSEO-related data storage, which may occur at any time during this window. This maintenance is part of our ongoing efforts to strengthen reliability and security. No impact on overall platform performance is expected outside of this short interruption. Our teams will be fully mobilised throughout the operation to ensure a smooth execution, with no risk of data loss or corruption. Thank you for your understanding. If you have any questions, our support team remains at your disposal. The Fasterize team

Scheduled maintenance on website configuration management and data storage

Nov <var data-var='date'>24</var>, <var data-var='time'>16:43</var> CET Resolved - The incident has been resolved, everything is now operating normally Nov <var data-var='date'>24</var>, <var data-var='time'>16:22</var> CET Identified - The issue has been identified, our team is working on resolving it Nov <var data-var='date'>24</var>, <var data-var='time'>15:50</var> CET Investigating - The Fasterzie Console is currently slow. We’re investigating.

Fasterize Console is slow

Nov <var data-var='date'>10</var>, <var data-var='time'>10:58</var> CET Completed - The scheduled maintenance has been completed. Nov <var data-var='date'>10</var>, <var data-var='time'>07:00</var> CET In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Nov <var data-var='date'> 6</var>, <var data-var='time'>08:13</var> CET Scheduled - We will be performing scheduled maintenance on the optimisation engine. This work is part of the actions outlined in the post-mortem of the 9 October incident (https://status.fasterize.com/incidents/84f0ss6vdbnc). Specifically, we are: - Upscale in-memory database cluster in order to accept more connections

Scheduled maintenance – Maintenance operation on our platform

Nov <var data-var='date'> 6</var>, <var data-var='time'>08:11</var> CET Completed - The scheduled maintenance has been completed. Nov <var data-var='date'> 6</var>, <var data-var='time'>07:00</var> CET In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Nov <var data-var='date'>10</var>, <var data-var='time'>07:00</var> CET Scheduled - We will be performing scheduled maintenance on the optimisation engine. This work is part of the actions outlined in the post-mortem of the 9 October incident (https://status.fasterize.com/incidents/84f0ss6vdbnc). Specifically, we are: - Upscale in-memory database cluster in order to accept more connections

Oct <var data-var='date'>21</var>, <var data-var='time'>08:38</var> CEST Completed - The scheduled maintenance has been completed. Oct <var data-var='date'>21</var>, <var data-var='time'>07:00</var> CEST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Oct <var data-var='date'>20</var>, <var data-var='time'>14:45</var> CEST Scheduled - We will be performing scheduled maintenance on the optimisation engine. This work is part of the short-term actions outlined in the post-mortem of the 9 October incident (https://status.fasterize.com/incidents/84f0ss6vdbnc). Specifically, we are: - Fixing the failover mechanism for websites that cannot be unplugged from Fasterize, by ensuring that all additional headers are properly sent to the origin.

Oct <var data-var='date'> 9</var>, <var data-var='time'>20:23</var> CEST Resolved - This incident has been resolved. The API and the dashboard are now able to handle correctly configuration updates and cache purges. As mentioned earlier, a postmortem will be written and available here. Oct <var data-var='date'> 9</var>, <var data-var='time'>19:04</var> CEST Identified - The issue has been identified and a workaround is being implemented. In the meantime, configuration updates and cache purges are unfortunately still unavailable. The workaround will unfortunately degrade the API performance but it should be temporary until we rollout a definitive solution. As soon as the fix is delivered, we'll monitor it to be sure that everything's ok. The postmortem will follow, as we also need to gather further elements from our provider. We deeply apologize for this incident and we're actively working to solve this issue as soon as possible. Oct <var data-var='date'> 9</var>, <var data-var='time'>17:35</var> CEST Investigating - Acceleration is now fully operational. Configuration updates are still unavailable, and we are investigating the issue. Cache purges are also currently unavailable. Oct <var data-var='date'> 9</var>, <var data-var='time'>15:20</var> CEST Update - Configuration updates are not possible from the Fasterize console. We are currently investigating. Oct <var data-var='date'> 9</var>, <var data-var='time'>12:34</var> CEST Monitoring - A fix has been implemented and we are monitoring the results. Oct <var data-var='date'> 9</var>, <var data-var='time'>12:27</var> CEST Update - The failing component is gradually recovering, and we are monitoring it until full restoration Oct <var data-var='date'> 9</var>, <var data-var='time'>11:54</var> CEST Identified - We are still investigating and trying to restore the failing component. Oct <var data-var='date'> 9</var>, <var data-var='time'>11:01</var> CEST Investigating - Our platform is experiencing an outage, where possible traffic is automatically routed to origin to mitigate the incident. We identified the issue and are working on a fix to restore availability

Platform unavailability

Oct <var data-var='date'> 9</var>, <var data-var='time'>08:37</var> CEST Completed - The scheduled maintenance has been completed. Oct <var data-var='date'> 9</var>, <var data-var='time'>07:00</var> CEST Update - We will be undergoing scheduled maintenance during this time. Oct <var data-var='date'> 7</var>, <var data-var='time'>07:00</var> CEST Scheduled - We are performing a maintenance operation on part of our platform to improve reliability and performance. Enhanced monitoring will be in place during and after the maintenance

Sep <var data-var='date'>25</var>, <var data-var='time'>10:00</var> CEST Resolved - 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.

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

Sep <var data-var='date'> 9</var>, <var data-var='time'>15:51</var> CEST Resolved - This incident has been resolved. Sep <var data-var='date'> 9</var>, <var data-var='time'>15:11</var> CEST Monitoring - 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.

Platform has been unavailable

Sep <var data-var='date'> 9</var>, <var data-var='time'>12:13</var> CEST Resolved - Between 11:35 a.m. and 11:55 a.m. (Paris time), the platform experienced performance slowdowns following a scheduled update impacting the load balancers.

Slowdowns on the platform

Sep <var data-var='date'> 9</var>, <var data-var='time'>02:30</var> CEST Resolved - On September 9, Fasterize performed a planned network maintenance to replace an obsolete private network. As part of this operation, a new private IP address was introduced for our load balancers while keeping the existing ones in place. Later that afternoon, a DDoS attack led to the saturation and restart of one of the load balancers. Following this restart, the load balancer started using the new private IP address to communicate with the backend servers. Since this IP had not yet been registered as a trusted proxy, some requests were processed incorrectly.

Client IP retrieval has been broken between 14:50 – 18:30 (Paris time)

Jul <var data-var='date'>30</var>, <var data-var='time'>11:25</var> CEST Resolved - This incident has been resolved. Jul <var data-var='date'>30</var>, <var data-var='time'>11:20</var> CEST Investigating - Slowdowns on the platform since 10 a.m.

Jun <var data-var='date'>18</var>, <var data-var='time'>10:55</var> CEST Resolved - This incident is now resolved. Post-mortem will follow but to sum up: the root cause is a change in a DNS record. During that change, the record pointing to our DC took a temporary wrong value that was captured by some edge servers and stored for one hour. This affected only a subset of edge servers and only a subset of the health checkers responsible for triggering the failover mechanism. This explains why the failover mechanism wasn't fully triggered. Jun <var data-var='date'>18</var>, <var data-var='time'>09:49</var> CEST Update - The failover mechanism didn't trigger. We trigger it manually. Jun <var data-var='date'>18</var>, <var data-var='time'>09:41</var> CEST Investigating - We currently have some issues on one of our european DC. Being fixed. Trafic is interrupted for a large portion of the customers. Really sorry for the inconvenience.

Unavailability of the origin on several CDN Edge Servers leading to 502/504 errors for end users

Jun <var data-var='date'>11</var>, <var data-var='time'>18:50</var> CEST Resolved - Incident is now closed. Sorry for the inconvenience. A post-mortem will follow. Jun <var data-var='date'>11</var>, <var data-var='time'>17:02</var> CEST Monitoring - We're still monitoring. Jun <var data-var='date'>11</var>, <var data-var='time'>16:02</var> CEST Identified - Issue has been identified. Some load balancers in one of our datacenter have crashed and have been restarted. Traffic was interrupted at 3:31PM and is back to normal since 3:42PM CET. Jun <var data-var='date'>11</var>, <var data-var='time'>15:41</var> CEST Investigating - We currently have some issues on our european infrastructure. We're investigating. Speeding-up is disable. Traffic should be redirected to origins.

Acceleration is disabled.

May <var data-var='date'>28</var>, <var data-var='time'>09:00</var> CEST 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.

Temporary Service Disruption : Error 502

May <var data-var='date'>13</var>, <var data-var='time'>22:53</var> CEST Resolved - We experienced a service disruption caused by a Distributed Denial of Service (DDoS) attack. The issue has now been resolved. A full post-mortem will follow. Thank you for your patience and understanding. May <var data-var='date'>13</var>, <var data-var='time'>21:54</var> CEST Investigating - One of our datacenter has been unavailable between 21h21 and 21h47. We are investigating the incident.

Mar <var data-var='date'> 3</var>, <var data-var='time'>10:00</var> CET Completed - The scheduled maintenance has been completed. Feb <var data-var='date'> 1</var>, <var data-var='time'>10:00</var> CET In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jan <var data-var='date'>24</var>, <var data-var='time'>13:53</var> CET Scheduled - At Fasterize, the quest to achieve the best possible performance for our customers is written into our DNA. This instinct prompted us to start exploring new infrastructure options in 2024. This mission is now complete, and over the next few months we will progressively migrate our services to the new infrastructure. From your perspective, this transition will be fully transparent and does not require any specific action, other than taking into account an update we've made to the list of IP addresses from which Fasterize routes traffic to your hosting provider’s servers: https://support.fasterize.com/en/support/solutions/articles/43000456888-list-of-fasterize-ip-addresses To prevent any disruption to your site, please ensure that the necessary steps are taken on your side to ensure that the new Fasterize IPs are authorized as soon as possible. Do not hesitate to contact our Support team by creating a ticket from the Fasterize Console if you have any questions. We would also be grateful if you could confirm once this step has been completed on your side. Regarding the security and GDPR considerations of this change, please know that our new infrastructure not only meets all requirements under current legislation (as is the case with our existing infrastructure), it goes even further by being based on a sovereign, French cloud. You'll find the details in our updated Data Protection Agreement here: www.fasterize.com/en/dpa/

Update of Fasterize IP addresses list

Feb <var data-var='date'>25</var>, <var data-var='time'>18:06</var> CET Resolved - Incident is now closed. Sorry for the inconvenience. A post-mortem will follow. Feb <var data-var='date'>25</var>, <var data-var='time'>17:37</var> CET Monitoring - Fix has been deployed, everything is back to normal (the platform is properly monitored again). We're still monitoring. Feb <var data-var='date'>25</var>, <var data-var='time'>16:37</var> CET Update - Root cause has been identified. A post-mortem is being written. We're gonna set up more robust global platform health checks. Feb <var data-var='date'>25</var>, <var data-var='time'>11:10</var> CET Identified - Acceleration was disabled between 10:45 AM GMT+1 and 11 AM GMT+1 due to a misconfiguration of the global platform health checks. These health checks are currently being reviewed (but the platform is actually healthy).

Acceleration was disabled between 10:45 AM GMT+1 and 11 AM GMT+1

Jan <var data-var='date'> 1</var>, <var data-var='time'>22:00</var> CET Resolved - 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.

Minor Incident: Purging Image Metadata and CSS/JS Bundles

Dec <var data-var='date'>11</var>, <var data-var='time'>09:30</var> CET Resolved - 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.

Is Fasterize down?

Fasterize status is UP

Lastest published events

Performance degradation

Website status may incorrectly show as “Ping blocked”

Issue on the flush on the dashboard and API

Fasterize Services, Components and Regions

Recent Fasterize events

Performance degradation

Website status may incorrectly show as “Ping blocked”

Issue on the flush on the dashboard and API

Performance degradation

INP Data Inaccuracy on Safari (iPhone)

Scheduled maintenance on website configuration management and data storage