Is Simplero down?
Last checked 3m agoNo incidents right now.
Simplero is operational right now. Last checked 3m ago; the most recent incident resolved 12d ago.
Real-time Simplero status, recent outages, and incident history — pulled directly from Simplero's official status page at https://status.simplero.com every 5 minutes. Pingoru tracks 7 Simplero services and has captured 2 incidents in the last 90 days (99.68% uptime). Get email, Slack, Discord, or webhook alerts the moment Simplero reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Website
Timeline · 4 updates
- 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)
- 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)
- 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)
- 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)
Latest: 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.yourd…
-
- Started Sep 03, 2026, 07:57 PM UTC · Resolved Sep 03, 2026, 07:57 PM UTC · —