I’m coming from https://bugs.launchpad.net/ubuntu.
The “Report a bug” CTA target page seems to be unreachable, and I’m checking whether the issue is temporary or more serious.
There was no need to report this as Canonical’s IS team is fully aware. A general rule of thumb is:
5xx errors: The server is at fault.
4xx errors: The client is at fault.
From a community standpoint, there is nothing actionable, and there is nothing anyone can do to help you with this situation other than to tell you to be patient and wait.
Hi, thanks for the error codes. I am familiar with the topic, but I am sure they will be helpful for those who may not be familiar with them. May I ask whether you are speaking on behalf of Ubuntu on this matter? Is that a formal statement or a community heads-up? Where should users report broken links and platform unavailability? Isn’t the Ubuntu Discourse community the preferred place for this? We also experienced Discourse unavailability a couple of weeks ago due to DDoS-related issues, so I’m curious to know whether this is the appropriate channel for reporting similar platform issues, or where we should go next time, both for me and for other users. I’d be interested maybe to hear what others think about this as well. Have a great evening!
Moved to the lounge for a more appropriate category.
Just a little additional information the following link: https://status.canonical.com most of the time may show a server is back up when it is still not available.
Canonical IS is doing a lot of infrastructure upgrades, so over the next several months all sites up time will most likely improve greatly, in fact there has been significant improvement already.
I’m not @eeickmeyer but I can confidently answer on their behalf.
“On behalf of Ubuntu” is (in this instance) a fun/interesting question.
In short, we are (mostly) volunteers here, but our experience is significant. We’re not always right, but we often are. There are Canonical employees who have significantly more access to systems, processes and alerts than us, but they’re typically busy dealing with alerts, systems, tickets etc.
Those employees may be reading these messages, but they don’t necessarily have the time or inclination to respond. So consider those of us with Ubuntu badges somewhat well-informed community members, as a frontline proxy for the hard-working IS team at Canonical.
Honestly, here is best, but also nowhere is usually fine too. It’s incredibly rare that you’d be the first human to spot a service problem. There are significant monitoring and alerting tools that Canonical employs to keep an eye on all this.
Kinda, maybe, not really, no, it depends. Canonical has paid employees to look after this stuff. If it was an esoteric and niche system (isn’t it all!? ) that no normal person uses, and is community maintained, then yes. But if it’s a mainstream system that everyone in the project uses on a daily basis, probably not.
) that no normal person uses, and is community maintained, then yes. But if it’s a mainstream system that everyone in the project uses on a daily basis, probably not.