Re: (Fwd) [support.osuosl.org #35260] busybox.net showing down for 3 days?

On Thu, 26 Mar 2026 05:33:00 +1000
"Michael D. Setzer II via busybox" <[email protected]> wrote:

> Just got this message, and replied that some things are connecting 
> now in better way, but http and https showing closed?
> Starting Nmap 7.92 ( https://nmap.org ) at 2026-03-26 05:14 ChST
> Nmap scan report for busybox.net (140.211.167.122)
> Host is up, received echo-reply ttl 252 (0.097s latency).
> rDNS record for 140.211.167.122: busybox.osuosl.org
> Not shown: 994 filtered tcp ports (no-response)
> PORT     STATE  SERVICE REASON
> 22/tcp   open   ssh     syn-ack ttl 252
> 80/tcp   closed http    reset ttl 252
> 443/tcp  closed https   reset ttl 252
> 873/tcp  open   rsync   syn-ack ttl 252
> 3690/tcp closed svn     reset ttl 252
> 9418/tcp open   git     syn-ack ttl 252
> 
> ------- Forwarded message follows -------
> Subject:	[support.osuosl.org #35260] busybox.net showing down for 3 days?
> From:	"Lance Albertson via RT" <[email protected]>
> Send reply to:	[email protected]
> To:	[email protected]
> Date sent:	Wed, 25 Mar 2026 12:23:54 -0700
> 
> 
> On Fri Mar 20 15:42:21 2026, [email protected] wrote:
> > https://www.isitdownrightnow.com/busybox.net.html
> > Website Name:
> > busybox.netURL Checked:
> > no responseResponse Time:
> > ~3 days 19 hoursDown For:
> > DOWN
> > Busybox.net is DOWN for everyone.  It is not just you. The server is not
> > responding...
> > 
> > Had done a git clone on the 16th, that worked fine, but just tried, and it
> > fails.
> > 
> > Cloning into 'busybox'...
> > fatal: unable to connect to busybox.net:
> > busybox.net[0: 140.211.167.122]: errno=Connection timed out
> > 
> > Was a message on list showing site was done.
> > 
> > Strangely, if I go to webpage, it comes up even if I clear cache, it takes a
> > long time, so might be a copy in ram?
> 
> Looks like the IP connection tracking table was getting full:
> 
> Mar 25 19:09:06 busybox kernel: [702609.137658] nf_conntrack: 
> nf_conntrack: table full, dropping packet
> 
> I've increased the max for now and will keep an eye on it to make 
> sure it
> doesn't keep happening.
> 
> Thanks-
> 
Hi,
Seems to me there must be more as it is even worse than before:

website is down

The connection has timed out

The server at busybox.net is taking too long to respond.

and git:

 git pull
fatal: unable to access 'https://git.busybox.net/busybox/': Failed to connect to git.busybox.net port 443 after 19481 ms: Could not connect to server

it's a wonder that the mailing list still works.

Ciao,
Tito