Incident History

Back to status page
  1. Jan 16, 2026

    1. Issue with wildcard domain routing

      We're currently experiencing issues with our wildcard domain routing. If you don't use a custom domain for your workspace, but a eniston.com subdomain, you're currently routed to our website.

    2. Ongoing issue with wildcard domain routing

      We're still experiencing issues with wildcard domain routing for the eniston.com domain. We are closely working with our IT partner to get this issues resolved.

      If you are able to use your own domain, please consider using this instead. Custom domains are not affected by this.

  2. Jan 24, 2026

    1. eniston.com has recovered.

    2. eniston.com appears to be down.

    3. Ongoing issue with wildcard domain routing

  3. Jan 23, 2026

    1. Ongoing issue with wildcard domain routing

  4. Jan 22, 2026

    1. Ongoing issue with wildcard domain routing

  5. Jan 21, 2026

    1. Ongoing issue with wildcard domain routing

  6. Jan 20, 2026

    1. Ongoing issue with wildcard domain routing

      We've (probably) identified the root cause of the wildcard domain routing issue and are continuing to work with our IT partner to resolve this issue.

      From what it looks like, it's a known issue with certain types of web server software (eg. Apache) in combination with a large amount of domains.

    2. eniston.com has recovered.

    3. eniston.com appears to be down.

  7. Jan 19, 2026

    1. Ongoing issue with wildcard domain routing

      We're still experiencing issues with the wildcard domain routing. The issue is likely related to Cloudflare setup and we're actively in communication with their support staff.

  8. Jan 18, 2026

    1. Ongoing issue with wildcard domain routing

  9. Jan 17, 2026

    1. Ongoing issue with wildcard domain routing