misskey.miro-sv.net
おひとりサーバ
Details
up since 2024-06-04 08:29 (29.1 days ago)
- Uptime: 46.29%
- Users: 3
- Posts: 174
- Posts per user: 58.00
- Peers: 3772
- Version: misskey 2024.2.0
- Source code: https://github.com/misskey-dev/misskey
- Registrations: Closed
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-06-19 11:27 — 2024-07-03 10:10
users: 3 (0.00/day)
min/max/avg/stddev: 3 / 3 / 3.00 / 0.00
⋯ ⋯posts: 174 (0.07/day)
min/max/avg/stddev: 173 / 174 / 173.16 / 0.37
peers: 3772 (2.64/day)
min/max/avg/stddev: 3734 / 3772 / 3753.83 / 12.54
response_time: 2.279 (-0.01/day)
min/max/avg/stddev: 0 / 9 / 3.91 / 2.11
Crawling Info
First contact: 2023-03-01 (16.1 months ago)
Last successful contact: 2024-07-03 (8.9 minutes ago)
Contact: 5289 successful, 2143 failed.
Average fetch time: 3.91s
Next attempt scheduled for 10.8 minutes from now.
Found through calckey.jp (nxdomain)
IP address: 162.43.51.16
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-07-03 08:47:15 in 0.00s]: IP: 162.43.51.16 / Error: http / HTTP status: -1
- [2024-07-03 05:16:47 in 0.00s]: IP: 162.43.51.16 / Error: http / HTTP status: -1
- [2024-07-03 04:35:16 in 0.00s]: IP: 162.43.51.16 / Error: http / HTTP status: -1
- [2024-07-02 20:25:31 in 0.00s]: IP: 162.43.51.16 / Error: http / HTTP status: -1
- [2024-07-02 14:46:02 in 0.00s]: IP: 162.43.51.16 / Error: http / HTTP status: -1
- [2024-07-02 12:38:53 in 0.00s]: IP: 162.43.51.16 / Error: http / HTTP status: -1
- [2024-07-02 09:52:26 in 0.00s]: IP: 162.43.51.16 / Error: http / HTTP status: -1
- [2024-07-02 09:12:55 in 0.00s]: IP: 162.43.51.16 / Error: http / HTTP status: -1
- [2024-07-02 08:53:07 in 0.00s]: IP: 162.43.51.16 / Error: http / HTTP status: -1
- [2024-07-02 08:33:02 in 0.00s]: IP: 162.43.51.16 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-07-03 09:07:43 in 0.67s]: IP: 162.43.51.16 / Error: http / HTTP status: 404
- [2024-07-03 00:18:17 in 0.13s]: IP: 162.43.51.16 / Error: http / HTTP status: 404
- [2024-07-02 17:36:43 in 0.13s]: IP: 162.43.51.16 / Error: http / HTTP status: 404
- [2024-07-02 13:20:45 in 0.14s]: IP: 162.43.51.16 / Error: http / HTTP status: 404
- [2024-07-02 11:57:10 in 0.14s]: IP: 162.43.51.16 / Error: http / HTTP status: 404
- [2024-07-02 10:53:04 in 0.63s]: IP: 162.43.51.16 / Error: http / HTTP status: 404
- [2024-07-01 23:31:01 in 0.63s]: IP: 162.43.51.16 / Error: http / HTTP status: 404
- [2024-07-01 07:51:15 in 0.67s]: IP: 162.43.51.16 / Error: http / HTTP status: 404
- [2024-07-01 07:29:29 in 0.13s]: IP: 162.43.51.16 / Error: http / HTTP status: 404
- [2024-07-01 01:56:34 in 1.06s]: IP: 162.43.51.16 / Error: http / HTTP status: 404
- /api/v1/instance/peers ₍⇗₎
- [2024-07-03 04:56:02 in 0.40s]: IP: 162.43.51.16 / OK / HTTP status: 200
- [2024-07-02 20:47:02 in 0.37s]: IP: 162.43.51.16 / OK / HTTP status: 200
- [2024-07-02 11:14:12 in 1.11s]: IP: 162.43.51.16 / OK / HTTP status: 200
- [2024-07-02 02:50:30 in 0.93s]: IP: 162.43.51.16 / OK / HTTP status: 200
- [2024-07-01 17:15:59 in 0.93s]: IP: 162.43.51.16 / OK / HTTP status: 200
- [2024-07-01 07:07:37 in 1.02s]: IP: 162.43.51.16 / OK / HTTP status: 200
- [2024-06-30 22:25:45 in 0.38s]: IP: 162.43.51.16 / OK / HTTP status: 200
- [2024-06-30 12:55:17 in 0.32s]: IP: 162.43.51.16 / OK / HTTP status: 200
- /nodeinfo/2.1 ₍⇗₎
- [2024-07-03 10:10:24 in 0.74s]: IP: 162.43.51.16 / OK / HTTP status: 200
- [2024-07-03 09:49:41 in 0.57s]: IP: 162.43.51.16 / OK / HTTP status: 200
- [2024-07-03 09:28:41 in 2.60s]: IP: 162.43.51.16 / OK / HTTP status: 200
- [2024-07-03 09:07:43 in 2.44s]: IP: 162.43.51.16 / OK / HTTP status: 200
- [2024-07-03 08:26:31 in 0.57s]: IP: 162.43.51.16 / OK / HTTP status: 200
- [2024-07-03 08:05:08 in 3.80s]: IP: 162.43.51.16 / OK / HTTP status: 200
- [2024-07-03 07:43:55 in 2.32s]: IP: 162.43.51.16 / OK / HTTP status: 200
- [2024-07-03 07:23:09 in 0.57s]: IP: 162.43.51.16 / OK / HTTP status: 200
- [2024-07-03 07:02:34 in 0.56s]: IP: 162.43.51.16 / OK / HTTP status: 200
- [2024-07-03 06:42:07 in 0.52s]: IP: 162.43.51.16 / OK / HTTP status: 200