[Owasp-leaders] OWASP Website down!
psiinon at gmail.com
Sun Jul 8 09:25:47 UTC 2012
I know this only happens infrequently, but it is a bit embarrassing.
Do we know what went wrong this time, and was is something that could have
been easily fixed by volunteers with the right access?
Would it help if we had a set of people in different timezones who had
enough access to fix common problems and who got alerted when the site
Until we pay someone to do this of course.
I'd be happy to be involved.
Free online services like www.monitor.us and www.pingdom.com work well.
We could always set up an owasp list that gets alerts from these sort of
services that anyone can subscript to...
On Sat, Jul 7, 2012 at 3:18 PM, Matt Tesauro <matt.tesauro at owasp.org> wrote:
> Its back up now - at least from Texas / USA.
> -- Matt Tesauro
> OWASP Board Member
> OWASP WTE Project Lead
> http://AppSecLive.org - Community and Download site
> On Sat, Jul 7, 2012 at 8:12 AM, Dominique Righetto <
> dominique.righetto at owasp.org> wrote:
>> Hi all,
>> Same behavior from Luxemburg.....
>> "This web page is not available"
>> Best regards,
>> On Sat, Jul 7, 2012 at 2:04 PM, Tobias <tobias.gondrom at owasp.org> wrote:
>>> Hi all,
>>> I can also confirm the OWASP web pages are not loading (from the UK and
>>> Ping reaches the server, but page loads time-out.
>>> Whoever is in charge of the server please try to fix this ASAP!
>>> Best regards, Tobias
>>> On 07/07/12 12:59, Abbas Naderi Afooshteh wrote:
>>> Hello leaders,
>>> OWASP website is not loading in Iran.
>>> dig returns IP 220.127.116.11 and the IP won't load as well.
>>> How am I supposed to spread the word in my community if the portal is
>>> not functional there?
>>> I usually use a private anonymity and privacy setup on a personal server
>>> to access Internet, that's why I don't have the problem.
>>> Could anyone trace it and find the problem?
>>> Then someone propose a solution?
>>> *Notice:** *This message is *digitally signed*, this means that its *
>>> source* and *integrity* are verifiable.
>>> Certain mail clients would automatically verify this email and present a
>>> "*signed and sealed*" sign, but others might just provide a
>>> downloadable file (smime.p7s), which includes the X.509 certificate and the
>>> signature body.
>>> In this case, you can either ignore it or manually verify it. Read more
>>> on this at Certified E-Mail with Comodo and Thunderbird<http://abiusx.com/certified-e-mail-with-comodo-and-thunderbird/> at
OWASP ZAP: Toolsmith Tool of the Year
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OWASP-Leaders