Our dear beloved search.cpan.org is having a bad day. Queries are currently returning "502 Proxy Error" and were returning "No matches" for common modules about an hour ago.

http://search.cpan.org/search?query=cgi&mode=all

OK, so it's busted, and I'm sure someone will fix it eventually, but I want to help out by raising a red flag or filing a bug or some such thing.

The FAQ lists a contact e-mail that bounces. Googling around a bit found nothing very useful.

So, wise monks, for my edification now and in the future, what do you think is the best way to raise an alarm about problems with cpan.org?

And besides the obvious (not listing a bouncy e-mail address in the FAQ), how should this best be communicated to the public?

In reply to Where should one report search.cpan.org breakage? by frostman

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.