fedi.fh3m.de
fedi.fh3m.de
Details
up since 2024-11-09 21:24 (5.4 days ago)
- Uptime: 0.79%
- Users: 1 (0 active this month, 1 active last six months)
- Posts: 3
- Posts per user: 3.00
- Peers: 0
- Version: snac 2.59
- Registrations: Closed
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-11-10 21:39 — 2024-11-15 07:45
users: 1 (0.00/day)
min/max/avg/stddev: 1 / 1 / 1.00 / 0.00
⋯ —posts: 3 (0.00/day)
min/max/avg/stddev: 3 / 3 / 3.00 / 0.00
⋯ —peers: 0 (0.00/day)
min/max/avg/stddev: 0 / 0 / 0.00 / 0.00
⋯ —response_time: 3.621 (0.39/day)
min/max/avg/stddev: 1 / 3 / 2.65 / 0.97
—
Crawling Info
First contact: 2021-08-08 (3.3 years ago)
Last successful contact: 2024-11-15 (9.1 minutes ago)
Contact: 1002 successful, 270 failed.
Average fetch time: 2.65s
Next attempt scheduled for 7.5 minutes from now.
Found through kinky.business (up)
IP address: 46.101.181.30
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-11-15 07:14:01 in 0.00s]: IP: 46.101.181.30 / Error: http / HTTP status: -1
- [2024-11-15 06:57:54 in 0.00s]: IP: 46.101.181.30 / Error: http / HTTP status: -1
- [2024-11-15 03:26:36 in 0.00s]: IP: 46.101.181.30 / Error: http / HTTP status: -1
- [2024-11-15 00:32:59 in 0.00s]: IP: 46.101.181.30 / Error: http / HTTP status: -1
- [2024-11-15 00:16:52 in 0.00s]: IP: 46.101.181.30 / Error: http / HTTP status: -1
- [2024-11-14 21:52:27 in 0.00s]: IP: 46.101.181.30 / Error: http / HTTP status: -1
- [2024-11-14 21:20:21 in 0.00s]: IP: 46.101.181.30 / Error: http / HTTP status: -1
- [2024-11-14 20:40:33 in 0.00s]: IP: 46.101.181.30 / Error: http / HTTP status: -1
- [2024-11-14 19:19:31 in 0.00s]: IP: 46.101.181.30 / Error: http / HTTP status: -1
- [2024-11-14 18:24:53 in 0.00s]: IP: 46.101.181.30 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-11-15 07:45:44 in 0.31s]: IP: 46.101.181.30 / OK / HTTP status: 200
- [2024-11-15 07:29:52 in 0.30s]: IP: 46.101.181.30 / OK / HTTP status: 200
- [2024-11-15 06:38:01 in 0.37s]: IP: 46.101.181.30 / OK / HTTP status: 200
- [2024-11-15 06:16:04 in 0.28s]: IP: 46.101.181.30 / OK / HTTP status: 200
- [2024-11-15 05:50:11 in 0.45s]: IP: 46.101.181.30 / OK / HTTP status: 200
- [2024-11-15 05:27:53 in 0.24s]: IP: 46.101.181.30 / OK / HTTP status: 200
- [2024-11-15 05:11:40 in 0.16s]: IP: 46.101.181.30 / OK / HTTP status: 200
- [2024-11-15 04:52:54 in 0.16s]: IP: 46.101.181.30 / OK / HTTP status: 200
- [2024-11-15 04:30:17 in 0.61s]: IP: 46.101.181.30 / OK / HTTP status: 200
- [2024-11-15 04:14:20 in 0.16s]: IP: 46.101.181.30 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-11-15 05:27:53 in 0.39s]: IP: 46.101.181.30 / Error: http / HTTP status: 404
- [2024-11-14 19:51:11 in 0.35s]: IP: 46.101.181.30 / Error: http / HTTP status: 404
- [2024-11-14 11:40:00 in 0.15s]: IP: 46.101.181.30 / Error: http / HTTP status: 404
- [2024-11-14 02:45:23 in 0.40s]: IP: 46.101.181.30 / Error: http / HTTP status: 404
- [2024-11-13 16:29:02 in 0.16s]: IP: 46.101.181.30 / Error: http / HTTP status: 404
- [2024-11-13 07:48:32 in 0.15s]: IP: 46.101.181.30 / Error: http / HTTP status: 404
- [2024-11-12 19:05:27 in 0.28s]: IP: 46.101.181.30 / Error: http / HTTP status: 404
- [2024-11-12 09:59:32 in 0.16s]: IP: 46.101.181.30 / Error: http / HTTP status: 404
- /nodeinfo_2_0 ₍⇗₎
- [2024-11-15 07:45:44 in 1.97s]: IP: 46.101.181.30 / OK / HTTP status: 200
- [2024-11-15 07:29:52 in 1.79s]: IP: 46.101.181.30 / OK / HTTP status: 200
- [2024-11-15 06:38:01 in 1.52s]: IP: 46.101.181.30 / OK / HTTP status: 200
- [2024-11-15 06:16:04 in 1.46s]: IP: 46.101.181.30 / OK / HTTP status: 200
- [2024-11-15 05:50:11 in 3.64s]: IP: 46.101.181.30 / OK / HTTP status: 200
- [2024-11-15 05:27:53 in 1.88s]: IP: 46.101.181.30 / OK / HTTP status: 200
- [2024-11-15 05:11:40 in 0.80s]: IP: 46.101.181.30 / OK / HTTP status: 200
- [2024-11-15 04:52:54 in 0.89s]: IP: 46.101.181.30 / OK / HTTP status: 200
- [2024-11-15 04:30:17 in 3.60s]: IP: 46.101.181.30 / OK / HTTP status: 200
- [2024-11-15 04:14:20 in 0.80s]: IP: 46.101.181.30 / OK / HTTP status: 200