misskey.lavacat.obl.ong — new lavacat's social
New instance, made because of troubles with previous ones. Made by @lavacat for @lavacat and others
Art used as instance background made by @00aa@misskey.io
Details
up since 2024-06-23 20:10 (7.7 days ago)
- Uptime: 99.73%
- Users: 6
- Posts: 277
- Posts per user: 46.17
- Peers: 1477
- Version: misskey 2024.5.0
- Source code: https://github.com/misskey-dev/misskey
- Registrations: Open
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-06-17 15:07 — 2024-07-01 12:04
users: 6 (0.07/day)
min/max/avg/stddev: 5 / 6 / 5.24 / 0.43
posts: 277 (13.95/day)
min/max/avg/stddev: 83 / 277 / 188.76 / 54.56
peers: 1477 (54.62/day)
min/max/avg/stddev: 760 / 1477 / 1161.50 / 199.98
response_time: 1.614 (-4.32/day)
min/max/avg/stddev: 0 / 75 / 11.34 / 21.24
Crawling Info
First contact: 2024-06-13 (18.0 days ago)
Last successful contact: 2024-07-01 (24.7 minutes ago)
Contact: 435 successful, 335 failed.
Average fetch time: 11.35s
Next attempt scheduled for 11.6 minutes from now.
Found through udongein.xyz (up)
IP address: 5.3.233.252 (and lavacat.dns.army.)
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-07-01 08:12:38 in 0.00s]: IP: 5.3.233.252 / Error: http / HTTP status: -1
- [2024-06-30 21:59:52 in 0.00s]: IP: 5.3.233.252 / Error: http / HTTP status: -1
- [2024-06-30 20:42:14 in 0.00s]: IP: 5.3.233.252 / Error: http / HTTP status: -1
- [2024-06-30 19:24:06 in 0.00s]: IP: 5.3.233.252 / Error: http / HTTP status: -1
- [2024-06-30 17:29:29 in 0.00s]: IP: 5.3.233.252 / Error: http / HTTP status: -1
- [2024-06-30 16:52:29 in 0.00s]: IP: 5.3.233.252 / Error: http / HTTP status: -1
- [2024-06-30 14:23:08 in 0.00s]: IP: 5.3.233.252 / Error: http / HTTP status: -1
- [2024-06-30 08:41:52 in 0.00s]: IP: 5.3.233.252 / Error: http / HTTP status: -1
- [2024-06-30 04:27:27 in 0.00s]: IP: 5.3.233.252 / Error: http / HTTP status: -1
- [2024-06-29 18:39:10 in 0.00s]: IP: 5.3.233.252 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-06-30 20:02:39 in 0.22s]: IP: 5.3.233.252 / Error: http / HTTP status: 404
- [2024-06-30 11:53:51 in 0.20s]: IP: 5.3.233.252 / Error: http / HTTP status: 404
- [2024-06-29 21:44:05 in 0.19s]: IP: 5.3.233.252 / Error: http / HTTP status: 404
- [2024-06-29 16:13:48 in 0.20s]: IP: 5.3.233.252 / Error: http / HTTP status: 404
- [2024-06-29 09:14:23 in 0.20s]: IP: 5.3.233.252 / Error: http / HTTP status: 404
- [2024-06-29 01:57:50 in 0.19s]: IP: 5.3.233.252 / Error: http / HTTP status: 404
- /api/v1/instance/peers ₍⇗₎
- [2024-07-01 01:51:36 in 0.30s]: IP: 5.3.233.252 / OK / HTTP status: 200
- [2024-06-30 12:31:29 in 0.28s]: IP: 5.3.233.252 / OK / HTTP status: 200
- [2024-06-29 21:44:05 in 0.26s]: IP: 5.3.233.252 / OK / HTTP status: 200
- [2024-06-29 01:22:13 in 0.30s]: IP: 5.3.233.252 / OK / HTTP status: 200
- [2024-06-28 14:37:04 in 0.27s]: IP: 5.3.233.252 / OK / HTTP status: 200
- /nodeinfo/2.1 ₍⇗₎
- [2024-07-01 12:04:27 in 0.82s]: IP: 5.3.233.252 / OK / HTTP status: 200
- [2024-07-01 11:27:25 in 0.95s]: IP: 5.3.233.252 / OK / HTTP status: 200
- [2024-07-01 10:13:52 in 1.10s]: IP: 5.3.233.252 / OK / HTTP status: 200
- [2024-07-01 08:53:23 in 1.14s]: IP: 5.3.233.252 / OK / HTTP status: 200
- [2024-07-01 06:53:31 in 0.95s]: IP: 5.3.233.252 / OK / HTTP status: 200
- [2024-07-01 05:36:04 in 1.23s]: IP: 5.3.233.252 / OK / HTTP status: 200
- [2024-07-01 04:20:24 in 1.00s]: IP: 5.3.233.252 / OK / HTTP status: 200
- [2024-07-01 01:51:36 in 0.93s]: IP: 5.3.233.252 / OK / HTTP status: 200
- [2024-07-01 01:14:35 in 0.82s]: IP: 5.3.233.252 / OK / HTTP status: 200
- [2024-07-01 00:37:32 in 1.11s]: IP: 5.3.233.252 / OK / HTTP status: 200