pleroma.sokosoko.info — SOKO.dayo
soko's pleroma instance
Details
up since 2024-06-09 20:33 (23.7 days ago)
- Uptime: 98.04%
- Users: 1 (1 active this month, 1 active last six months)
- Posts: 56
- Posts per user: 56.00
- Peers: 360
- Version: pleroma 2.5.0
- Source code: https://git.pleroma.social/pleroma/pleroma
- Registrations: Invite
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-06-20 07:36 — 2024-07-03 13:12
users: 1 (0.00/day)
min/max/avg/stddev: 1 / 1 / 1.00 / 0.00
⋯ ⋯posts: 56 (0.08/day)
min/max/avg/stddev: 35 / 56 / 53.11 / 6.52
peers: 360 (0.31/day)
min/max/avg/stddev: 272 / 360 / 348.00 / 26.90
response_time: 1.943 (0.00/day)
min/max/avg/stddev: 1 / 8 / 3.62 / 2.30
Crawling Info
First contact: 2023-01-25 (17.2 months ago)
Last successful contact: 2024-07-03 (15.9 minutes ago)
Contact: 23158 successful, 1109 failed.
Average fetch time: 3.62s
Next attempt scheduled for 147.7 seconds from now.
Found through letus.inspiredlife.fun (up)
IP address: 160.16.142.94
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-07-03 12:53:33 in 0.00s]: IP: 160.16.142.94 / Error: http / HTTP status: -1
- [2024-07-03 09:52:33 in 0.00s]: IP: 160.16.142.94 / Error: http / HTTP status: -1
- [2024-07-03 06:49:32 in 0.00s]: IP: 160.16.142.94 / Error: http / HTTP status: -1
- [2024-07-03 05:30:17 in 0.00s]: IP: 160.16.142.94 / Error: http / HTTP status: -1
- [2024-07-02 15:12:14 in 0.00s]: IP: 160.16.142.94 / Error: http / HTTP status: -1
- [2024-07-02 14:31:58 in 0.00s]: IP: 160.16.142.94 / Error: http / HTTP status: -1
- [2024-07-02 10:48:23 in 0.00s]: IP: 160.16.142.94 / Error: http / HTTP status: -1
- [2024-07-02 10:29:39 in 0.00s]: IP: 160.16.142.94 / Error: http / HTTP status: -1
- [2024-07-02 10:10:54 in 0.00s]: IP: 160.16.142.94 / Error: http / HTTP status: -1
- [2024-07-02 07:56:03 in 0.00s]: IP: 160.16.142.94 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-07-03 13:12:40 in 0.12s]: IP: 160.16.142.94 / OK / HTTP status: 200
- [2024-07-03 12:33:15 in 0.12s]: IP: 160.16.142.94 / OK / HTTP status: 200
- [2024-07-03 12:12:05 in 0.40s]: IP: 160.16.142.94 / OK / HTTP status: 200
- [2024-07-03 11:51:22 in 0.12s]: IP: 160.16.142.94 / OK / HTTP status: 200
- [2024-07-03 11:31:07 in 0.11s]: IP: 160.16.142.94 / OK / HTTP status: 200
- [2024-07-03 11:10:16 in 0.80s]: IP: 160.16.142.94 / OK / HTTP status: 200
- [2024-07-03 10:50:53 in 0.45s]: IP: 160.16.142.94 / OK / HTTP status: 200
- [2024-07-03 10:32:01 in 0.11s]: IP: 160.16.142.94 / OK / HTTP status: 200
- [2024-07-03 10:12:34 in 0.13s]: IP: 160.16.142.94 / OK / HTTP status: 200
- [2024-07-03 09:31:29 in 0.75s]: IP: 160.16.142.94 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-07-03 11:51:22 in 0.12s]: IP: 160.16.142.94 / OK / HTTP status: 200
- [2024-07-03 01:40:15 in 0.52s]: IP: 160.16.142.94 / OK / HTTP status: 200
- [2024-07-02 16:52:41 in 0.13s]: IP: 160.16.142.94 / OK / HTTP status: 200
- [2024-07-02 07:36:53 in 0.10s]: IP: 160.16.142.94 / OK / HTTP status: 200
- [2024-07-01 21:50:47 in 0.11s]: IP: 160.16.142.94 / OK / HTTP status: 200
- [2024-07-01 13:45:07 in 0.13s]: IP: 160.16.142.94 / OK / HTTP status: 200
- [2024-07-01 05:24:21 in 0.81s]: IP: 160.16.142.94 / OK / HTTP status: 200
- [2024-06-30 20:50:35 in 1.19s]: IP: 160.16.142.94 / OK / HTTP status: 200
- /nodeinfo/2.1.json ₍⇗₎
- [2024-07-03 13:12:40 in 0.73s]: IP: 160.16.142.94 / OK / HTTP status: 200
- [2024-07-03 12:33:15 in 0.49s]: IP: 160.16.142.94 / OK / HTTP status: 200
- [2024-07-03 12:12:05 in 1.71s]: IP: 160.16.142.94 / OK / HTTP status: 200
- [2024-07-03 11:51:22 in 0.74s]: IP: 160.16.142.94 / OK / HTTP status: 200
- [2024-07-03 11:31:07 in 0.46s]: IP: 160.16.142.94 / OK / HTTP status: 200
- [2024-07-03 11:10:16 in 3.59s]: IP: 160.16.142.94 / OK / HTTP status: 200
- [2024-07-03 10:50:53 in 0.45s]: IP: 160.16.142.94 / OK / HTTP status: 200
- [2024-07-03 10:32:01 in 0.69s]: IP: 160.16.142.94 / OK / HTTP status: 200
- [2024-07-03 10:12:34 in 0.64s]: IP: 160.16.142.94 / OK / HTTP status: 200
- [2024-07-03 09:31:29 in 2.89s]: IP: 160.16.142.94 / OK / HTTP status: 200