Affected Components:

Jul 18, 20:32:37 GMT+0
Postmortem - On 18/07/2026 at 21:36, I was notified of a performance issue affecting my website. The report clearly showed that the first byte took far too long to respond (over 10,000 ms). The next cron check was also impacted by the degradation, with the first byte again taking too long to respond. It was only after the third cron check that the incident was resolved. The affected regions were Europe and Canada, suggesting it was likely a networking issue with the CDN provider..

Jul 18, 19:56:05 GMT+0
Resolved - The degradation affecting my website has been mitigated. A root cause analysis is currently underway, and I will share further details as soon as they are available..

Jul 18, 19:36:11 GMT+0
Investigating - I am investigating a reported degradation affecting my website's response time. The next update will be provided after the next scheduled cron check..

Affected Components:

Jul 15, 06:25:23 GMT+0
Postmortem - On July 15 at 02:09:56, I received an incident about my website's response time exceeding the configured limit. After a quick review, it became clear that the main issue was in Europe, where the TLS response time averaged over 500ms. Combined with other factors, the total response time exceeded 1000ms, resulting in a degradation report. The incident was automatically closed ten minutes later, after the next cron check..

Jul 15, 00:19:54 GMT+0
Resolved - The degradation affecting my website has been mitigated. A root cause analysis is currently underway, and I will share further details as soon as they are available..

Jul 15, 00:09:56 GMT+0
Investigating - I am investigating a reported degradation affecting my website's response time. The next update will be provided after the next scheduled cron check..