legionify.com — Legionify
Istanza single-user per Bonny
Details
up since 2024-06-29 06:41 (4.2 days ago)
- Uptime: 99.53%
- Users: 1 (1 active this month, 1 active last six months)
- Posts: 127
- Posts per user: 127.00
- Peers: 7726
- Version: sharkey 2024.5.1
- Source code: https://activitypub.software/TransFem-org/Sharkey/
- Registrations: Closed
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-06-19 13:25 — 2024-07-03 11:26
users: 1 (0.00/day)
min/max/avg/stddev: 1 / 1 / 1.00 / 0.00
⋯ ⋯posts: 127 (0.00/day)
min/max/avg/stddev: 127 / 127 / 127.00 / 0.00
⋯ ⋯peers: 7726 (16.90/day)
min/max/avg/stddev: 7490 / 7726 / 7615.60 / 67.68
response_time: 1.839 (-0.04/day)
min/max/avg/stddev: 0 / 20 / 3.42 / 2.88
Crawling Info
First contact: 2023-12-20 (6.5 months ago)
Last successful contact: 2024-07-03 (6.1 minutes ago)
Contact: 11727 successful, 3924 failed.
Average fetch time: 3.42s
Next attempt scheduled for 11.5 minutes from now.
Found through maid.army (up)
IP address: 172.67.192.73
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-07-03 10:12:35 in 0.94s]: IP: 104.21.41.199 / Error: http / HTTP status: 403
- [2024-07-03 09:54:10 in 0.00s]: IP: 104.21.41.199 / Error: http / HTTP status: -1
- [2024-07-03 07:21:48 in 0.89s]: IP: 172.67.192.73 / Error: http / HTTP status: 403
- [2024-07-03 06:23:29 in 1.81s]: IP: 104.21.41.199 / Error: http / HTTP status: 403
- [2024-07-03 05:06:24 in 0.00s]: IP: 104.21.41.199 / Error: http / HTTP status: -1
- [2024-07-03 04:28:38 in 0.00s]: IP: 104.21.41.199 / Error: http / HTTP status: -1
- [2024-07-03 03:10:53 in 1.36s]: IP: 104.21.41.199 / Error: http / HTTP status: 403
- [2024-07-03 02:51:23 in 0.00s]: IP: 104.21.41.199 / Error: http / HTTP status: -1
- [2024-07-03 02:13:33 in 0.00s]: IP: 172.67.192.73 / Error: http / HTTP status: -1
- [2024-07-03 01:35:13 in 1.06s]: IP: 172.67.192.73 / Error: http / HTTP status: 403
- /api/v1/instance ₍⇗₎
- [2024-07-03 11:26:02 in 0.70s]: IP: 172.67.192.73 / OK / HTTP status: 200
- [2024-07-03 11:07:33 in 0.50s]: IP: 104.21.41.199 / OK / HTTP status: 200
- [2024-07-03 10:49:08 in 0.73s]: IP: 172.67.192.73 / OK / HTTP status: 200
- [2024-07-03 10:31:02 in 0.67s]: IP: 104.21.41.199 / OK / HTTP status: 200
- [2024-07-03 09:35:57 in 0.72s]: IP: 104.21.41.199 / OK / HTTP status: 200
- [2024-07-03 09:16:48 in 1.10s]: IP: 172.67.192.73 / OK / HTTP status: 200
- [2024-07-03 08:57:27 in 0.80s]: IP: 104.21.41.199 / OK / HTTP status: 200
- [2024-07-03 08:38:38 in 0.66s]: IP: 172.67.192.73 / OK / HTTP status: 200
- [2024-07-03 08:19:39 in 0.70s]: IP: 104.21.41.199 / OK / HTTP status: 200
- [2024-07-03 08:00:29 in 0.66s]: IP: 172.67.192.73 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-07-03 05:25:12 in 0.36s]: IP: 104.21.41.199 / OK / HTTP status: 200
- [2024-07-02 13:45:02 in 0.32s]: IP: 172.67.192.73 / OK / HTTP status: 200
- [2024-07-02 05:29:35 in 0.32s]: IP: 104.21.41.199 / OK / HTTP status: 200
- [2024-07-01 21:07:57 in 0.32s]: IP: 172.67.192.73 / OK / HTTP status: 200
- [2024-07-01 12:25:55 in 0.34s]: IP: 172.67.192.73 / OK / HTTP status: 200
- [2024-07-01 00:29:54 in 0.32s]: IP: 104.21.41.199 / OK / HTTP status: 200
- [2024-06-30 14:30:30 in 0.32s]: IP: 104.21.41.199 / OK / HTTP status: 200
- /nodeinfo/2.1 ₍⇗₎
- [2024-07-03 11:26:02 in 0.85s]: IP: 172.67.192.73 / OK / HTTP status: 200
- [2024-07-03 11:07:33 in 0.86s]: IP: 104.21.41.199 / OK / HTTP status: 200
- [2024-07-03 10:49:08 in 0.83s]: IP: 172.67.192.73 / OK / HTTP status: 200
- [2024-07-03 10:31:02 in 0.81s]: IP: 104.21.41.199 / OK / HTTP status: 200
- [2024-07-03 09:35:57 in 0.87s]: IP: 104.21.41.199 / OK / HTTP status: 200
- [2024-07-03 09:16:48 in 0.81s]: IP: 172.67.192.73 / OK / HTTP status: 200
- [2024-07-03 08:57:27 in 0.96s]: IP: 104.21.41.199 / OK / HTTP status: 200
- [2024-07-03 08:38:38 in 0.90s]: IP: 172.67.192.73 / OK / HTTP status: 200
- [2024-07-03 08:19:39 in 0.79s]: IP: 104.21.41.199 / OK / HTTP status: 200
- [2024-07-03 08:00:29 in 0.44s]: IP: 172.67.192.73 / OK / HTTP status: 200