Hi,
I believe you want to contact infrastruct...@apache.org about this. I think
usually such blacklisting happens for a reason, so its ideal to fix the
root cause of any problem that caused blacklisting in the first place, so
that it does not happen again.
On Wed, Apr 17, 2019, 12:41 PM Eric Auen
Since this is from one of my colleagues at Lucidworks, I’ll talk to INFRA about
this. Sorry for the noise to the list.
Cassandra
On Apr 17, 2019, 11:41 AM -0500, Eric Auensen ,
wrote:
> Hi,
> I work for Lucidworks and users in our San Francisco office have not been
> able to access the http://l
Hi,
I work for Lucidworks and users in our San Francisco office have not been
able to access the http://lucene.apache.org/ website since ~1:45 PM PDT on
4/16/19. This works from other networks. A trace route yields the following:
traceroute to lucene.apache.org (95.216.24.32), 30 hops max, 46 byte
