> From what it looks like ( domain did not resolve at all, now it seems to
> do so ) they’re on it.
>
> Code:
> --------------------
> ping susestudio.com
> PING susestudio.com (130.57.70.200) 56(84) bytes of data.
>
> --------------------
Yes it was reported to SUSE yesterday so they are aware of it and should
be working on it.
HTH.
Simon
SUSE Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.
Yes, and while I can get into SUSE Studio, I have not been able to build a
system all day, and neither has a customer of mine. Would that be related
to the DDoS silliness? i do not think so, but who knows.
–
Good luck.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below…
> Yes, and while I can get into SUSE Studio, I have not been able to build
> a system all day, and neither has a customer of mine. Would that be
> related to the DDoS silliness? i do not think so, but who knows.
Yeah, I noticed the build end of things does seem to not be working today
as well. It could be caused by the DDoS problem, since that was a DNS
attack - if the build servers can’t be resolved, that could well explain
the issue. But that’s just a guess.
The Dyn DDoS attack definitely took the SuseStudio website offline, but now it appears to be something else. The site has been accessible, but appliances can’t be edited, with “error retrieving status information”. This has been going on for a week. I’m kind of worried.