Is Qwilr down?
Last checked 9m agoNo incidents right now.
Qwilr is operational right now. Last checked 9m ago; the most recent incident resolved 9d ago.
Real-time Qwilr status, recent outages, and incident history — pulled directly from Qwilr's official status page at http://status.qwilr.com every 5 minutes. Pingoru tracks 5 Qwilr services and has captured 7 incidents in the last 90 days (98.89% uptime). Get email, Slack, Discord, or webhook alerts the moment Qwilr reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Published Qwilr Pages
Timeline · 2 updates
- investigating · Jun 05, 2026, 05:12 AM UTC
We are experiencing an issue with published Qwilr Pages on a custom domain. Our team are currently investigating.
- resolved · Jun 05, 2026, 05:32 AM UTC
Published Qwilr Pages have been restored
Latest: Published Qwilr Pages have been restored
-
- Qwilr App
Timeline · 3 updates
- identified · May 20, 2026, 09:11 PM UTC
We have identified an issue that is causing new Single Sign On logins to be denied. This only affects new logins, existing logins will not be affected. A fix is being deployed.
- identified · May 20, 2026, 09:50 PM UTC
A fix has been deployed and we are monitoring.
- resolved · May 20, 2026, 10:04 PM UTC
The issue has been resolved. SSO logins are working as expected.
Latest: The issue has been resolved. SSO logins are working as expected.
-
-
Timeline · 1 update
- resolved · May 20, 2026, 12:51 AM UTC
Certificates used for HTTPS on Custom Domains may not have been correctly registered for customers using this feature. Visitors to those pages may have received a security warning in their browser.
Latest: Certificates used for HTTPS on Custom Domains may not have been correctly registered for customers using this feature. Visitors to those pages may have received a security warning …
-
-
Timeline · 1 update
- resolved · Apr 01, 2026, 10:43 PM UTC
During scheduled maintenance, some users may have received “comment resolved” email notifications. These were sent in error — no comments were resolved, and no data was modified. This was not a security incident. The root cause has been identified and we are updating the system to prevent this occurring again. We apologise for any inconvenience.
Latest: During scheduled maintenance, some users may have received “comment resolved” email notifications. These were sent in error — no comments were resolved, and no data was modified. T…
-
-
Timeline · 1 update
- resolved · Apr 01, 2026, 10:00 PM UTC
Apr 2, 09:00 AEDT Resolved - During scheduled maintenance, some users may have received “comment resolved” email notifications. These were sent in error — no comments were resolved, and no data was modified. This was not a security incident. The root cause has been identified and we are updating the system to prevent this occurring again. We apologise for any inconvenience.
Latest: Apr 2, 09:00 AEDT Resolved - During scheduled maintenance, some users may have received “comment resolved” email notifications. These were sent in error — no comments were resolved…
-
See the full Qwilr outage history
2 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse Qwilr outage history →Or sign up free to get alerts when Qwilr breaks · 10 free monitors · No credit card
- Started Jun 05, 2026, 05:12 AM UTC · Resolved Jun 05, 2026, 05:32 AM UTC · 19m
- SSO Login Errors ResolvedStarted May 20, 2026, 09:11 PM UTC · Resolved May 20, 2026, 10:04 PM UTC · 52m
- HTTPS Certificates degraded ResolvedStarted May 20, 2026, 12:51 AM UTC · Resolved May 19, 2026, 12:00 AM UTC · —
- Unexpected Email Notifications ResolvedStarted Apr 01, 2026, 10:43 PM UTC · Resolved Apr 01, 2026, 10:00 PM UTC · —
- Unexpected Email Notifications ResolvedStarted Apr 01, 2026, 10:00 PM UTC · Resolved Apr 01, 2026, 10:00 PM UTC · —
- Analytics Not Being Processed ResolvedStarted Mar 16, 2026, 08:27 PM UTC · Resolved Mar 16, 2026, 08:27 PM UTC · —
- Analytics Not Being Processed ResolvedStarted Mar 16, 2026, 07:43 PM UTC · Resolved Mar 16, 2026, 08:27 PM UTC · 43m