tatooine.clubDetails
up since 2024-06-10 14:59 (25.5 days ago)
- Uptime: 91.38%
- Users: 28 (5 active this month, 13 active last six months)
- Posts: 5878
- Posts per user: 209.93
- Peers: 14485
- Version: mastodon 4.1.18
- Registrations: Approval Required
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-06-22 04:14 — 2024-07-06 02:47
users: 28 (0.01/day)
min/max/avg/stddev: 24 / 28 / 27.88 / 0.69
posts: 5878 (12.27/day)
min/max/avg/stddev: 2346 / 5878 / 5682.31 / 597.58
peers: 14485 (11.03/day)
min/max/avg/stddev: 11310 / 14485 / 14356.09 / 544.60
response_time: 18.501 (0.06/day)
min/max/avg/stddev: 0 / 64 / 12.52 / 16.29
Crawling Info
First contact: 2022-11-11 (19.8 months ago)
Last successful contact: 2024-07-06 (33.9 minutes ago)
Contact: 24058 successful, 1637 failed.
Average fetch time: 12.52s
Next attempt scheduled for 3.5 minutes from now.
Found through bofh.social (up)
IP address: 139.59.48.222
Staff
nemo@tatooine.club
Programmer/Geek/UX Enthusiast. He/him.
@recursecenter alum. Takshashila scholar. I run endoflife.date, @tertracker and @dykindia. BLR/Indiranagar
I do not have an Aadhaar and cannot consent to DigiYatra.
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-07-05 20:18:57 in 0.00s]: IP: 139.59.48.222 / Error: http / HTTP status: -1
- [2024-07-05 17:39:20 in 0.00s]: IP: 139.59.48.222 / Error: http / HTTP status: -1
- [2024-07-05 17:00:36 in 0.00s]: IP: 139.59.48.222 / Error: http / HTTP status: -1
- [2024-07-05 10:02:53 in 0.00s]: IP: 139.59.48.222 / Error: http / HTTP status: -1
- [2024-07-05 08:05:35 in 0.00s]: IP: 139.59.48.222 / Error: http / HTTP status: -1
- [2024-07-04 23:16:51 in 0.00s]: IP: 139.59.48.222 / Error: http / HTTP status: -1
- [2024-07-04 22:00:09 in 0.00s]: IP: 139.59.48.222 / Error: http / HTTP status: -1
- [2024-07-04 21:21:59 in 0.00s]: IP: 139.59.48.222 / Error: http / HTTP status: -1
- [2024-07-04 11:11:33 in 0.00s]: IP: 139.59.48.222 / Error: http / HTTP status: -1
- [2024-07-04 05:30:11 in 0.00s]: IP: 139.59.48.222 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-07-06 02:47:06 in 0.68s]: IP: 139.59.48.222 / OK / HTTP status: 200
- [2024-07-06 02:08:17 in 0.21s]: IP: 139.59.48.222 / OK / HTTP status: 200
- [2024-07-06 01:30:08 in 0.65s]: IP: 139.59.48.222 / OK / HTTP status: 200
- [2024-07-06 00:51:43 in 0.21s]: IP: 139.59.48.222 / OK / HTTP status: 200
- [2024-07-06 00:12:06 in 0.27s]: IP: 139.59.48.222 / OK / HTTP status: 200
- [2024-07-05 23:32:59 in 0.62s]: IP: 139.59.48.222 / OK / HTTP status: 200
- [2024-07-05 22:53:58 in 0.22s]: IP: 139.59.48.222 / OK / HTTP status: 200
- [2024-07-05 22:15:21 in 0.24s]: IP: 139.59.48.222 / OK / HTTP status: 200
- [2024-07-05 21:36:23 in 0.65s]: IP: 139.59.48.222 / OK / HTTP status: 200
- [2024-07-05 20:57:26 in 0.53s]: IP: 139.59.48.222 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-07-05 13:50:29 in 0.22s]: IP: 139.59.48.222 / OK / HTTP status: 200
- [2024-07-05 01:49:34 in 0.23s]: IP: 139.59.48.222 / OK / HTTP status: 200
- [2024-07-04 13:06:20 in 0.23s]: IP: 139.59.48.222 / OK / HTTP status: 200
- [2024-07-03 18:39:32 in 0.21s]: IP: 139.59.48.222 / OK / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2024-07-06 02:47:06 in 13.65s]: IP: 139.59.48.222 / OK / HTTP status: 200
- [2024-07-06 02:08:17 in 1.32s]: IP: 139.59.48.222 / OK / HTTP status: 200
- [2024-07-06 01:30:08 in 4.35s]: IP: 139.59.48.222 / OK / HTTP status: 200
- [2024-07-06 00:51:43 in 1.26s]: IP: 139.59.48.222 / OK / HTTP status: 200
- [2024-07-06 00:12:06 in 1.56s]: IP: 139.59.48.222 / OK / HTTP status: 200
- [2024-07-05 23:32:59 in 24.73s]: IP: 139.59.48.222 / OK / HTTP status: 200
- [2024-07-05 22:53:58 in 1.28s]: IP: 139.59.48.222 / OK / HTTP status: 200
- [2024-07-05 22:15:21 in 1.42s]: IP: 139.59.48.222 / OK / HTTP status: 200
- [2024-07-05 21:36:23 in 15.05s]: IP: 139.59.48.222 / OK / HTTP status: 200
- [2024-07-05 20:57:26 in 11.88s]: IP: 139.59.48.222 / OK / HTTP status: 200