rosekey.jp
このサーバーは Rosekey の公式サーバー！！
ジャンルフリーで誰でもご利用いただけます！！！！！
新規登録解放中！！！
Details
up since 2024-06-17 13:07 (18.5 days ago)
- Uptime: 98.80%
- Users: 15
- Posts: 469
- Posts per user: 31.27
- Peers: 463
- Version: rosekey R6.0729.Al1
- Source code: https://github.com/mirielsystems/rosekey
- Registrations: Open
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-06-22 00:54 — 2024-07-06 00:22
users: 15 (0.15/day)
min/max/avg/stddev: 13 / 15 / 14.18 / 0.46
posts: 469 (18.94/day)
min/max/avg/stddev: 210 / 469 / 358.76 / 71.89
peers: 463 (7.09/day)
min/max/avg/stddev: 366 / 463 / 400.81 / 33.28
response_time: 4.153 (0.03/day)
min/max/avg/stddev: 0 / 60 / 5.71 / 8.02
Crawling Info
First contact: 2024-06-02 (33.8 days ago)
Last successful contact: 2024-07-05 (38.5 minutes ago)
Latest attempt: 2024-07-06 (11.9 minutes ago)
Contact: 1417 successful, 441 failed.
Average fetch time: 5.71s
Next attempt scheduled for 13.7 minutes from now.
Found through misskey.m544.net (up)
IP address: 139.162.125.10 (and 4 others: post.miriel.net (down), freelynetwork.jp (down), rosekey.link (down), misskey.pkkis.com (up))
Staff
miriel@rosekey.jp
ども、Miriel「みりえる」です。 Rosekey Read Developer & Rosekey.jp 鯖缶 努めてます。 どうぞ、よろしくお願いします。
ども、Miriel「みりえる」です。 Rosekey Read Developer & Rosekey.jp 鯖缶 努めてます。 どうぞ、よろしくお願いします。
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-07-06 00:22:45 in 0.00s]: IP: 139.162.125.10 / Error: http / HTTP status: -1
- [2024-07-05 23:01:58 in 0.00s]: IP: 139.162.125.10 / Error: http / HTTP status: -1
- [2024-07-05 19:27:59 in 0.00s]: IP: 139.162.125.10 / Error: http / HTTP status: -1
- [2024-07-05 18:32:42 in 0.00s]: IP: 139.162.125.10 / Error: http / HTTP status: -1
- [2024-07-05 17:36:52 in 0.00s]: IP: 139.162.125.10 / Error: http / HTTP status: -1
- [2024-07-05 16:42:49 in 0.00s]: IP: 139.162.125.10 / Error: http / HTTP status: -1
- [2024-07-05 16:16:34 in 0.00s]: IP: 139.162.125.10 / Error: http / HTTP status: -1
- [2024-07-05 14:04:09 in 0.00s]: IP: 139.162.125.10 / Error: http / HTTP status: -1
- [2024-07-05 10:57:42 in 0.00s]: IP: 139.162.125.10 / Error: http / HTTP status: -1
- [2024-07-05 10:31:02 in 0.00s]: IP: 139.162.125.10 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-07-05 11:50:20 in 0.41s]: IP: 139.162.125.10 / Error: http / HTTP status: 401
- [2024-07-04 18:49:41 in 0.40s]: IP: 139.162.125.10 / Error: http / HTTP status: 401
- [2024-07-04 17:56:36 in 0.40s]: IP: 139.162.125.10 / Error: http / HTTP status: 401
- [2024-07-04 06:18:41 in 0.34s]: IP: 139.162.125.10 / Error: http / HTTP status: 401
- [2024-07-03 17:54:17 in 0.38s]: IP: 139.162.125.10 / Error: http / HTTP status: 401
- [2024-07-03 08:19:46 in 0.86s]: IP: 139.162.125.10 / Error: http / HTTP status: 401
- [2024-07-03 00:00:29 in 0.33s]: IP: 139.162.125.10 / Error: http / HTTP status: 401
- /api/v1/instance/peers ₍⇗₎
- [2024-07-05 17:09:28 in 1.30s]: IP: 139.162.125.10 / OK / HTTP status: 200
- [2024-07-05 02:13:14 in 0.87s]: IP: 139.162.125.10 / OK / HTTP status: 200
- [2024-07-04 13:59:30 in 0.17s]: IP: 139.162.125.10 / OK / HTTP status: 200
- [2024-07-04 04:54:35 in 0.16s]: IP: 139.162.125.10 / OK / HTTP status: 200
- [2024-07-03 15:58:35 in 0.17s]: IP: 139.162.125.10 / OK / HTTP status: 200
- /nodeinfo/2.1 ₍⇗₎
- [2024-07-05 23:56:07 in 0.69s]: IP: 139.162.125.10 / OK / HTTP status: 200
- [2024-07-05 22:35:09 in 0.63s]: IP: 139.162.125.10 / OK / HTTP status: 200
- [2024-07-05 22:08:25 in 0.54s]: IP: 139.162.125.10 / OK / HTTP status: 200
- [2024-07-05 21:41:59 in 0.67s]: IP: 139.162.125.10 / OK / HTTP status: 200
- [2024-07-05 21:15:21 in 0.63s]: IP: 139.162.125.10 / OK / HTTP status: 200
- [2024-07-05 20:48:37 in 0.63s]: IP: 139.162.125.10 / OK / HTTP status: 200
- [2024-07-05 20:21:48 in 0.74s]: IP: 139.162.125.10 / OK / HTTP status: 200
- [2024-07-05 19:55:00 in 0.73s]: IP: 139.162.125.10 / OK / HTTP status: 200
- [2024-07-05 19:00:42 in 14.87s]: IP: 139.162.125.10 / OK / HTTP status: 200
- [2024-07-05 18:04:09 in 0.99s]: IP: 139.162.125.10 / OK / HTTP status: 200