Compare the status, incidents stats and history between Fly.io and Redis
Every service has different practices when updating its status page, so compare these stats with a grain of salt. E.g., one service can be more aggressive when updating its status page than other so that they will have more incidents, but it doesn't mean it is worse than the other.
We have noticed a spike in packet loss across the FRA region at around 14:44 UTC caused by an upstream issue. This has recovered since 14:47 UTC, and we are currently monitoring the situation along...
We have noticed a temporary blip in our upstream network(s) between 16:38-16:40 UTC that affected our platform. This has been resolving and we are monitoring for any continuing effects.
We were alerted to elevated error rates for machine creates and updates. A deploy caused a validation error which is now being reverted.
We are experiencing some network issues. This may affect resources that have the following pattern in their endpoint: c228
We’re currently performing periodic maintenance for the Redis Cloud admin console, which may impact your access to it (cloud.redis.io). Your database’s connectivity is not affected.
Service maintenance applies to all of the resources with the following pattern in their endpoint : c248, c272, c319
How much time you'll save your team, by having the outages information close to them?
14-day free trial · No credit card required · Cancel anytime