sharkey.kithop.ca — Kithop's Sharkey
Private Sharkey instance for Kithop
Details
up since 2024-05-01 19:43 (16.9 days ago)
- Uptime: 100.00%
- Users: 2
- Posts: 0
- Posts per user: 0.00
- Peers: 25
- Version: sharkey 2024.3.2
- Source code: https://activitypub.software/TransFem-org/Sharkey/
- Registrations: Closed
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-05-06 14:55 — 2024-05-18 17:27
users: 2 (0.00/day)
min/max/avg/stddev: 2 / 2 / 2.00 / 0.00
⋯ ⋯posts: 0 (0.00/day)
min/max/avg/stddev: 0 / 0 / 0.00 / 0.00
⋯ ⋯peers: 25 (0.73/day)
min/max/avg/stddev: 16 / 25 / 21.12 / 3.10
response_time: 5.453 (0.24/day)
min/max/avg/stddev: 0 / 14 / 6.03 / 4.45
Crawling Info
First contact: 2024-05-01 (16.9 days ago)
Last successful contact: 2024-05-18 (50.8 minutes ago)
Latest attempt: 2024-05-18 (19.4 minutes ago)
Contact: 999 successful, 52 failed.
Average fetch time: 6.03s
Next attempt scheduled for 7.6 minutes from now.
Found through cooltrans.men (up)
IP address: 206.116.24.11 (and social.kithop.ca.)
Staff
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-05-18 17:27:23 in 0.00s]: IP: 206.116.24.11 / Error: http / HTTP status: -1
- [2024-05-18 14:02:52 in 0.00s]: IP: 206.116.24.11 / Error: http / HTTP status: -1
- [2024-05-18 12:33:52 in 0.00s]: IP: 206.116.24.11 / Error: http / HTTP status: -1
- [2024-05-18 08:59:46 in 0.00s]: IP: 206.116.24.11 / Error: http / HTTP status: -1
- [2024-05-18 04:21:12 in 0.00s]: IP: 206.116.24.11 / Error: http / HTTP status: -1
- [2024-05-18 02:35:16 in 0.00s]: IP: 206.116.24.11 / Error: http / HTTP status: -1
- [2024-05-18 01:13:42 in 0.00s]: IP: 206.116.24.11 / Error: http / HTTP status: -1
- [2024-05-18 00:18:32 in 0.00s]: IP: 206.116.24.11 / Error: http / HTTP status: -1
- [2024-05-17 17:47:50 in 0.00s]: IP: 206.116.24.11 / Error: http / HTTP status: -1
- [2024-05-17 17:18:31 in 0.00s]: IP: 206.116.24.11 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-05-18 16:55:57 in 0.87s]: IP: 206.116.24.11 / OK / HTTP status: 200
- [2024-05-18 16:22:29 in 1.96s]: IP: 206.116.24.11 / OK / HTTP status: 200
- [2024-05-18 15:48:46 in 0.08s]: IP: 206.116.24.11 / OK / HTTP status: 200
- [2024-05-18 15:15:21 in 1.30s]: IP: 206.116.24.11 / OK / HTTP status: 200
- [2024-05-18 14:40:54 in 0.06s]: IP: 206.116.24.11 / OK / HTTP status: 200
- [2024-05-18 13:20:54 in 0.06s]: IP: 206.116.24.11 / OK / HTTP status: 200
- [2024-05-18 11:55:58 in 1.22s]: IP: 206.116.24.11 / OK / HTTP status: 200
- [2024-05-18 11:19:41 in 2.01s]: IP: 206.116.24.11 / OK / HTTP status: 200
- [2024-05-18 10:41:05 in 0.08s]: IP: 206.116.24.11 / OK / HTTP status: 200
- [2024-05-18 10:02:12 in 0.08s]: IP: 206.116.24.11 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-05-18 11:55:58 in 1.16s]: IP: 206.116.24.11 / OK / HTTP status: 200
- [2024-05-18 03:01:36 in 0.05s]: IP: 206.116.24.11 / OK / HTTP status: 200
- [2024-05-17 18:16:52 in 0.71s]: IP: 206.116.24.11 / OK / HTTP status: 200
- [2024-05-17 05:51:30 in 0.02s]: IP: 206.116.24.11 / OK / HTTP status: 200
- [2024-05-16 20:35:18 in 4.72s]: IP: 206.116.24.11 / OK / HTTP status: 200
- [2024-05-16 00:16:07 in 0.03s]: IP: 206.116.24.11 / OK / HTTP status: 200
- /nodeinfo/2.1 ₍⇗₎
- [2024-05-18 16:55:57 in 5.47s]: IP: 206.116.24.11 / OK / HTTP status: 200
- [2024-05-18 16:22:29 in 4.66s]: IP: 206.116.24.11 / OK / HTTP status: 200
- [2024-05-18 15:48:46 in 0.59s]: IP: 206.116.24.11 / OK / HTTP status: 200
- [2024-05-18 15:15:21 in 6.31s]: IP: 206.116.24.11 / OK / HTTP status: 200
- [2024-05-18 14:40:54 in 0.25s]: IP: 206.116.24.11 / OK / HTTP status: 200
- [2024-05-18 13:20:54 in 0.30s]: IP: 206.116.24.11 / OK / HTTP status: 200
- [2024-05-18 11:55:58 in 5.57s]: IP: 206.116.24.11 / OK / HTTP status: 200
- [2024-05-18 11:19:41 in 11.34s]: IP: 206.116.24.11 / OK / HTTP status: 200
- [2024-05-18 10:41:05 in 0.43s]: IP: 206.116.24.11 / OK / HTTP status: 200
- [2024-05-18 10:02:12 in 0.40s]: IP: 206.116.24.11 / OK / HTTP status: 200