misskey.suzuri.jp — SUZURI倶楽部
SUZURI by GMOペパボの公式コミュニティです！
Details
up since 2024-06-10 17:10 (22.7 days ago)
- Uptime: 97.22%
- Users: 184
- Posts: 2024
- Posts per user: 11.00
- Peers: 439
- Version: misskey 2024.5.0
- Source code: https://github.com/misskey-dev/misskey
- Registrations: Open
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-06-19 12:33 — 2024-07-03 10:57
users: 184 (0.64/day)
min/max/avg/stddev: 175 / 184 / 178.86 / 3.02
posts: 2024 (6.62/day)
min/max/avg/stddev: 1931 / 2025 / 1972.78 / 28.47
peers: 439 (2.38/day)
min/max/avg/stddev: 409 / 439 / 423.17 / 10.77
response_time: 1.494 (-0.01/day)
min/max/avg/stddev: 0 / 57 / 3.94 / 5.82
Crawling Info
First contact: 2024-01-13 (5.7 months ago)
Last successful contact: 2024-07-03 (11.9 minutes ago)
Contact: 6748 successful, 1493 failed.
Average fetch time: 3.94s
Next attempt scheduled for 8.2 minutes from now.
Found through misskey.yancya.club (up)
IP address: 18.65.116.87
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-07-03 09:55:15 in 0.00s]: IP: 18.65.116.70 / Error: http / HTTP status: -1
- [2024-07-03 09:34:43 in 0.00s]: IP: 18.65.116.61 / Error: http / HTTP status: -1
- [2024-07-03 04:18:48 in 0.00s]: IP: 18.65.116.122 / Error: http / HTTP status: -1
- [2024-07-03 03:57:46 in 0.00s]: IP: 18.65.116.122 / Error: http / HTTP status: -1
- [2024-07-03 02:53:33 in 0.00s]: IP: 18.65.116.61 / Error: http / HTTP status: -1
- [2024-07-02 13:22:12 in 0.00s]: IP: 3.163.218.35 / Error: http / HTTP status: -1
- [2024-07-02 07:56:08 in 0.00s]: IP: 18.65.116.122 / Error: http / HTTP status: -1
- [2024-07-02 06:14:35 in 0.00s]: IP: 18.65.116.87 / Error: http / HTTP status: -1
- [2024-07-01 23:09:41 in 0.00s]: IP: 3.163.218.25 / Error: http / HTTP status: -1
- [2024-07-01 21:28:49 in 0.00s]: IP: 3.163.218.119 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-07-03 10:57:11 in 0.15s]: IP: 18.65.116.87 / Error: http / HTTP status: 404
- [2024-07-03 05:20:56 in 0.12s]: IP: 18.65.116.87 / Error: http / HTTP status: 404
- [2024-07-02 23:24:11 in 0.58s]: IP: 18.65.116.122 / Error: http / HTTP status: 404
- [2024-07-02 07:15:29 in 0.14s]: IP: 18.65.116.70 / Error: http / HTTP status: 404
- [2024-07-02 03:31:08 in 0.15s]: IP: 18.65.116.122 / Error: http / HTTP status: 404
- [2024-07-02 02:04:48 in 0.15s]: IP: 18.65.116.122 / Error: http / HTTP status: 404
- [2024-07-01 19:23:35 in 0.13s]: IP: 3.163.218.20 / Error: http / HTTP status: 404
- [2024-07-01 18:20:34 in 0.84s]: IP: 18.65.116.61 / Error: http / HTTP status: 404
- [2024-07-01 12:28:37 in 0.13s]: IP: 18.65.116.87 / Error: http / HTTP status: 404
- [2024-07-01 08:54:47 in 0.49s]: IP: 18.65.116.70 / Error: http / HTTP status: 404
- /api/v1/instance/peers ₍⇗₎
- [2024-07-03 03:36:16 in 0.16s]: IP: 18.65.116.70 / OK / HTTP status: 200
- [2024-07-02 18:55:08 in 0.15s]: IP: 18.65.116.61 / OK / HTTP status: 200
- [2024-07-02 07:35:58 in 0.53s]: IP: 18.65.116.70 / OK / HTTP status: 200
- [2024-07-01 21:49:05 in 0.19s]: IP: 3.163.218.119 / OK / HTTP status: 200
- [2024-07-01 12:28:37 in 0.14s]: IP: 18.65.116.87 / OK / HTTP status: 200
- [2024-07-01 04:14:08 in 0.16s]: IP: 18.65.116.61 / OK / HTTP status: 200
- [2024-06-30 18:14:10 in 0.94s]: IP: 18.65.116.61 / OK / HTTP status: 200
- /nodeinfo/2.1 ₍⇗₎
- [2024-07-03 10:57:11 in 0.52s]: IP: 18.65.116.87 / OK / HTTP status: 200
- [2024-07-03 10:36:14 in 0.46s]: IP: 18.65.116.122 / OK / HTTP status: 200
- [2024-07-03 10:15:50 in 0.68s]: IP: 18.65.116.87 / OK / HTTP status: 200
- [2024-07-03 09:13:53 in 2.84s]: IP: 18.65.116.87 / OK / HTTP status: 200
- [2024-07-03 08:52:47 in 4.60s]: IP: 18.65.116.70 / OK / HTTP status: 200
- [2024-07-03 08:31:45 in 0.81s]: IP: 18.65.116.122 / OK / HTTP status: 200
- [2024-07-03 08:10:43 in 0.49s]: IP: 18.65.116.70 / OK / HTTP status: 200
- [2024-07-03 07:49:30 in 3.99s]: IP: 18.65.116.70 / OK / HTTP status: 200
- [2024-07-03 07:28:26 in 0.76s]: IP: 18.65.116.122 / OK / HTTP status: 200
- [2024-07-03 07:07:25 in 0.62s]: IP: 18.65.116.122 / OK / HTTP status: 200