misskey.sagt.xyz — Misskey @ sagt.xyz
Ein Misskey Instanz zum ausprobieren
Details
up since 2023-04-28 11:57 (12.6 months ago)
- Uptime: 99.37%
- Users: 3 (0 active this month, 0 active last six months)
- Posts: 20
- Posts per user: 6.67
- Peers: 1919
- Version: misskey 13.14.2
- Registrations: Closed
[View Timeline] (← Broken) | [View Timeline Media]
Stats
No successful contact during the given timeframe.
Crawling Info
First contact: 2022-03-12 (26.2 months ago)
Last successful contact: 2024-05-17 (38.4 minutes ago)
Contact: 7735 successful, 4475 failed.
Average fetch time: 11.71s
Next attempt scheduled for 44.1 seconds ago.
Found through friendica.vrije-mens.org (down)
IP address: 94.130.18.135 (and 3 others: lemmy.myifn.de (down), toot.krinetzki.de (up), mstdn.myifn.de (up))
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-05-17 08:10:22 in 0.00s]: IP: 94.130.18.135 / Error: http / HTTP status: -1
- [2024-05-17 02:35:03 in 0.00s]: IP: 94.130.18.135 / Error: http / HTTP status: -1
- [2024-05-17 01:44:42 in 0.00s]: IP: 94.130.18.135 / Error: http / HTTP status: -1
- [2024-05-16 17:28:05 in 0.00s]: IP: 94.130.18.135 / Error: http / HTTP status: -1
- [2024-05-16 12:13:05 in 0.00s]: IP: 94.130.18.135 / Error: http / HTTP status: -1
- [2024-05-16 00:53:20 in 0.00s]: IP: 94.130.18.135 / Error: http / HTTP status: -1
- [2024-05-16 00:27:57 in 0.00s]: IP: 94.130.18.135 / Error: http / HTTP status: -1
- [2024-05-15 22:33:33 in 0.00s]: IP: 94.130.18.135 / Error: http / HTTP status: -1
- [2024-05-15 22:11:22 in 0.00s]: IP: 94.130.18.135 / Error: http / HTTP status: -1
- [2024-05-15 21:34:12 in 0.00s]: IP: 94.130.18.135 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-05-17 09:04:02 in 0.16s]: IP: 94.130.18.135 / Error: http / HTTP status: 404
- [2024-05-17 03:48:06 in 9.22s]: IP: 94.130.18.135 / Error: http / HTTP status: 404
- [2024-05-16 23:31:51 in 0.16s]: IP: 94.130.18.135 / Error: http / HTTP status: 404
- [2024-05-16 22:33:54 in 0.57s]: IP: 94.130.18.135 / Error: http / HTTP status: 404
- [2024-05-16 15:45:47 in 0.15s]: IP: 94.130.18.135 / Error: http / HTTP status: 404
- [2024-05-15 20:25:34 in 0.16s]: IP: 94.130.18.135 / Error: http / HTTP status: 404
- [2024-05-15 15:05:26 in 0.16s]: IP: 94.130.18.135 / Error: http / HTTP status: 404
- [2024-05-15 06:46:17 in 0.15s]: IP: 94.130.18.135 / Error: http / HTTP status: 404
- /api/v1/instance/peers ₍⇗₎
- [2024-05-17 08:46:13 in 0.32s]: IP: 94.130.18.135 / OK / HTTP status: 200
- [2024-05-16 20:11:21 in 0.35s]: IP: 94.130.18.135 / OK / HTTP status: 200
- [2024-05-16 09:54:30 in 2.69s]: IP: 94.130.18.135 / OK / HTTP status: 200
- [2024-05-15 23:51:46 in 1.33s]: IP: 94.130.18.135 / OK / HTTP status: 200
- [2024-05-15 12:59:13 in 0.32s]: IP: 94.130.18.135 / OK / HTTP status: 200
- [2024-05-15 04:14:02 in 0.34s]: IP: 94.130.18.135 / OK / HTTP status: 200
- [2024-05-14 16:54:07 in 0.34s]: IP: 94.130.18.135 / OK / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2024-05-17 11:22:43 in 4.21s]: IP: 94.130.18.135 / OK / HTTP status: 200
- [2024-05-17 10:37:17 in 11.37s]: IP: 94.130.18.135 / OK / HTTP status: 200
- [2024-05-17 10:04:28 in 0.68s]: IP: 94.130.18.135 / OK / HTTP status: 200
- [2024-05-17 09:22:37 in 11.76s]: IP: 94.130.18.135 / OK / HTTP status: 200
- [2024-05-17 09:04:02 in 0.68s]: IP: 94.130.18.135 / OK / HTTP status: 200
- [2024-05-17 08:46:13 in 0.62s]: IP: 94.130.18.135 / OK / HTTP status: 200
- [2024-05-17 08:27:13 in 0.65s]: IP: 94.130.18.135 / OK / HTTP status: 200
- [2024-05-17 07:44:01 in 0.68s]: IP: 94.130.18.135 / OK / HTTP status: 200
- [2024-05-17 07:08:39 in 0.65s]: IP: 94.130.18.135 / OK / HTTP status: 200
- [2024-05-17 06:26:36 in 9.52s]: IP: 94.130.18.135 / OK / HTTP status: 200