ice.legionify.com — Iceshrimp Legionify
Test Iceshrimp
Details
up since 2024-11-15 05:08 (15.5 hours ago)
- Uptime: 46.73%
- Users: 3 (1 active this month, 1 active last six months)
- Posts: 1
- Posts per user: 0.33
- Peers: 1160
- Version: iceshrimp 2023.12.9-dev-447bd10ec
- Source code: https://iceshrimp.dev/iceshrimp/iceshrimp
- Registrations: Invite
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-11-13 03:27 — 2024-11-15 20:22
users: 3 (0.00/day)
min/max/avg/stddev: 3 / 3 / 3.00 / 0.00
⋯ ⋯posts: 1 (0.01/day)
min/max/avg/stddev: 0 / 1 / 0.91 / 0.29
peers: 1160 (0.26/day)
min/max/avg/stddev: 1141 / 1160 / 1152.36 / 5.40
response_time: 4.19 (-0.10/day)
min/max/avg/stddev: 0 / 11 / 4.07 / 3.01
Crawling Info
First contact: 2024-07-03 (4.5 months ago)
Last successful contact: 2024-11-15 (15.7 minutes ago)
Contact: 6460 successful, 3837 failed.
Average fetch time: 4.08s
Next attempt scheduled for 8.8 minutes from now.
Found through blob.cat (up)
IP address: 104.21.41.199 (and legionify.com.)
Staff
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-11-15 17:50:51 in 0.00s]: IP: 172.67.192.73 / Error: http / HTTP status: -1
- [2024-11-15 16:58:24 in 0.00s]: IP: 104.21.41.199 / Error: http / HTTP status: -1
- [2024-11-15 15:42:33 in 0.00s]: IP: 172.67.192.73 / Error: http / HTTP status: -1
- [2024-11-15 09:10:58 in 0.00s]: IP: 104.21.41.199 / Error: http / HTTP status: -1
- [2024-11-15 06:18:17 in 0.00s]: IP: 104.21.41.199 / Error: http / HTTP status: -1
- [2024-11-15 05:44:09 in 0.00s]: IP: 104.21.41.199 / Error: http / HTTP status: -1
- [2024-11-13 03:27:11 in 6.24s]: IP: 199.59.243.227 / Error: unparseable / HTTP status: 200
- /api/v1/instance ₍⇗₎
- [2024-11-15 20:22:31 in 0.40s]: IP: 104.21.41.199 / OK / HTTP status: 200
- [2024-11-15 19:58:20 in 0.21s]: IP: 172.67.192.73 / OK / HTTP status: 200
- [2024-11-15 19:32:52 in 0.22s]: IP: 172.67.192.73 / OK / HTTP status: 200
- [2024-11-15 19:07:05 in 0.47s]: IP: 104.21.41.199 / OK / HTTP status: 200
- [2024-11-15 18:41:56 in 0.34s]: IP: 172.67.192.73 / OK / HTTP status: 200
- [2024-11-15 18:16:07 in 0.60s]: IP: 104.21.41.199 / OK / HTTP status: 200
- [2024-11-15 17:23:41 in 0.22s]: IP: 104.21.41.199 / OK / HTTP status: 200
- [2024-11-15 16:32:54 in 0.38s]: IP: 172.67.192.73 / OK / HTTP status: 200
- [2024-11-15 16:08:23 in 0.23s]: IP: 104.21.41.199 / OK / HTTP status: 200
- [2024-11-15 15:16:23 in 0.23s]: IP: 104.21.41.199 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-11-15 13:58:20 in 0.42s]: IP: 104.21.41.199 / OK / HTTP status: 200
- [2024-11-15 05:08:16 in 0.40s]: IP: 172.67.192.73 / OK / HTTP status: 200
- /nodeinfo/2.1 ₍⇗₎
- [2024-11-15 20:22:31 in 3.11s]: IP: 104.21.41.199 / OK / HTTP status: 200
- [2024-11-15 19:58:20 in 0.82s]: IP: 172.67.192.73 / OK / HTTP status: 200
- [2024-11-15 19:32:52 in 0.86s]: IP: 172.67.192.73 / OK / HTTP status: 200
- [2024-11-15 19:07:05 in 1.54s]: IP: 104.21.41.199 / OK / HTTP status: 200
- [2024-11-15 18:41:56 in 1.51s]: IP: 172.67.192.73 / OK / HTTP status: 200
- [2024-11-15 18:16:07 in 2.68s]: IP: 104.21.41.199 / OK / HTTP status: 200
- [2024-11-15 17:23:41 in 5.49s]: IP: 104.21.41.199 / OK / HTTP status: 200
- [2024-11-15 16:32:54 in 2.19s]: IP: 172.67.192.73 / OK / HTTP status: 200
- [2024-11-15 16:08:23 in 1.05s]: IP: 104.21.41.199 / OK / HTTP status: 200
- [2024-11-15 15:16:23 in 0.82s]: IP: 104.21.41.199 / OK / HTTP status: 200