This post is a few minutes from the start of this event, in between 2023-08-17 05:00 and 2023-08-18 22:00 UTC, see https://cloudflarestatus.com . If you use Cloudflare and watch the scheduled maintenance activity start or kicked in, you'd notice that resources got a blip, just for a second. They went out and a refreshed would make those affected resources return and its noticeable for websites. In our end, everything seemed to be working fine, with a little, lag, if your eyes are set on to your traffic right now. Here, we can see it's okay overall. Right?
Having a different internet browser makes handy for people whose job is to make sure any web service or application, and their behavior, would not fail before and after making any changes, or upgrade. In our definition, it is that it would not fail regardless of methods, not the geeky ones and without harm of course, applied to access, in a regular way, a resource designed and made available to the public. We think that premise, which is to "make sure it will work, somehow a little better", characteristic of our work @𝖎𝖈𝖑𝖆𝖘𝖘𝖊𝖉, is true to any technology designed for use mainstream but which this post is toned or using such example, specifically. Do you know what causes a browser to process a web service or application like this in the image? We would see it is due to an HSTS, primarily, not being processed or some bug prevented to load by, in here we have, Microsoft Edge Dev browser where a notice is produced. Then it could be that, with other browsers, this is not at