Simplero incident

SSL Certificate Warning on Some Custom Domains

Minor Resolved View vendor source →

Simplero experienced a minor incident on September 3, 2026 affecting Website, lasting —. The incident has been resolved; the full update timeline is below.

Started
Sep 03, 2026, 07:57 PM UTC
Resolved
Sep 03, 2026, 07:57 PM UTC
Duration
Detected by Pingoru
Sep 03, 2026, 07:57 PM UTC

Affected components

Website

Update timeline

  1. identified Aug 24, 2026, 01:25 PM UTC

    Status: Identified We're aware that few accounts using a custom domain without "www" (e.g. yourdomain.com: http://yourdomain.com rather than www.yourdomain.com: http://www.yourdomain.com) may see a browser security warning when visiting their site. This is caused by a DNS/network configuration issue, not a security breach — no customer data has been accessed or exposed. Accounts using their default Simplero domain, or the "www" version of a custom domain, are not affected. We're actively investigating and will post an update here as soon as we have more information. Affected components Website (Partial outage)

  2. resolved Aug 24, 2026, 03:06 PM UTC

    Status: Resolved We've identified the cause of the security warning some customers have seen on their custom domain (e.g. yourdomain.com: http://yourdomain.com instead of www.yourdomain.com: http://www.yourdomain.com). If your domain's DNS settings are managed by you (through your own domain registrar or DNS provider), please check if you have an "A record" set to 18.214.48.22. If so, please update it to: 34.228.154.79 This is usually found in your domain's DNS settings, under a record type "A", pointing to @ or your root domain. If you're not sure how to do this, your domain registrar's support team (GoDaddy, Namecheap, Cloudflare, etc.) can help, or reach out to us and we'll guide you. If Simplero manages your domain's DNS for you, no action is needed — we've already updated this on your behalf. This was caused by a network configuration issue on our end, not a security breach — no customer data was accessed or exposed, and your website, SSL certificate, and account are otherwise unaffected. Affected components Website (Operational)

  3. monitoring Aug 24, 2026, 03:07 PM UTC

    Status: Monitoring We've identified the cause of the security warning some customers have seen on their custom domain (e.g. yourdomain.com: http://yourdomain.com instead of www.yourdomain.com: http://www.yourdomain.com). If your domain's DNS settings are managed by you (through your own domain registrar or DNS provider), please check if you have an "A record" set to 18.214.48.22. If so, please update it to: 34.228.154.79 This is usually found in your domain's DNS settings, under a record type "A", pointing to @ or your root domain. If you're not sure how to do this, your domain registrar's support team (GoDaddy, Namecheap, Cloudflare, etc.) can help, or reach out to us and we'll guide you. If Simplero manages your domain's DNS for you, no action is needed — we've already updated this on your behalf. This was caused by a network configuration issue on our end, not a security breach — no customer data was accessed or exposed, and your website, SSL certificate, and account are otherwise unaffected. Affected components Website (Operational)

  4. resolved Sep 03, 2026, 07:57 PM UTC

    Status: Resolved We've identified the cause of the security warning some customers have seen on their custom domain (e.g. yourdomain.com: http://yourdomain.com instead of www.yourdomain.com: http://www.yourdomain.com). If your domain's DNS settings are managed by you (through your own domain registrar or DNS provider), please check if you have an "A record" set to 18.214.48.22. If so, please update it to: 34.228.154.79 This is usually found in your domain's DNS settings, under a record type "A", pointing to @ or your root domain. If you're not sure how to do this, your domain registrar's support team (GoDaddy, Namecheap, Cloudflare, etc.) can help, or reach out to us and we'll guide you. If Simplero manages your domain's DNS for you, no action is needed — we've already updated this on your behalf. This was caused by a network configuration issue on our end, not a security breach — no customer data was accessed or exposed, and your website, SSL certificate, and account are otherwise unaffected. Affected components Website (Operational)