All Systems Operational
API   ? Operational
Dashboard   ? Operational
Acceleration   ? Operational
90 days ago
100.0 % uptime
Today
Website   ? Operational
Collect   ? Operational
Logs delivery   Operational
90 days ago
99.24 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
System Metrics Month Week Day
Platform uptime (Europe)
Fetching
Global optimization engine overhead
Fetching
Past Incidents
Feb 24, 2018

No incidents reported today.

Feb 23, 2018

No incidents reported.

Feb 22, 2018
Completed - Deployment has been cancelled.
Feb 22, 21:31 CET
Scheduled - We plan two important changes in our platform that require your attention. Those changes will be effective on February 22nd 2018:
- we will stop the support of TLS 1.0 and TLS 1.1
- we will introduce a new IP range that will be visible by your origin.

1) TLS 1.0 and TLS 1.1 deprecation

TLS 1.0 and 1.1 are both fairly dated versions of the TLS protocol. TLS 1.0 was published in 1999 as RFC 2246 while TLS 1.1 was published in 2006 as RFC 4346. Many improvements have been made since the release of these versions and upgrading to the current standard (TLS 1.2) is now considered the safest and most reliable method for delivering encrypted content over the Internet.

Furthermore, the PCI Data Security Standard (PCI DSS) requires that we disable the use of any SSL/TLS 1.0 implementations by June 30, 2018. TLS 1.1 will still be accepted by PCI although they strongly recommend using TLS 1.2. Given the vulnerabilities TLS 1.0 and 1.1 are susceptible to and the recommendations provided by PCI, we’ll be deprecating support of both of these versions and moving ahead with more recent versions of the TLS protocol.

We see that 99.4% of current secure connections are done in TLS 1.2 in our platform. Most browsers have been supporting TLS 1.2 for at least a few versions with the exception of Internet Explorer. The most recent version (IE 11) does indeed support TLS 1.2, however, in versions 8-10 TLS 1.2 must be enabled manually and it is not supported in versions prior to 7.0.

Our main CDN - KeyCDN - will also discontinue the support of TLS 1.1 and TLS 1.2 on February 28th 2018.

Furthermore, we are keeping a close eye on TLS 1.3 and are planning to roll out support once it becomes an RFC standard. This will even further improve both security and performance.

2) New IP range that should be whitelisted

We have decided to acquire new IP addresses Blocks that will help us extend the capability of our infrastructure. ​This change will be effective on February 22nd 2018.

Please, make sure that the following IP addresses are whitelisted in your firewall system(s) in order to prevent any 502 response codes from being generated unexpectedly: following blocks (https://support.fasterize.com/fr/article/ip-lists/)

The new IP range is 163.172.238.160/27

Don’t hesitate to ask for any help by sending an e-mail to support@fasterize.com.
Feb 6, 12:22 CET
Completed - Deployment has been cancelled.
Feb 22, 21:29 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
[0] [dashboard] Fix monitoring dashboards creation when a domain is plugged
[0] [engine] Add new option to prevent resource cache on CDN for unoptimized users
[1] [engine] Fix URL encoding in smartcache URL
[1] [engine] Fix proxy memory leak on smartcache redirect responses
[1] [infra] Apply Meltdown and Spectre security fix

Feature
[2] [API] update origin and failover DNS records for all domain declared in a Fasterize configuration
Feb 21, 18:22 CET
Feb 21, 2018

No incidents reported.

Feb 20, 2018

No incidents reported.

Feb 19, 2018

No incidents reported.

Feb 18, 2018

No incidents reported.

Feb 17, 2018

No incidents reported.

Feb 16, 2018

No incidents reported.

Feb 15, 2018

No incidents reported.

Feb 14, 2018

No incidents reported.

Feb 13, 2018

No incidents reported.

Feb 12, 2018

No incidents reported.

Feb 11, 2018

No incidents reported.

Feb 10, 2018

No incidents reported.