mstdn.funil.de — Mastodon at Funil Networks
Details
up since 2024-10-11 00:43 (37.5 days ago)
- Uptime: 99.72%
- Users: 4 (2 active this month, 3 active last six months)
- Posts: 795
- Posts per user: 198.75
- Peers: 124912
- Version: mastodon 4.2.13
- Registrations: Approval Required
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-11-03 16:12 — 2024-11-17 13:17
users: 4 (0.00/day)
min/max/avg/stddev: 4 / 4 / 4.00 / 0.00
⋯ ⋯posts: 795 (-0.14/day)
min/max/avg/stddev: 794 / 798 / 795.94 / 0.88
peers: 124912 (9.56/day)
min/max/avg/stddev: 124780 / 124912 / 124844.74 / 37.86
response_time: 7.217 (-1.77/day)
min/max/avg/stddev: 0 / 85 / 13.39 / 19.26
Crawling Info
First contact: 2022-12-01 (23.6 months ago)
Last successful contact: 2024-11-17 (21.6 minutes ago)
Contact: 42801 successful, 3039 failed.
Average fetch time: 13.40s
Next attempt scheduled for 25.1 minutes from now.
Found through mastodon.social (up)
IP address: 83.141.25.59
Staff
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-11-17 10:54:29 in 0.00s]: IP: 83.141.25.59 / Error: http / HTTP status: -1
- [2024-11-17 08:29:36 in 0.00s]: IP: 83.141.25.59 / Error: http / HTTP status: -1
- [2024-11-17 07:42:12 in 0.00s]: IP: 83.141.25.59 / Error: http / HTTP status: -1
- [2024-11-17 06:54:55 in 0.00s]: IP: 83.141.25.59 / Error: http / HTTP status: -1
- [2024-11-17 05:19:57 in 0.00s]: IP: 83.141.25.59 / Error: http / HTTP status: -1
- [2024-11-17 04:32:18 in 0.00s]: IP: 83.141.25.59 / Error: http / HTTP status: -1
- [2024-11-17 03:44:57 in 0.00s]: IP: 83.141.25.59 / Error: http / HTTP status: -1
- [2024-11-17 02:09:45 in 0.00s]: IP: 83.141.25.59 / Error: http / HTTP status: -1
- [2024-11-16 23:48:31 in 0.00s]: IP: 83.141.25.59 / Error: http / HTTP status: -1
- [2024-11-16 22:13:56 in 0.00s]: IP: 83.141.25.59 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-11-17 13:17:03 in 0.18s]: IP: 83.141.25.59 / OK / HTTP status: 200
- [2024-11-17 12:29:45 in 0.47s]: IP: 83.141.25.59 / OK / HTTP status: 200
- [2024-11-17 11:42:06 in 0.46s]: IP: 83.141.25.59 / OK / HTTP status: 200
- [2024-11-17 10:06:22 in 0.44s]: IP: 83.141.25.59 / OK / HTTP status: 200
- [2024-11-17 09:17:27 in 0.18s]: IP: 83.141.25.59 / OK / HTTP status: 200
- [2024-11-17 06:07:33 in 0.17s]: IP: 83.141.25.59 / OK / HTTP status: 200
- [2024-11-17 02:57:23 in 0.19s]: IP: 83.141.25.59 / OK / HTTP status: 200
- [2024-11-17 01:22:11 in 0.16s]: IP: 83.141.25.59 / OK / HTTP status: 200
- [2024-11-17 00:35:06 in 0.16s]: IP: 83.141.25.59 / OK / HTTP status: 200
- [2024-11-16 23:01:33 in 0.52s]: IP: 83.141.25.59 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-11-17 02:57:23 in 0.36s]: IP: 83.141.25.59 / Error: unparseable / HTTP status: 200
- [2024-11-16 13:33:58 in 0.34s]: IP: 83.141.25.59 / Error: unparseable / HTTP status: 200
- [2024-11-15 21:53:28 in 0.34s]: IP: 83.141.25.59 / Error: unparseable / HTTP status: 200
- [2024-11-15 07:53:56 in 0.99s]: IP: 83.141.25.59 / Error: unparseable / HTTP status: 200
- [2024-11-14 18:04:52 in 0.35s]: IP: 83.141.25.59 / Error: unparseable / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2024-11-17 13:17:03 in 0.81s]: IP: 83.141.25.59 / OK / HTTP status: 200
- [2024-11-17 12:29:45 in 2.18s]: IP: 83.141.25.59 / OK / HTTP status: 200
- [2024-11-17 11:42:06 in 11.18s]: IP: 83.141.25.59 / OK / HTTP status: 200
- [2024-11-17 10:06:22 in 26.03s]: IP: 83.141.25.59 / OK / HTTP status: 200
- [2024-11-17 09:17:27 in 0.78s]: IP: 83.141.25.59 / OK / HTTP status: 200
- [2024-11-17 06:07:33 in 0.80s]: IP: 83.141.25.59 / OK / HTTP status: 200
- [2024-11-17 02:57:22 in 0.80s]: IP: 83.141.25.59 / OK / HTTP status: 200
- [2024-11-17 01:22:11 in 0.61s]: IP: 83.141.25.59 / OK / HTTP status: 200
- [2024-11-17 00:35:06 in 0.78s]: IP: 83.141.25.59 / OK / HTTP status: 200
- [2024-11-16 23:01:33 in 11.70s]: IP: 83.141.25.59 / OK / HTTP status: 200