rmaestas.social — R. Maestas Social
Details
up since 2024-10-18 05:22 (18.0 days ago)
- Uptime: 99.05%
- Users: 1 (1 active this month, 1 active last six months)
- Posts: 75
- Posts per user: 75.00
- Peers: 4737
- Version: mastodon 4.3.0
- Registrations: Invite
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-10-22 07:18 — 2024-11-05 04:05
users: 1 (0.00/day)
min/max/avg/stddev: 1 / 1 / 1.00 / 0.00
⋯ ⋯posts: 75 (0.07/day)
min/max/avg/stddev: 74 / 75 / 74.31 / 0.46
peers: 4737 (3.82/day)
min/max/avg/stddev: 4683 / 4737 / 4709.36 / 14.52
response_time: 12.058 (0.52/day)
min/max/avg/stddev: 0 / 108 / 41.97 / 35.33
Crawling Info
First contact: 2024-04-02 (7.1 months ago)
Last successful contact: 2024-11-05 (21.8 minutes ago)
Contact: 5933 successful, 2187 failed.
Average fetch time: 41.97s
Next attempt scheduled for 46.2 minutes from now.
Found through social.kernel.org (up)
IP address: 98.53.170.209 (and 2 others: maestas.photos (down), maestas.us (up))
Staff
An independent business management and IT consultant who harmonizes IT departments and business operations, helping clients become more competitive, efficient, and sustainable.
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-11-05 02:56:59 in 0.00s]: IP: 98.53.170.209 / Error: http / HTTP status: -1
- [2024-11-05 00:38:14 in 0.00s]: IP: 98.53.170.209 / Error: http / HTTP status: -1
- [2024-11-04 23:29:02 in 0.00s]: IP: 98.53.170.209 / Error: http / HTTP status: -1
- [2024-11-04 22:19:58 in 0.00s]: IP: 98.53.170.209 / Error: http / HTTP status: -1
- [2024-11-04 20:01:47 in 0.00s]: IP: 98.53.170.209 / Error: http / HTTP status: -1
- [2024-11-04 18:50:34 in 0.00s]: IP: 98.53.170.209 / Error: http / HTTP status: -1
- [2024-11-04 16:22:25 in 0.00s]: IP: 98.53.170.209 / Error: http / HTTP status: -1
- [2024-11-04 15:11:28 in 0.00s]: IP: 98.53.170.209 / Error: http / HTTP status: -1
- [2024-11-04 14:01:29 in 0.00s]: IP: 98.53.170.209 / Error: http / HTTP status: -1
- [2024-11-04 12:50:53 in 0.00s]: IP: 98.53.170.209 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-11-05 04:05:50 in 0.08s]: IP: 98.53.170.209 / OK / HTTP status: 200
- [2024-11-05 01:48:06 in 44.46s]: IP: 98.53.170.209 / OK / HTTP status: 200
- [2024-11-04 21:11:08 in 0.11s]: IP: 98.53.170.209 / OK / HTTP status: 200
- [2024-11-04 17:32:56 in 0.10s]: IP: 98.53.170.209 / OK / HTTP status: 200
- [2024-11-04 11:41:27 in 0.09s]: IP: 98.53.170.209 / OK / HTTP status: 200
- [2024-11-04 10:26:45 in 0.09s]: IP: 98.53.170.209 / OK / HTTP status: 200
- [2024-11-04 06:55:49 in 0.10s]: IP: 98.53.170.209 / OK / HTTP status: 200
- [2024-11-04 05:46:08 in 0.10s]: IP: 98.53.170.209 / OK / HTTP status: 200
- [2024-11-04 02:13:39 in 0.09s]: IP: 98.53.170.209 / OK / HTTP status: 200
- [2024-11-03 20:18:55 in 0.13s]: IP: 98.53.170.209 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-11-04 21:11:08 in 0.06s]: IP: 98.53.170.209 / OK / HTTP status: 200
- [2024-11-02 13:46:44 in 0.08s]: IP: 98.53.170.209 / OK / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2024-11-05 04:05:50 in 0.41s]: IP: 98.53.170.209 / OK / HTTP status: 200
- [2024-11-05 01:48:06 in 0.28s]: IP: 98.53.170.209 / OK / HTTP status: 200
- [2024-11-04 21:11:08 in 0.33s]: IP: 98.53.170.209 / OK / HTTP status: 200
- [2024-11-04 17:32:56 in 0.43s]: IP: 98.53.170.209 / OK / HTTP status: 200
- [2024-11-04 11:41:27 in 0.41s]: IP: 98.53.170.209 / OK / HTTP status: 200
- [2024-11-04 10:26:45 in 0.31s]: IP: 98.53.170.209 / OK / HTTP status: 200
- [2024-11-04 06:55:49 in 0.41s]: IP: 98.53.170.209 / OK / HTTP status: 200
- [2024-11-04 05:46:08 in 0.30s]: IP: 98.53.170.209 / OK / HTTP status: 200
- [2024-11-04 02:13:39 in 0.43s]: IP: 98.53.170.209 / OK / HTTP status: 200
- [2024-11-03 20:18:55 in 0.35s]: IP: 98.53.170.209 / OK / HTTP status: 200