tuttle.clubDetails
up since 2024-10-24 19:26 (23.0 days ago)
- Uptime: 99.79%
- Users: 4 (1 active this month, 3 active last six months)
- Posts: 6
- Posts per user: 1.50
- Peers: 5
- Version: hometown 4.0.6+hometown-1.1.1
- Registrations: Approval Required
[View Timeline] (← Broken) | [View Timeline Media]
Stats
No successful contact during the given timeframe.
Crawling Info
First contact: 2023-08-10 (15.3 months ago)
Last successful contact: 2024-11-16 (36.4 minutes ago)
Latest attempt: 2024-11-16 (3.8 minutes ago)
Contact: 31641 successful, 2701 failed.
Average fetch time: 0.48s
Next attempt scheduled for 11.2 minutes from now.
Found through octodon.social (up)
IP address: 139.162.221.50
Staff
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-11-16 19:15:25 in 0.00s]: IP: 139.162.221.50 / Error: http / HTTP status: -1
- [2024-11-16 18:58:53 in 0.00s]: IP: 139.162.221.50 / Error: http / HTTP status: -1
- [2024-11-16 18:10:27 in 0.00s]: IP: 139.162.221.50 / Error: http / HTTP status: -1
- [2024-11-16 16:03:02 in 0.00s]: IP: 139.162.221.50 / Error: http / HTTP status: -1
- [2024-11-16 14:49:33 in 0.00s]: IP: 139.162.221.50 / Error: http / HTTP status: -1
- [2024-11-16 14:17:13 in 0.00s]: IP: 139.162.221.50 / Error: http / HTTP status: -1
- [2024-11-16 13:29:05 in 0.00s]: IP: 139.162.221.50 / Error: http / HTTP status: -1
- [2024-11-16 12:56:44 in 0.00s]: IP: 139.162.221.50 / Error: http / HTTP status: -1
- [2024-11-16 12:24:02 in 0.00s]: IP: 139.162.221.50 / Error: http / HTTP status: -1
- [2024-11-16 11:47:40 in 0.00s]: IP: 139.162.221.50 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-11-16 18:42:47 in 0.20s]: IP: 139.162.221.50 / OK / HTTP status: 200
- [2024-11-16 18:26:38 in 0.15s]: IP: 139.162.221.50 / OK / HTTP status: 200
- [2024-11-16 17:53:30 in 0.21s]: IP: 139.162.221.50 / OK / HTTP status: 200
- [2024-11-16 17:36:52 in 0.19s]: IP: 139.162.221.50 / OK / HTTP status: 200
- [2024-11-16 17:18:20 in 0.39s]: IP: 139.162.221.50 / OK / HTTP status: 200
- [2024-11-16 17:01:47 in 0.20s]: IP: 139.162.221.50 / OK / HTTP status: 200
- [2024-11-16 16:42:18 in 0.18s]: IP: 139.162.221.50 / OK / HTTP status: 200
- [2024-11-16 16:19:08 in 0.40s]: IP: 139.162.221.50 / OK / HTTP status: 200
- [2024-11-16 15:43:59 in 0.21s]: IP: 139.162.221.50 / OK / HTTP status: 200
- [2024-11-16 15:21:17 in 1.05s]: IP: 139.162.221.50 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-11-16 16:19:08 in 0.32s]: IP: 139.162.221.50 / OK / HTTP status: 200
- [2024-11-16 00:16:30 in 0.15s]: IP: 139.162.221.50 / OK / HTTP status: 200
- [2024-11-15 13:34:05 in 0.14s]: IP: 139.162.221.50 / OK / HTTP status: 200
- [2024-11-15 05:24:18 in 0.32s]: IP: 139.162.221.50 / OK / HTTP status: 200
- [2024-11-14 19:25:36 in 0.30s]: IP: 139.162.221.50 / OK / HTTP status: 200
- [2024-11-14 09:08:52 in 0.29s]: IP: 139.162.221.50 / OK / HTTP status: 200
- [2024-11-13 23:14:24 in 0.14s]: IP: 139.162.221.50 / OK / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2024-11-16 18:42:47 in 0.61s]: IP: 139.162.221.50 / OK / HTTP status: 200
- [2024-11-16 18:26:38 in 0.58s]: IP: 139.162.221.50 / OK / HTTP status: 200
- [2024-11-16 17:53:30 in 0.67s]: IP: 139.162.221.50 / OK / HTTP status: 200
- [2024-11-16 17:36:52 in 0.64s]: IP: 139.162.221.50 / OK / HTTP status: 200
- [2024-11-16 17:18:20 in 1.10s]: IP: 139.162.221.50 / OK / HTTP status: 200
- [2024-11-16 17:01:47 in 0.61s]: IP: 139.162.221.50 / OK / HTTP status: 200
- [2024-11-16 16:42:18 in 0.59s]: IP: 139.162.221.50 / OK / HTTP status: 200
- [2024-11-16 16:19:08 in 2.09s]: IP: 139.162.221.50 / OK / HTTP status: 200
- [2024-11-16 15:43:59 in 0.64s]: IP: 139.162.221.50 / OK / HTTP status: 200
- [2024-11-16 15:21:16 in 1.72s]: IP: 139.162.221.50 / OK / HTTP status: 200