hax.social — Hax Social
Mastodon instance for le hax.
This is a public instance, operated as part of Hax LLC.
Details
up since 2023-08-27 12:16 (8.2 months ago)
- Uptime: 99.79%
- Users: 3 (1 active this month, 3 active last six months)
- Posts: 1087
- Posts per user: 362.33
- Peers: 17564
- Version: mastodon 4.3.0-alpha.3+glitch
- Registrations: Approval Required
Stats 2024-04-18 17:57 — 2024-05-02 15:19
users: 3 (0.00/day)
min/max/avg/stddev: 3 / 3 / 3.00 / 0.00
⋯ ⋯posts: 1087 (2.42/day)
min/max/avg/stddev: 1053 / 1087 / 1069.80 / 9.60
peers: 17564 (10.21/day)
min/max/avg/stddev: 17420 / 17564 / 17488.31 / 40.95
response_time: 1.408 (-2.77/day)
min/max/avg/stddev: 1 / 72 / 11.63 / 12.37
Crawling Info
First contact: 2023-02-04 (14.9 months ago)
Last successful contact: 2024-05-02 (30.8 minutes ago)
Contact: 22931 successful, 1168 failed.
Average fetch time: 11.63s
Next attempt scheduled for 6.3 minutes from now.
Found through outerheaven.club (up)
IP address: 95.217.133.237
Staff
rallias@hax.social
Admin hax.social
Pronouns: look, if I knew who I was, as a person, and what that meant, that would solve a lot of problems.
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-05-01 17:38:39 in 0.00s]: IP: 95.217.133.237 / Error: http / HTTP status: -1
- [2024-05-01 14:23:54 in 0.00s]: IP: 95.217.133.237 / Error: http / HTTP status: -1
- [2024-04-29 16:41:28 in 0.00s]: IP: 95.217.133.237 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-05-02 15:19:51 in 0.24s]: IP: 95.217.133.237 / OK / HTTP status: 200
- [2024-05-02 14:42:19 in 0.41s]: IP: 95.217.133.237 / OK / HTTP status: 200
- [2024-05-02 14:04:37 in 0.26s]: IP: 95.217.133.237 / OK / HTTP status: 200
- [2024-05-02 13:26:56 in 0.17s]: IP: 95.217.133.237 / OK / HTTP status: 200
- [2024-05-02 12:49:16 in 0.49s]: IP: 95.217.133.237 / OK / HTTP status: 200
- [2024-05-02 12:11:41 in 0.22s]: IP: 95.217.133.237 / OK / HTTP status: 200
- [2024-05-02 11:33:58 in 0.44s]: IP: 95.217.133.237 / OK / HTTP status: 200
- [2024-05-02 10:56:01 in 0.20s]: IP: 95.217.133.237 / OK / HTTP status: 200
- [2024-05-02 09:39:23 in 0.60s]: IP: 95.217.133.237 / OK / HTTP status: 200
- [2024-05-02 09:01:38 in 0.27s]: IP: 95.217.133.237 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-05-02 08:23:51 in 0.72s]: IP: 95.217.133.237 / Error: http / HTTP status: 404
- [2024-05-01 20:54:03 in 0.17s]: IP: 95.217.133.237 / Error: http / HTTP status: 404
- [2024-05-01 09:10:57 in 0.17s]: IP: 95.217.133.237 / Error: http / HTTP status: 404
- [2024-05-01 00:03:33 in 1.03s]: IP: 95.217.133.237 / Error: http / HTTP status: 404
- [2024-04-30 15:52:11 in 0.18s]: IP: 95.217.133.237 / Error: http / HTTP status: 404
- [2024-04-30 05:55:49 in 0.18s]: IP: 95.217.133.237 / Error: http / HTTP status: 404
- [2024-04-29 18:41:19 in 0.17s]: IP: 95.217.133.237 / Error: http / HTTP status: 404
- /nodeinfo/2.0 ₍⇗₎
- [2024-05-02 15:19:51 in 0.89s]: IP: 95.217.133.237 / OK / HTTP status: 200
- [2024-05-02 14:42:19 in 3.07s]: IP: 95.217.133.237 / OK / HTTP status: 200
- [2024-05-02 14:04:37 in 0.83s]: IP: 95.217.133.237 / OK / HTTP status: 200
- [2024-05-02 13:26:56 in 0.95s]: IP: 95.217.133.237 / OK / HTTP status: 200
- [2024-05-02 12:49:16 in 3.05s]: IP: 95.217.133.237 / OK / HTTP status: 200
- [2024-05-02 12:11:41 in 0.85s]: IP: 95.217.133.237 / OK / HTTP status: 200
- [2024-05-02 11:33:58 in 2.01s]: IP: 95.217.133.237 / OK / HTTP status: 200
- [2024-05-02 10:56:01 in 0.87s]: IP: 95.217.133.237 / OK / HTTP status: 200
- [2024-05-02 09:39:23 in 4.06s]: IP: 95.217.133.237 / OK / HTTP status: 200
- [2024-05-02 09:01:38 in 0.87s]: IP: 95.217.133.237 / OK / HTTP status: 200