misskey.azumabashi.dev
Azumabashi の個人用インスタンスです．
Details
up since 2024-06-10 15:23 (22.8 days ago)
- Uptime: 99.56%
- Users: 2 (1 active this month, 1 active last six months)
- Posts: 1912
- Posts per user: 956.00
- Peers: 1320
- Version: misskey 2024.5.0
- Source code: https://github.com/misskey-dev/misskey
- Registrations: Closed
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-06-19 15:59 — 2024-07-03 11:26
users: 2 (0.00/day)
min/max/avg/stddev: 2 / 2 / 2.00 / 0.00
⋯ ⋯posts: 1912 (4.41/day)
min/max/avg/stddev: 1851 / 1912 / 1884.58 / 18.19
peers: 1320 (2.39/day)
min/max/avg/stddev: 1287 / 1320 / 1301.97 / 10.88
response_time: 2.406 (0.14/day)
min/max/avg/stddev: 0 / 8 / 2.98 / 1.94
Crawling Info
First contact: 2022-11-22 (19.4 months ago)
Last successful contact: 2024-07-03 (13.4 minutes ago)
Contact: 10960 successful, 3121 failed.
Average fetch time: 2.98s
Next attempt scheduled for 120.7 seconds from now.
Found through social.digitalcastle.me (nxdomain)
IP address: 202.222.11.41
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-07-03 08:57:21 in 0.00s]: IP: 202.222.11.41 / Error: http / HTTP status: -1
- [2024-07-03 08:41:06 in 0.00s]: IP: 202.222.11.41 / Error: http / HTTP status: -1
- [2024-07-03 06:11:23 in 0.00s]: IP: 202.222.11.41 / Error: http / HTTP status: -1
- [2024-07-03 05:54:56 in 0.00s]: IP: 202.222.11.41 / Error: http / HTTP status: -1
- [2024-07-03 05:22:23 in 0.00s]: IP: 202.222.11.41 / Error: http / HTTP status: -1
- [2024-07-03 05:05:39 in 0.00s]: IP: 202.222.11.41 / Error: http / HTTP status: -1
- [2024-07-03 02:01:09 in 0.00s]: IP: 202.222.11.41 / Error: http / HTTP status: -1
- [2024-07-03 01:44:02 in 0.00s]: IP: 202.222.11.41 / Error: http / HTTP status: -1
- [2024-07-02 23:14:45 in 0.00s]: IP: 202.222.11.41 / Error: http / HTTP status: -1
- [2024-07-02 21:52:31 in 0.00s]: IP: 202.222.11.41 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-07-02 21:35:57 in 0.13s]: IP: 202.222.11.41 / Error: http / HTTP status: 404
- [2024-07-02 18:32:42 in 0.11s]: IP: 202.222.11.41 / Error: http / HTTP status: 404
- [2024-07-01 22:56:19 in 0.74s]: IP: 202.222.11.41 / Error: http / HTTP status: 404
- [2024-07-01 17:40:10 in 0.10s]: IP: 202.222.11.41 / Error: http / HTTP status: 404
- [2024-06-30 19:01:55 in 0.12s]: IP: 202.222.11.41 / Error: http / HTTP status: 404
- [2024-06-30 18:21:38 in 0.12s]: IP: 202.222.11.41 / Error: http / HTTP status: 404
- /api/v1/instance/peers ₍⇗₎
- [2024-07-03 07:18:29 in 1.12s]: IP: 202.222.11.41 / OK / HTTP status: 200
- [2024-07-02 21:35:57 in 0.32s]: IP: 202.222.11.41 / OK / HTTP status: 200
- [2024-07-02 10:57:17 in 0.30s]: IP: 202.222.11.41 / OK / HTTP status: 200
- [2024-07-02 00:27:39 in 0.30s]: IP: 202.222.11.41 / OK / HTTP status: 200
- [2024-07-01 14:32:43 in 1.26s]: IP: 202.222.11.41 / OK / HTTP status: 200
- [2024-07-01 06:02:28 in 0.24s]: IP: 202.222.11.41 / OK / HTTP status: 200
- [2024-06-30 20:23:14 in 0.95s]: IP: 202.222.11.41 / OK / HTTP status: 200
- /nodeinfo/2.1 ₍⇗₎
- [2024-07-03 11:26:01 in 0.42s]: IP: 202.222.11.41 / OK / HTTP status: 200
- [2024-07-03 11:09:43 in 2.62s]: IP: 202.222.11.41 / OK / HTTP status: 200
- [2024-07-03 10:53:16 in 0.51s]: IP: 202.222.11.41 / OK / HTTP status: 200
- [2024-07-03 10:36:49 in 0.51s]: IP: 202.222.11.41 / OK / HTTP status: 200
- [2024-07-03 10:20:24 in 2.55s]: IP: 202.222.11.41 / OK / HTTP status: 200
- [2024-07-03 10:03:47 in 0.63s]: IP: 202.222.11.41 / OK / HTTP status: 200
- [2024-07-03 09:47:12 in 2.43s]: IP: 202.222.11.41 / OK / HTTP status: 200
- [2024-07-03 09:30:30 in 3.02s]: IP: 202.222.11.41 / OK / HTTP status: 200
- [2024-07-03 09:13:50 in 2.60s]: IP: 202.222.11.41 / OK / HTTP status: 200
- [2024-07-03 08:24:44 in 0.44s]: IP: 202.222.11.41 / OK / HTTP status: 200