Fasterize Status

Resolved Logging / Monitoring incident

We currently have some issues on our logging infrastructure. It's being actively fixed but there are impacts on log delivery. No impact on acceleration.

Resolved Optimisations temporarily disabled

Following the previously scheduled maintenance, starting at 3pm, optimizations has been disabled and will be restored in the next hour.

Resolved Inlined images may be corrupted

We are currently investigating an issue on the image inlining feature. This feature has been deactivated. We saw inlined images that were not the right images.

Resolved Fasterize.com website unavailable

Our website has been attacked, so security systems have blocked trafic. We are investigating.

Resolved TLS Certificat issue on the dashboard and the API

We are currently investigating an issue on our TLS certificat for fasterize.com. This affect the dashboard and the API.

Resolved Intermittent errors 502 emitted by KeyCDN

We are currently investigating errors 502 emitted by KeyCDN since 04:34 (Paris time). We already ask to their support more details. Customers using the new platform with Cloudfront are not affected. We are unplugging KeyCDN on impacted customers

Resolved Instability on the engine : optimisations may be canceled

We are investigating an issue on our worker pool. A part of the pool is not taking load as usual.

Resolved Logs cluster failure

Our logs cluster has some performance issues since yesterday 10:00PM UTC. It seems that some logs indices experiment sharding issue that may have corrupted the yesterday's index. We have scaled cluster to force it to re-shard and rebalance shard. This will allow us to delete unhealthy nodes once re-balance is finished.

Resolved Flush on CDN is blocked

When flushing a configuration with a CDN link, the flush of the CDN is blocked and failed the flush service call. We are trying to unblock CDN flush as soon as possible.

Resolved Short unavailability of some of our front servers

Some of our front servers were unavailable for a short period (1 minute) which might have caused some 502 errors.