Redirect service issue US

Resolved
Updated

Post Mortem: The issue was caused by a previously unknown edge case in configuration which was not picked up by our monitoring. We are still investigating what exactly happened. Our customers informed us earlier, but unfortunately we missed those messages for a long time, due to a change in support shift responsibility.

Please keep in mind, that you should not depend on the redirect service. The redirect service is an extra convenience and will forward naked domains like https://fortrabbit.com to the www doamin like https://www.fortrabbit.com. The www subdomain should be the main domain and the redirect service should best not be used at all for any links.

Avatar for
Resolved

We've now resolved the incident. Thanks for your patience and sorry for the inconvenience.

Avatar for
Investigating

The redirect service seems to have issues since 12h already. Calling naked domains will return 'Unable to connect'. We are on it. Reminder: The redirect service points https://fortrabbit.com to https://www.fortrabbit.com. The www domain should always be the main domain, nearly no traffic should hit the naked domain.

Avatar for
Began at:

Affected components
  • US
    • Pro Apps
      • Web delivery
      • Object Storage
      • Memcache
      • Worker
    • Universal Apps
    • MySQL
    • Deployment
    • Backups