BetterUptime fails for docs.winglang.io

[staycoolcall911]

Incident description

Perhaps it is related to the fact we now switched to winglang.io/docs, but it could also be just a temporary hiccup

Is there a workaround?

Yes, use winglang.io/docs

Incident Response Checklist

• [x] CREATE this issue (fill up the title, description and submit), then follow the next steps.
• [x] PIN the incident issue.
• [x] ACKNOWLEDGE the incident on PagerDuty.
• [x] ACKNOWLEDGE the incident on BetterStack.
• [x] WORKAROUND - if there is one, make sure it is documented in the section above.
• [x] PRIORITIZE (P0/P1/P2 - see the definitions here).
• [x] (optional) CONTACT a relevant person who has more information about the incident.
• [ ] (optional) ANNOUNCE major incidents on Slack #dev or #general channels. "NOTICE - P0 incident started. {incident-description}. Track on {link to issue}".
• [x] HANDLE by reverting or forward fixing.
• [x] UPDATE the team on your actions in the created #alert Slack thread throughout the incident.
• [x] RESOLVE the incident on PagerDuty (BetterStack resolves automatically).
• [x] UPDATE the team on the issue closure.
• [ ] (optional) ANNOUNCE closure of major incidents on Slack #dev or #general channels. "NOTICE - P0 incident ended. {incident-resolution-description}. Track on {link to issue}".
• [x] UNPIN the incident issue.
• [ ] LESSONS LEARNED should be shared via the "post-mortem" workflow on #dev Slack channel.
• [x] CLOSE the incident issue.

[staycoolcall911]

The docs.winglang.io url is back up. Closing. Was a minor hiccup for all I could judge.