rumohr.social — Rumohr Mastodon
Details
up since 2024-06-10 16:29 (25.1 days ago)
- Uptime: 99.97%
- Users: 1 (1 active this month, 1 active last six months)
- Posts: 0
- Posts per user: 0.00
- Peers: 502
- Version: mastodon 4.2.8
- Registrations: Invite
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-06-21 21:50 — 2024-07-05 19:33
users: 1 (0.00/day)
min/max/avg/stddev: 1 / 1 / 1.00 / 0.00
⋯ ⋯posts: 0 (0.00/day)
min/max/avg/stddev: 0 / 0 / 0.00 / 0.00
⋯ ⋯peers: 502 (7.76/day)
min/max/avg/stddev: 396 / 502 / 439.30 / 25.74
response_time: 1.618 (-0.15/day)
min/max/avg/stddev: 0 / 8 / 3.03 / 1.80
Crawling Info
First contact: 2024-05-21 (45.6 days ago)
Last successful contact: 2024-07-05 (150.9 seconds ago)
Contact: 5042 successful, 456 failed.
Average fetch time: 3.04s
Next attempt scheduled for 13.6 minutes from now.
Found through hallole.eu (up)
IP address: 216.225.203.217
Staff
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-07-05 19:16:18 in 0.00s]: IP: 216.225.203.217 / Error: http / HTTP status: -1
- [2024-07-05 16:41:21 in 0.00s]: IP: 216.225.203.217 / Error: http / HTTP status: -1
- [2024-07-05 14:58:43 in 0.00s]: IP: 216.225.203.217 / Error: http / HTTP status: -1
- [2024-07-05 14:23:48 in 0.00s]: IP: 216.225.203.217 / Error: http / HTTP status: -1
- [2024-07-05 11:32:15 in 0.00s]: IP: 216.225.203.217 / Error: http / HTTP status: -1
- [2024-07-05 10:58:45 in 0.00s]: IP: 216.225.203.217 / Error: http / HTTP status: -1
- [2024-07-05 08:23:56 in 0.00s]: IP: 216.225.203.217 / Error: http / HTTP status: -1
- [2024-07-05 08:06:32 in 0.00s]: IP: 216.225.203.217 / Error: http / HTTP status: -1
- [2024-07-05 06:24:37 in 0.00s]: IP: 216.225.203.217 / Error: http / HTTP status: -1
- [2024-07-05 05:32:54 in 0.00s]: IP: 216.225.203.217 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-07-05 19:33:25 in 0.10s]: IP: 216.225.203.217 / OK / HTTP status: 200
- [2024-07-05 18:59:12 in 0.45s]: IP: 216.225.203.217 / OK / HTTP status: 200
- [2024-07-05 18:42:17 in 0.11s]: IP: 216.225.203.217 / OK / HTTP status: 200
- [2024-07-05 18:24:29 in 0.11s]: IP: 216.225.203.217 / OK / HTTP status: 200
- [2024-07-05 18:05:48 in 0.09s]: IP: 216.225.203.217 / OK / HTTP status: 200
- [2024-07-05 17:48:27 in 0.72s]: IP: 216.225.203.217 / OK / HTTP status: 200
- [2024-07-05 17:31:27 in 0.10s]: IP: 216.225.203.217 / OK / HTTP status: 200
- [2024-07-05 17:14:28 in 0.48s]: IP: 216.225.203.217 / OK / HTTP status: 200
- [2024-07-05 16:57:44 in 0.10s]: IP: 216.225.203.217 / OK / HTTP status: 200
- [2024-07-05 16:24:59 in 0.09s]: IP: 216.225.203.217 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-07-05 17:31:27 in 0.08s]: IP: 216.225.203.217 / OK / HTTP status: 200
- [2024-07-05 06:41:37 in 0.10s]: IP: 216.225.203.217 / OK / HTTP status: 200
- [2024-07-04 20:07:06 in 0.08s]: IP: 216.225.203.217 / OK / HTTP status: 200
- [2024-07-04 10:34:35 in 0.08s]: IP: 216.225.203.217 / OK / HTTP status: 200
- [2024-07-04 02:24:57 in 0.08s]: IP: 216.225.203.217 / OK / HTTP status: 200
- [2024-07-03 18:22:12 in 0.08s]: IP: 216.225.203.217 / OK / HTTP status: 200
- [2024-07-03 10:14:30 in 0.08s]: IP: 216.225.203.217 / OK / HTTP status: 200
- [2024-07-03 01:32:31 in 0.10s]: IP: 216.225.203.217 / OK / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2024-07-05 19:33:25 in 0.37s]: IP: 216.225.203.217 / OK / HTTP status: 200
- [2024-07-05 18:59:12 in 2.50s]: IP: 216.225.203.217 / OK / HTTP status: 200
- [2024-07-05 18:42:17 in 0.53s]: IP: 216.225.203.217 / OK / HTTP status: 200
- [2024-07-05 18:24:29 in 0.59s]: IP: 216.225.203.217 / OK / HTTP status: 200
- [2024-07-05 18:05:48 in 0.69s]: IP: 216.225.203.217 / OK / HTTP status: 200
- [2024-07-05 17:48:27 in 3.11s]: IP: 216.225.203.217 / OK / HTTP status: 200
- [2024-07-05 17:31:27 in 0.53s]: IP: 216.225.203.217 / OK / HTTP status: 200
- [2024-07-05 17:14:28 in 1.96s]: IP: 216.225.203.217 / OK / HTTP status: 200
- [2024-07-05 16:57:44 in 0.41s]: IP: 216.225.203.217 / OK / HTTP status: 200
- [2024-07-05 16:24:59 in 0.44s]: IP: 216.225.203.217 / OK / HTTP status: 200