mk.double-oxygen.net — MISSing_monKEY
当サーバーは，@double_oxygen@mk.double-oxygen.net の専用サーバーです．
最小限のサーバースペックで運用しています．
Details
up since 2024-09-18 04:13 (60.6 days ago)
- Uptime: 99.92%
- Users: 3
- Posts: 87
- Posts per user: 29.00
- Peers: 7691
- Version: misskey 2024.10.1
- Source code: https://github.com/misskey-dev/misskey
- Registrations: Closed
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-11-04 05:09 — 2024-11-17 18:37
users: 3 (0.00/day)
min/max/avg/stddev: 3 / 3 / 3.00 / 0.00
⋯ ⋯posts: 87 (0.14/day)
min/max/avg/stddev: 85 / 87 / 85.65 / 0.68
peers: 7691 (1.42/day)
min/max/avg/stddev: 7670 / 7691 / 7684.15 / 5.74
response_time: 3.531 (0.02/day)
min/max/avg/stddev: 1 / 4 / 2.69 / 1.08
Crawling Info
First contact: 2023-03-11 (20.3 months ago)
Last successful contact: 2024-11-17 (10.9 minutes ago)
Contact: 18156 successful, 4934 failed.
Average fetch time: 2.69s
Next attempt scheduled for 5.8 minutes from now.
Found through misskey.dummy.red (up)
IP address: 162.43.20.32
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-11-17 16:28:50 in 0.00s]: IP: 162.43.20.32 / Error: http / HTTP status: -1
- [2024-11-17 16:11:30 in 0.00s]: IP: 162.43.20.32 / Error: http / HTTP status: -1
- [2024-11-17 14:59:17 in 0.00s]: IP: 162.43.20.32 / Error: http / HTTP status: -1
- [2024-11-17 14:24:23 in 0.00s]: IP: 162.43.20.32 / Error: http / HTTP status: -1
- [2024-11-17 13:49:19 in 0.00s]: IP: 162.43.20.32 / Error: http / HTTP status: -1
- [2024-11-17 13:32:03 in 0.00s]: IP: 162.43.20.32 / Error: http / HTTP status: -1
- [2024-11-17 12:06:08 in 0.00s]: IP: 162.43.20.32 / Error: http / HTTP status: -1
- [2024-11-17 11:13:28 in 0.00s]: IP: 162.43.20.32 / Error: http / HTTP status: -1
- [2024-11-17 10:20:52 in 0.00s]: IP: 162.43.20.32 / Error: http / HTTP status: -1
- [2024-11-17 09:44:52 in 0.00s]: IP: 162.43.20.32 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-11-17 14:41:57 in 0.13s]: IP: 162.43.20.32 / Error: http / HTTP status: 404
- [2024-11-16 23:26:49 in 0.13s]: IP: 162.43.20.32 / Error: http / HTTP status: 404
- [2024-11-16 19:37:58 in 0.71s]: IP: 162.43.20.32 / Error: http / HTTP status: 404
- [2024-11-16 06:36:53 in 0.13s]: IP: 162.43.20.32 / Error: http / HTTP status: 404
- [2024-11-16 04:52:10 in 1.08s]: IP: 162.43.20.32 / Error: http / HTTP status: 404
- [2024-11-16 00:55:14 in 0.59s]: IP: 162.43.20.32 / Error: http / HTTP status: 404
- [2024-11-15 21:15:03 in 0.13s]: IP: 162.43.20.32 / Error: http / HTTP status: 404
- [2024-11-15 20:23:52 in 0.13s]: IP: 162.43.20.32 / Error: http / HTTP status: 404
- [2024-11-15 18:47:11 in 0.13s]: IP: 162.43.20.32 / Error: http / HTTP status: 404
- [2024-11-15 15:20:12 in 0.95s]: IP: 162.43.20.32 / Error: http / HTTP status: 404
- /api/v1/instance/peers ₍⇗₎
- [2024-11-17 11:47:21 in 0.72s]: IP: 162.43.20.32 / OK / HTTP status: 200
- [2024-11-17 03:06:28 in 0.27s]: IP: 162.43.20.32 / OK / HTTP status: 200
- [2024-11-16 18:25:59 in 0.78s]: IP: 162.43.20.32 / OK / HTTP status: 200
- [2024-11-16 07:09:29 in 0.37s]: IP: 162.43.20.32 / OK / HTTP status: 200
- [2024-11-15 19:35:44 in 0.27s]: IP: 162.43.20.32 / OK / HTTP status: 200
- [2024-11-15 10:19:15 in 0.34s]: IP: 162.43.20.32 / OK / HTTP status: 200
- [2024-11-15 00:28:16 in 0.31s]: IP: 162.43.20.32 / OK / HTTP status: 200
- /nodeinfo/2.1 ₍⇗₎
- [2024-11-17 18:37:52 in 0.62s]: IP: 162.43.20.32 / OK / HTTP status: 200
- [2024-11-17 18:19:18 in 1.95s]: IP: 162.43.20.32 / OK / HTTP status: 200
- [2024-11-17 17:59:20 in 4.90s]: IP: 162.43.20.32 / OK / HTTP status: 200
- [2024-11-17 17:40:12 in 0.56s]: IP: 162.43.20.32 / OK / HTTP status: 200
- [2024-11-17 17:21:51 in 2.25s]: IP: 162.43.20.32 / OK / HTTP status: 200
- [2024-11-17 17:03:11 in 4.53s]: IP: 162.43.20.32 / OK / HTTP status: 200
- [2024-11-17 16:45:42 in 0.52s]: IP: 162.43.20.32 / OK / HTTP status: 200
- [2024-11-17 15:53:07 in 0.57s]: IP: 162.43.20.32 / OK / HTTP status: 200
- [2024-11-17 15:34:10 in 4.29s]: IP: 162.43.20.32 / OK / HTTP status: 200
- [2024-11-17 15:16:11 in 2.72s]: IP: 162.43.20.32 / OK / HTTP status: 200