Qwilr Outage History
10 incidents recorded over the last 365 days, 10 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Qwilr Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Jul 22, 2026 | Degraded Custom PagesA fix has been implemented and custom domains are working for all customers. | 53 min | Resolved |
| Jun 5, 2026 | Custom Domains - Published Qwilr PagesPublished Qwilr Pages have been restored | 19 min | Resolved |
| May 20, 2026 | SSO Login ErrorsThe issue has been resolved. SSO logins are working as expected. | 52 min | Resolved |
| May 20, 2026 | HTTPS Certificates degradedCertificates 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. | -1491 min | Resolved |
| Apr 1, 2026 | Unexpected Email NotificationsDuring 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… | -43 min | Resolved |
| Mar 16, 2026 | Analytics Not Being ProcessedThis incident has been resolved. | 43 min | Resolved |
| Mar 3, 2026 | Custom Domains - UnresponsiveA fix has been deployed and resolved the issue for custom-domains. | 16 min | Resolved |
| Feb 19, 2026 | Public Pages - Degraded AccessSome pages were degraded after an upstream authentication provider for Qwilr Public Pages experienced an outage. During this time access to some custom domain pages was not available. | -286 min | Resolved |
| Dec 5, 2025 | Full outage of pages.qwilr.comThis incident has been resolved. | 10 min | Resolved |
| Nov 18, 2025 | Degraded serviceThis incident has been resolved. | 2h 32m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Qwilr incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Qwilr Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Qwilr acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Qwilr outage in this window ran 2h 32m, against a mean recovery of 49 min. If you depend on Qwilr in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.