All Systems Operational
API   ? Operational
Dashboard   ? Operational
Acceleration   ? Operational
90 days ago
99.91 % uptime
Today
Website   ? Operational
Collect   ? Operational
Logs delivery   Operational
90 days ago
99.85 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Platform uptime (Europe)
Fetching
Global optimization engine overhead
Fetching
Past Incidents
Nov 18, 2018

No incidents reported today.

Nov 17, 2018

No incidents reported.

Nov 16, 2018
Completed - The scheduled maintenance has been completed.
Nov 16, 00:41 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Nov 15, 22:00 CET
Scheduled - For a best appreciation of deployment impacts, we use a scale from 0 to 3 :
0 : not critical (no impact is expected after the deployment of the feature or fix, it's often related to the Fasterize website, API or auxiliary tools)
1 : minor (it may have a minor impact on optimized websites operations during the deployment, it's often related to the optimization engine or the cache layer)
2 : major (it may have a major impact on optimized websites. It is advisable to monitor the websites during this deployment).

Fix
[1] [infra] Adjust broker retry mechanism to better handle high traffic spikes
[1] [engine] Fix deferjs execution order with async and defer scripts
[1] [engine] Improve HTML page charset detection
[1] [engine] Prevent force cache (from Fasterize rules) of Ajax responses

Feature
[1] [engine] Add an option to override the request protocol
[1] [engine] Automatically exclude too large uncachable HTML pages
[2] [engine] Enable new proxies and workers using existing outbound IP addresses
[2] [engine] Enable direct put into caches from workers
Nov 13, 18:05 CET
Nov 14, 2018

No incidents reported.

Nov 13, 2018

No incidents reported.

Nov 12, 2018
Completed - The scheduled maintenance has been completed.
Nov 12, 23:45 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Nov 12, 22:00 CET
Scheduled - Shadow launch of the ability to forward request to the origin through existing machine

To be more flexible regarding the addition of node, we will forward request to the origin through existing machine.
This will be activated on new machines only.

Shadow launch of the ability to directly send request to the cache without using the front layer

This will reduce the bandwidth consumed on the front layer. This will not be activated for the moment.

Prepare addition of new machine without updating the IP lists

To be more flexible regarding the addition of node, we will forward request to the origin through existing machine.
This will be activated on new machines only.

Monitor keycdn error ratio

As indicated in our last post-mortem, we improve the monitoring of errors introduced by our platform.

The engine migrate to node 8.

We migrated our engine to the last LTS version. This migration was a long due on our side. Most of the work has been done during this summer and this version has already been validated on a portion of our platform.

Don't add a Cache-Control header based on the last-modified header

When the Cache-Control header is not present on the response but a Last-Modified header is present, the spec allows to compute a TTL (generally browsers implement 10% of the duration since the last update. This is now removed since we encounter website setting a Last-Modified header on page that must not be cached.

Reduce congestion in the Front layer

We were using the front layer to send internal requests to the cache layer. This is now removed and the cache layer is addressed directly. This reduces potential bandwidth congestion on the front layer.

Brotli is supported at the origin

We correctly decode origin response using the Brotli compression algorithm.

Fix discovery mode

In discovery mode, when optimizations were enabled by the plugin, it was possible that some cache rules were not applied.

Support Protocol Rewriting

It's now possible to rewrite the page with HTTPS links even if the received request is in HTTP.
This is particularly important when a CDN in front of Fasterize modify the protocol.
Nov 9, 11:10 CET
Nov 11, 2018

No incidents reported.

Nov 10, 2018

No incidents reported.

Nov 9, 2018

No incidents reported.

Nov 8, 2018

No incidents reported.

Nov 7, 2018
Completed - The scheduled maintenance has been completed.
Nov 7, 01:35 CET
Scheduled - The engine migrate to node 8.

We migrated our engine to the last LTS version. This migration was a long due on our side. Most of the work has been done during this summer and this version has already been validated on a portion of our platform.

Don't add a Cache-Control header based on the last-modified header

When the Cache-Control header is not present on the response but a Last-Modified header is present, the spec allows to compute a TTL (generally browsers implement 10% of the duration since the last update. This is now removed since we encounter website setting a Last-Modified header on page that must not be cached.

Reduce congestion in the Front layer

We were using the front layer to send internal requests to the cache layer. This is now removed and the cache layer is addressed directly. This reduces potential bandwidth congestion on the front layer.

Brotli is supported at the origin

We correctly decode origin response using the Brotli compression algorithm.

Fix discovery mode

In discovery mode, when optimizations were enabled by the plugin, it was possible that some cache rules were not applied.

Support Protocol Rewriting

It's now possible to rewrite the page with HTTPS links even if the received request is in HTTP.
This is particularly important when a CDN in front of Fasterize modify the protocol.
Nov 5, 17:26 CET
Completed - The scheduled maintenance has been completed.
Nov 7, 00:30 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Nov 6, 22:30 CET
Update - We will be undergoing scheduled maintenance during this time.
Nov 5, 15:27 CET
Scheduled - No code will be deployed, only new machines will be added. No impact expected.
Nov 5, 15:26 CET
Nov 5, 2018

No incidents reported.

Nov 4, 2018

No incidents reported.