umickey.dev — umickey
@Umisyo@umickey.devが運営するお一人様インスタンスです
Details
up since 2024-06-27 11:22 (45.2 hours ago)
- Uptime: 97.88%
- Users: 6 (2 active this month, 2 active last six months)
- Posts: 813
- Posts per user: 135.50
- Peers: 2486
- Version: calckey 13.1.4.1
- Source code: https://github.com/misskey-dev/misskey
- Registrations: Closed
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-06-15 18:40 — 2024-06-29 08:33
users: 6 (0.00/day)
min/max/avg/stddev: 6 / 6 / 6.00 / 0.00
⋯ ⋯posts: 813 (0.50/day)
min/max/avg/stddev: 806 / 813 / 810.58 / 2.39
peers: 2486 (8.21/day)
min/max/avg/stddev: 2371 / 2486 / 2417.69 / 32.08
response_time: 1.357 (-0.36/day)
min/max/avg/stddev: 0 / 62 / 8.04 / 10.73
Crawling Info
First contact: 2023-07-09 (11.7 months ago)
Last successful contact: 2024-06-29 (156.0 minutes ago)
Latest attempt: 2024-06-29 (7.2 seconds ago)
Contact: 11588 successful, 3833 failed.
Average fetch time: 8.04s
Next attempt scheduled for 30.4 minutes from now.
Found through mk.shrimpia.network (up)
IP address: 172.67.154.147 (and www.nbloglinks.com.)
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-06-29 08:33:46 in 0.00s]: IP: 172.67.154.147 / Error: http / HTTP status: -1
- [2024-06-29 08:02:02 in 1.13s]: IP: 172.67.154.147 / Error: http / HTTP status: 403
- [2024-06-29 07:30:26 in 2.00s]: IP: 172.67.154.147 / Error: http / HTTP status: 403
- [2024-06-29 06:59:42 in 0.91s]: IP: 104.21.32.202 / Error: http / HTTP status: 403
- [2024-06-29 06:28:54 in 0.00s]: IP: 172.67.154.147 / Error: http / HTTP status: -1
- [2024-06-29 04:53:12 in 2.03s]: IP: 172.67.154.147 / Error: http / HTTP status: 403
- [2024-06-29 04:21:47 in 2.90s]: IP: 172.67.154.147 / Error: http / HTTP status: 403
- [2024-06-29 02:47:57 in 0.00s]: IP: 104.21.32.202 / Error: http / HTTP status: -1
- [2024-06-29 01:44:07 in 4.08s]: IP: 172.67.154.147 / Error: http / HTTP status: 403
- [2024-06-29 01:12:41 in 0.00s]: IP: 172.67.154.147 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-06-29 05:57:55 in 0.68s]: IP: 104.21.32.202 / OK / HTTP status: 200
- [2024-06-29 05:25:49 in 2.02s]: IP: 172.67.154.147 / OK / HTTP status: 200
- [2024-06-29 03:50:29 in 0.30s]: IP: 172.67.154.147 / OK / HTTP status: 200
- [2024-06-29 03:19:13 in 0.68s]: IP: 104.21.32.202 / OK / HTTP status: 200
- [2024-06-29 00:09:36 in 2.22s]: IP: 104.21.32.202 / OK / HTTP status: 200
- [2024-06-28 23:06:47 in 1.25s]: IP: 104.21.32.202 / OK / HTTP status: 200
- [2024-06-28 21:33:39 in 1.62s]: IP: 172.67.154.147 / OK / HTTP status: 200
- [2024-06-28 19:27:57 in 2.03s]: IP: 104.21.32.202 / OK / HTTP status: 200
- [2024-06-28 18:25:15 in 1.61s]: IP: 172.67.154.147 / OK / HTTP status: 200
- [2024-06-28 17:21:16 in 2.03s]: IP: 172.67.154.147 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-06-29 05:25:48 in 0.24s]: IP: 172.67.154.147 / OK / HTTP status: 200
- [2024-06-28 18:25:15 in 0.21s]: IP: 172.67.154.147 / OK / HTTP status: 200
- [2024-06-28 09:25:58 in 0.23s]: IP: 104.21.32.202 / OK / HTTP status: 200
- [2024-06-28 00:04:33 in 0.26s]: IP: 104.21.32.202 / OK / HTTP status: 200
- [2024-06-27 05:41:22 in 0.24s]: IP: 172.67.154.147 / OK / HTTP status: 200
- [2024-06-26 17:51:41 in 0.24s]: IP: 104.21.32.202 / OK / HTTP status: 200
- /nodeinfo/2.1 ₍⇗₎
- [2024-06-29 05:57:55 in 0.33s]: IP: 104.21.32.202 / OK / HTTP status: 200
- [2024-06-29 05:25:48 in 0.93s]: IP: 172.67.154.147 / OK / HTTP status: 200
- [2024-06-29 03:50:29 in 0.85s]: IP: 172.67.154.147 / OK / HTTP status: 200
- [2024-06-29 03:19:13 in 0.68s]: IP: 104.21.32.202 / OK / HTTP status: 200
- [2024-06-29 00:09:36 in 0.70s]: IP: 104.21.32.202 / OK / HTTP status: 200
- [2024-06-28 23:06:47 in 0.75s]: IP: 104.21.32.202 / OK / HTTP status: 200
- [2024-06-28 21:33:39 in 0.85s]: IP: 172.67.154.147 / OK / HTTP status: 200
- [2024-06-28 19:27:57 in 0.67s]: IP: 104.21.32.202 / OK / HTTP status: 200
- [2024-06-28 18:25:15 in 0.75s]: IP: 172.67.154.147 / OK / HTTP status: 200
- [2024-06-28 17:21:16 in 0.57s]: IP: 172.67.154.147 / OK / HTTP status: 200