jong.moe — Sharkey
This is a vanilla Sharkey Instance. It doesn't seem to have a description.
Details
up since 2024-07-01 05:23 (8.1 hours ago)
- Uptime: 90.78%
- Users: 1 (1 active this month, 1 active last six months)
- Posts: 1
- Posts per user: 1.00
- Peers: 405
- Version: sharkey 2024.3.3
- Source code: https://activitypub.software/TransFem-org/Sharkey/
- Registrations: Closed
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-06-17 19:31 — 2024-07-01 13:25
users: 1 (-0.07/day)
min/max/avg/stddev: 0 / 2 / 1.25 / 0.46
posts: 1 (0.07/day)
min/max/avg/stddev: 0 / 1 / 0.61 / 0.49
peers: 405 (15.61/day)
min/max/avg/stddev: 0 / 810 / 235.46 / 126.80
response_time: 11.117 (0.60/day)
min/max/avg/stddev: 0 / 15 / 3.07 / 2.09
Crawling Info
First contact: 2024-02-28 (4.1 months ago)
Last successful contact: 2024-07-01 (22.1 minutes ago)
Latest attempt: 2024-07-01 (4.9 minutes ago)
Contact: 5999 successful, 1816 failed.
Average fetch time: 3.07s
Next attempt scheduled for 11.3 minutes from now.
Found through miruku.cafe (up)
IP address: 104.21.74.151
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-07-01 13:25:13 in 9.89s]: IP: 104.21.74.151 / Error: http / HTTP status: 403
- [2024-07-01 12:16:05 in 0.82s]: IP: 104.21.74.151 / Error: http / HTTP status: 403
- [2024-07-01 11:58:44 in 0.00s]: IP: 172.67.159.139 / Error: http / HTTP status: -1
- [2024-07-01 11:24:06 in 1.42s]: IP: 104.21.74.151 / Error: http / HTTP status: 403
- [2024-07-01 10:00:22 in 0.00s]: IP: 104.21.74.151 / Error: http / HTTP status: -1
- [2024-07-01 09:42:28 in 7.36s]: IP: 172.67.159.139 / Error: http / HTTP status: 403
- [2024-07-01 09:02:12 in 1.26s]: IP: 172.67.159.139 / Error: http / HTTP status: 403
- [2024-07-01 08:22:50 in 0.00s]: IP: 172.67.159.139 / Error: http / HTTP status: -1
- [2024-07-01 07:44:06 in 0.80s]: IP: 172.67.159.139 / Error: http / HTTP status: 403
- [2024-07-01 07:07:43 in 1.42s]: IP: 104.21.74.151 / Error: http / HTTP status: 403
- /api/v1/instance ₍⇗₎
- [2024-07-01 13:08:07 in 0.56s]: IP: 172.67.159.139 / OK / HTTP status: 200
- [2024-07-01 12:50:54 in 0.51s]: IP: 172.67.159.139 / OK / HTTP status: 200
- [2024-07-01 12:33:27 in 2.08s]: IP: 172.67.159.139 / OK / HTTP status: 200
- [2024-07-01 11:41:25 in 2.05s]: IP: 172.67.159.139 / OK / HTTP status: 200
- [2024-07-01 11:07:43 in 0.55s]: IP: 172.67.159.139 / OK / HTTP status: 200
- [2024-07-01 10:50:42 in 0.87s]: IP: 104.21.74.151 / OK / HTTP status: 200
- [2024-07-01 10:34:07 in 2.27s]: IP: 172.67.159.139 / OK / HTTP status: 200
- [2024-07-01 10:17:13 in 0.45s]: IP: 104.21.74.151 / OK / HTTP status: 200
- [2024-07-01 09:23:20 in 2.21s]: IP: 104.21.74.151 / OK / HTTP status: 200
- [2024-07-01 08:42:53 in 0.81s]: IP: 104.21.74.151 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-07-01 10:34:07 in 0.25s]: IP: 172.67.159.139 / OK / HTTP status: 200
- [2024-07-01 01:01:24 in 0.33s]: IP: 172.67.159.139 / OK / HTTP status: 200
- [2024-06-30 16:49:50 in 0.23s]: IP: 104.21.74.151 / OK / HTTP status: 200
- [2024-06-30 08:24:02 in 0.20s]: IP: 172.67.159.139 / OK / HTTP status: 200
- [2024-06-29 19:41:36 in 0.20s]: IP: 104.21.74.151 / OK / HTTP status: 200
- [2024-06-29 08:19:22 in 0.23s]: IP: 104.21.74.151 / OK / HTTP status: 200
- /nodeinfo/2.1 ₍⇗₎
- [2024-07-01 13:08:07 in 0.92s]: IP: 172.67.159.139 / OK / HTTP status: 200
- [2024-07-01 12:50:54 in 0.82s]: IP: 172.67.159.139 / OK / HTTP status: 200
- [2024-07-01 12:33:27 in 0.86s]: IP: 172.67.159.139 / OK / HTTP status: 200
- [2024-07-01 11:41:25 in 0.81s]: IP: 172.67.159.139 / OK / HTTP status: 200
- [2024-07-01 11:07:43 in 0.79s]: IP: 172.67.159.139 / OK / HTTP status: 200
- [2024-07-01 10:50:42 in 1.00s]: IP: 104.21.74.151 / OK / HTTP status: 200
- [2024-07-01 10:34:07 in 0.87s]: IP: 172.67.159.139 / OK / HTTP status: 200
- [2024-07-01 10:17:13 in 0.78s]: IP: 104.21.74.151 / OK / HTTP status: 200
- [2024-07-01 09:23:20 in 0.86s]: IP: 104.21.74.151 / OK / HTTP status: 200
- [2024-07-01 08:42:53 in 0.85s]: IP: 104.21.74.151 / OK / HTTP status: 200