social.maraval.net
Personal Server maintained by @pierre@social.maraval.net.
Details
up since 2024-06-28 23:07 (6.8 days ago)
- Uptime: 98.15%
- Users: 2 (1 active this month, 1 active last six months)
- Posts: 37
- Posts per user: 18.50
- Peers: 1301
- Version: firefish 20240607
- Source code: https://codeberg.org/firefish/firefish
- Registrations: Closed
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-06-21 19:19 — 2024-07-05 17:14
users: 2 (0.00/day)
min/max/avg/stddev: 2 / 2 / 2.00 / 0.00
⋯ ⋯posts: 37 (1.76/day)
min/max/avg/stddev: 12 / 38 / 27.71 / 11.47
peers: 1301 (25.82/day)
min/max/avg/stddev: 934 / 1301 / 1143.83 / 111.52
response_time: 2.131 (-5.00/day)
min/max/avg/stddev: 0 / 119 / 37.28 / 36.96
Crawling Info
First contact: 2024-06-03 (32.6 days ago)
Last successful contact: 2024-07-05 (51.4 minutes ago)
Contact: 1038 successful, 420 failed.
Average fetch time: 37.28s
Next attempt scheduled for 3.6 minutes from now.
Found through digitalcourage.social (up)
IP address: 91.171.205.28 (and 2 others: cloud.maraval.net (down), wyrm.maraval.net (up))
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-07-05 15:22:56 in 0.00s]: IP: 91.171.205.28 / Error: http / HTTP status: -1
- [2024-07-05 12:26:48 in 0.00s]: IP: 91.171.205.28 / Error: http / HTTP status: -1
- [2024-07-05 11:29:35 in 0.00s]: IP: 91.171.205.28 / Error: http / HTTP status: -1
- [2024-07-05 09:38:00 in 0.00s]: IP: 91.171.205.28 / Error: http / HTTP status: -1
- [2024-07-05 08:41:13 in 0.00s]: IP: 91.171.205.28 / Error: http / HTTP status: -1
- [2024-07-05 07:45:45 in 0.00s]: IP: 91.171.205.28 / Error: http / HTTP status: -1
- [2024-07-05 06:49:36 in 0.00s]: IP: 91.171.205.28 / Error: http / HTTP status: -1
- [2024-07-05 03:59:50 in 0.00s]: IP: 91.171.205.28 / Error: http / HTTP status: -1
- [2024-07-05 02:07:07 in 0.00s]: IP: 91.171.205.28 / Error: http / HTTP status: -1
- [2024-07-05 00:14:40 in 0.00s]: IP: 91.171.205.28 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-07-05 17:14:19 in 0.65s]: IP: 91.171.205.28 / OK / HTTP status: 200
- [2024-07-05 16:18:54 in 0.33s]: IP: 91.171.205.28 / OK / HTTP status: 200
- [2024-07-05 14:26:05 in 0.28s]: IP: 91.171.205.28 / OK / HTTP status: 200
- [2024-07-05 13:25:27 in 0.33s]: IP: 91.171.205.28 / OK / HTTP status: 200
- [2024-07-05 10:33:20 in 5.27s]: IP: 91.171.205.28 / OK / HTTP status: 200
- [2024-07-05 05:51:57 in 0.26s]: IP: 91.171.205.28 / OK / HTTP status: 200
- [2024-07-05 04:55:51 in 0.29s]: IP: 91.171.205.28 / OK / HTTP status: 200
- [2024-07-05 03:03:39 in 5.47s]: IP: 91.171.205.28 / OK / HTTP status: 200
- [2024-07-05 01:10:34 in 5.25s]: IP: 91.171.205.28 / OK / HTTP status: 200
- [2024-07-04 23:18:19 in 0.28s]: IP: 91.171.205.28 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-07-05 10:33:20 in 0.17s]: IP: 91.171.205.28 / OK / HTTP status: 200
- [2024-07-03 02:34:26 in 0.28s]: IP: 91.171.205.28 / OK / HTTP status: 200
- /nodeinfo/2.1 ₍⇗₎
- [2024-07-05 17:14:19 in 1.21s]: IP: 91.171.205.28 / OK / HTTP status: 200
- [2024-07-05 16:18:54 in 1.18s]: IP: 91.171.205.28 / OK / HTTP status: 200
- [2024-07-05 14:26:05 in 0.85s]: IP: 91.171.205.28 / OK / HTTP status: 200
- [2024-07-05 13:25:27 in 1.00s]: IP: 91.171.205.28 / OK / HTTP status: 200
- [2024-07-05 10:33:20 in 0.74s]: IP: 91.171.205.28 / OK / HTTP status: 200
- [2024-07-05 05:51:57 in 0.68s]: IP: 91.171.205.28 / OK / HTTP status: 200
- [2024-07-05 04:55:51 in 0.79s]: IP: 91.171.205.28 / OK / HTTP status: 200
- [2024-07-05 03:03:39 in 0.89s]: IP: 91.171.205.28 / OK / HTTP status: 200
- [2024-07-05 01:10:34 in 1.07s]: IP: 91.171.205.28 / OK / HTTP status: 200
- [2024-07-04 23:18:19 in 0.59s]: IP: 91.171.205.28 / OK / HTTP status: 200