aschaffenburg.social — Mastodon
Details
up since 2024-10-22 08:58 (14.4 days ago)
- Uptime: 99.51%
- Users: 27 (15 active this month, 19 active last six months)
- Posts: 2782
- Posts per user: 103.04
- Peers: 12493
- Version: mastodon 4.2.13
- Registrations: Invite
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-10-22 22:26 — 2024-11-05 19:20
users: 27 (0.00/day)
min/max/avg/stddev: 27 / 27 / 27.00 / 0.00
⋯ ⋯posts: 2782 (5.25/day)
min/max/avg/stddev: 2709 / 2782 / 2742.91 / 20.55
peers: 12493 (9.29/day)
min/max/avg/stddev: 12364 / 12493 / 12437.71 / 42.22
response_time: 3.539 (0.09/day)
min/max/avg/stddev: 0 / 32 / 2.63 / 3.06
Crawling Info
First contact: 2023-04-12 (18.8 months ago)
Last successful contact: 2024-11-05 (16.9 minutes ago)
Contact: 42639 successful, 2760 failed.
Average fetch time: 2.63s
Next attempt scheduled for 30.3 seconds ago.
Found through meld.de (down)
IP address: 176.96.139.65
Staff
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-11-05 18:28:47 in 0.00s]: IP: 176.96.139.65 / Error: http / HTTP status: -1
- [2024-11-05 16:45:54 in 0.00s]: IP: 176.96.139.65 / Error: http / HTTP status: -1
- [2024-11-05 15:19:59 in 0.00s]: IP: 176.96.139.65 / Error: http / HTTP status: -1
- [2024-11-05 13:35:54 in 0.00s]: IP: 176.96.139.65 / Error: http / HTTP status: -1
- [2024-11-05 12:44:50 in 0.00s]: IP: 176.96.139.65 / Error: http / HTTP status: -1
- [2024-11-05 11:53:41 in 0.00s]: IP: 176.96.139.65 / Error: http / HTTP status: -1
- [2024-11-05 11:02:03 in 0.00s]: IP: 176.96.139.65 / Error: http / HTTP status: -1
- [2024-11-05 09:50:24 in 0.00s]: IP: 176.96.139.65 / Error: http / HTTP status: -1
- [2024-11-05 09:32:25 in 0.00s]: IP: 176.96.139.65 / Error: http / HTTP status: -1
- [2024-11-05 07:03:33 in 0.00s]: IP: 176.96.139.65 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-11-05 19:20:24 in 0.27s]: IP: 176.96.139.65 / OK / HTTP status: 200
- [2024-11-05 19:03:18 in 0.17s]: IP: 176.96.139.65 / OK / HTTP status: 200
- [2024-11-05 18:45:56 in 0.18s]: IP: 176.96.139.65 / OK / HTTP status: 200
- [2024-11-05 18:11:25 in 0.21s]: IP: 176.96.139.65 / OK / HTTP status: 200
- [2024-11-05 17:54:27 in 0.24s]: IP: 176.96.139.65 / OK / HTTP status: 200
- [2024-11-05 17:37:09 in 0.24s]: IP: 176.96.139.65 / OK / HTTP status: 200
- [2024-11-05 17:19:48 in 0.53s]: IP: 176.96.139.65 / OK / HTTP status: 200
- [2024-11-05 17:02:57 in 0.16s]: IP: 176.96.139.65 / OK / HTTP status: 200
- [2024-11-05 16:28:48 in 0.27s]: IP: 176.96.139.65 / OK / HTTP status: 200
- [2024-11-05 16:11:43 in 0.54s]: IP: 176.96.139.65 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-11-05 19:20:24 in 0.18s]: IP: 176.96.139.65 / OK / HTTP status: 200
- [2024-11-05 08:50:52 in 0.18s]: IP: 176.96.139.65 / OK / HTTP status: 200
- [2024-11-05 00:38:19 in 0.35s]: IP: 176.96.139.65 / OK / HTTP status: 200
- [2024-11-04 15:46:20 in 0.18s]: IP: 176.96.139.65 / OK / HTTP status: 200
- [2024-11-04 05:28:15 in 0.17s]: IP: 176.96.139.65 / OK / HTTP status: 200
- [2024-11-03 20:13:58 in 0.23s]: IP: 176.96.139.65 / OK / HTTP status: 200
- [2024-11-03 10:39:02 in 0.20s]: IP: 176.96.139.65 / OK / HTTP status: 200
- [2024-11-03 01:46:52 in 0.24s]: IP: 176.96.139.65 / OK / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2024-11-05 19:20:24 in 1.10s]: IP: 176.96.139.65 / OK / HTTP status: 200
- [2024-11-05 19:03:18 in 0.80s]: IP: 176.96.139.65 / OK / HTTP status: 200
- [2024-11-05 18:45:56 in 0.83s]: IP: 176.96.139.65 / OK / HTTP status: 200
- [2024-11-05 18:11:25 in 1.01s]: IP: 176.96.139.65 / OK / HTTP status: 200
- [2024-11-05 17:54:27 in 1.13s]: IP: 176.96.139.65 / OK / HTTP status: 200
- [2024-11-05 17:37:09 in 1.37s]: IP: 176.96.139.65 / OK / HTTP status: 200
- [2024-11-05 17:19:48 in 1.72s]: IP: 176.96.139.65 / OK / HTTP status: 200
- [2024-11-05 17:02:57 in 0.80s]: IP: 176.96.139.65 / OK / HTTP status: 200
- [2024-11-05 16:28:48 in 1.33s]: IP: 176.96.139.65 / OK / HTTP status: 200
- [2024-11-05 16:11:43 in 2.10s]: IP: 176.96.139.65 / OK / HTTP status: 200