maniakey.com — Maniakey
Details
up since 2024-06-25 20:45 (22.9 hours ago)
- Uptime: 99.62%
- Users: 685 (3 active this month, 5 active last six months)
- Posts: 409553
- Posts per user: 597.89
- Peers: 7888
- Version: misskey 2024.5.0-MA
- Source code: https://github.com/Otaku-Social/maniakey
- Registrations: Closed
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-06-12 22:25 — 2024-06-26 19:27
users: 685 (0.64/day)
min/max/avg/stddev: 676 / 685 / 680.68 / 1.73
posts: 409553 (824.69/day)
min/max/avg/stddev: 398012 / 409553 / 403812.36 / 3240.12
peers: 7888 (2.71/day)
min/max/avg/stddev: 7851 / 7888 / 7870.33 / 11.24
response_time: 0.589 (-0.28/day)
min/max/avg/stddev: 0 / 24 / 2.17 / 3.03
Crawling Info
First contact: 2022-12-11 (18.5 months ago)
Last successful contact: 2024-06-26 (12.7 minutes ago)
Contact: 13481 successful, 9603 failed.
Average fetch time: 2.17s
Next attempt scheduled for 140.7 seconds from now.
Found through pleroma.noellabo.jp (up)
IP address: 172.67.218.112
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-06-26 18:41:07 in 0.00s]: IP: 104.21.67.79 / Error: http / HTTP status: -1
- [2024-06-26 18:25:36 in 0.00s]: IP: 104.21.67.79 / Error: http / HTTP status: -1
- [2024-06-26 17:54:09 in 1.74s]: IP: 172.67.218.112 / Error: http / HTTP status: 403
- [2024-06-26 17:05:58 in 2.00s]: IP: 172.67.218.112 / Error: http / HTTP status: 403
- [2024-06-26 16:19:05 in 1.46s]: IP: 172.67.218.112 / Error: http / HTTP status: 403
- [2024-06-26 15:46:18 in 0.00s]: IP: 172.67.218.112 / Error: http / HTTP status: -1
- [2024-06-26 15:30:44 in 2.21s]: IP: 104.21.67.79 / Error: http / HTTP status: 403
- [2024-06-26 15:15:02 in 0.00s]: IP: 104.21.67.79 / Error: http / HTTP status: -1
- [2024-06-26 14:59:22 in 1.68s]: IP: 104.21.67.79 / Error: http / HTTP status: 403
- [2024-06-26 14:27:40 in 1.53s]: IP: 104.21.67.79 / Error: http / HTTP status: 403
- /api/v1/instance ₍⇗₎
- [2024-06-26 10:27:32 in 0.15s]: IP: 104.21.67.79 / Error: http / HTTP status: 404
- [2024-06-25 20:45:29 in 0.16s]: IP: 104.21.67.79 / Error: http / HTTP status: 404
- [2024-06-25 18:37:54 in 0.14s]: IP: 172.67.218.112 / Error: http / HTTP status: 404
- [2024-06-25 15:53:03 in 0.13s]: IP: 172.67.218.112 / Error: http / HTTP status: 404
- [2024-06-24 04:18:49 in 0.13s]: IP: 104.21.67.79 / Error: http / HTTP status: 404
- [2024-06-24 00:44:19 in 0.17s]: IP: 104.21.67.79 / Error: http / HTTP status: 404
- [2024-06-23 23:10:12 in 0.13s]: IP: 172.67.218.112 / Error: http / HTTP status: 404
- /api/v1/instance/peers ₍⇗₎
- [2024-06-26 14:43:18 in 0.30s]: IP: 172.67.218.112 / OK / HTTP status: 200
- [2024-06-26 06:14:30 in 0.29s]: IP: 104.21.67.79 / OK / HTTP status: 200
- [2024-06-25 22:13:32 in 0.27s]: IP: 104.21.67.79 / OK / HTTP status: 200
- [2024-06-25 09:16:48 in 0.26s]: IP: 172.67.218.112 / OK / HTTP status: 200
- [2024-06-24 23:55:24 in 0.32s]: IP: 104.21.67.79 / OK / HTTP status: 200
- [2024-06-24 10:32:44 in 0.32s]: IP: 104.21.67.79 / OK / HTTP status: 200
- [2024-06-23 22:08:22 in 0.27s]: IP: 172.67.218.112 / OK / HTTP status: 200
- /nodeinfo/2.1 ₍⇗₎
- [2024-06-26 19:27:45 in 0.59s]: IP: 172.67.218.112 / OK / HTTP status: 200
- [2024-06-26 19:12:09 in 3.62s]: IP: 104.21.67.79 / OK / HTTP status: 200
- [2024-06-26 18:56:46 in 0.60s]: IP: 104.21.67.79 / OK / HTTP status: 200
- [2024-06-26 18:09:36 in 0.58s]: IP: 172.67.218.112 / OK / HTTP status: 200
- [2024-06-26 17:37:42 in 0.67s]: IP: 104.21.67.79 / OK / HTTP status: 200
- [2024-06-26 17:21:38 in 0.59s]: IP: 104.21.67.79 / OK / HTTP status: 200
- [2024-06-26 16:50:39 in 0.60s]: IP: 104.21.67.79 / OK / HTTP status: 200
- [2024-06-26 16:34:47 in 0.60s]: IP: 172.67.218.112 / OK / HTTP status: 200
- [2024-06-26 16:02:11 in 0.64s]: IP: 172.67.218.112 / OK / HTTP status: 200
- [2024-06-26 14:43:17 in 0.62s]: IP: 172.67.218.112 / OK / HTTP status: 200