rama3.jp — Rama3
Details
up since 2024-12-04 00:31 (82.7 days ago)
- Uptime: 99.83%
- Users: 1 (1 active this month, 1 active last six months)
- Posts: 2606
- Posts per user: 2606.00
- Peers: 4810
- Version: mastodon 4.3.3
- Registrations: Invite
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2025-02-22 18:44 — 2025-02-24 15:20
users: 1 (0.00/day)
min/max/avg/stddev: 1 / 1 / 1.00 / 0.00
⋯ ⋯posts: 2606 (2.48/day)
min/max/avg/stddev: 2602 / 2606 / 2604.20 / 1.47
peers: 4810 (6.81/day)
min/max/avg/stddev: 4799 / 4810 / 4803.80 / 5.08
response_time: 3.45 (-2.22/day)
min/max/avg/stddev: 2 / 7 / 4.36 / 1.48
Crawling Info
First contact: 2022-12-25 (26.0 months ago)
Last successful contact: 2025-02-24 (109.3 minutes ago)
Latest attempt: 2025-02-24 (52.4 minutes ago)
Contact: 45853 successful, 3174 failed.
Average fetch time: 4.36s
Next attempt scheduled for 23.8 minutes ago.
Found through terere.social (up)
IP address: 139.99.39.10 (and 195 others, including: tanuki.hostdon.ne.jp (up), susunu.hostdon.ne.jp (up), nonentity.fedicity.net (up), petronel.info (up), fieldnotes.social (up), hilo00.hostdon.ne.jp (up), mmasuda.hostdon.ne.jp (up), harukakanata.net (up), matsudon.hostdon.ne.jp (down), tarasupadon.com (up))
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2025-02-24 15:20:06 in 0.00s]: IP: 139.99.39.10 / Error: http / HTTP status: -1
- [2025-02-24 00:49:26 in 0.00s]: IP: 139.99.39.10 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2025-02-24 14:23:14 in 0.23s]: IP: 139.99.39.10 / OK / HTTP status: 200
- [2025-02-24 13:24:38 in 0.21s]: IP: 139.99.39.10 / OK / HTTP status: 200
- [2025-02-24 12:32:36 in 0.25s]: IP: 139.99.39.10 / OK / HTTP status: 200
- [2025-02-24 11:36:24 in 0.25s]: IP: 139.99.39.10 / OK / HTTP status: 200
- [2025-02-24 10:35:33 in 0.21s]: IP: 139.99.39.10 / OK / HTTP status: 200
- [2025-02-24 09:30:05 in 1.14s]: IP: 139.99.39.10 / OK / HTTP status: 200
- [2025-02-24 07:52:25 in 0.22s]: IP: 139.99.39.10 / OK / HTTP status: 200
- [2025-02-24 05:56:42 in 0.23s]: IP: 139.99.39.10 / OK / HTTP status: 200
- [2025-02-24 04:01:20 in 0.28s]: IP: 139.99.39.10 / OK / HTTP status: 200
- [2025-02-23 22:41:26 in 0.23s]: IP: 139.99.39.10 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2025-02-24 07:52:25 in 0.22s]: IP: 139.99.39.10 / OK / HTTP status: 200
- [2025-02-23 22:41:26 in 0.21s]: IP: 139.99.39.10 / OK / HTTP status: 200
- [2025-02-23 14:20:23 in 0.44s]: IP: 139.99.39.10 / OK / HTTP status: 200
- [2025-02-22 18:44:42 in 0.55s]: IP: 139.99.39.10 / OK / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2025-02-24 14:23:14 in 2.03s]: IP: 139.99.39.10 / OK / HTTP status: 200
- [2025-02-24 13:24:38 in 3.86s]: IP: 139.99.39.10 / OK / HTTP status: 200
- [2025-02-24 12:32:36 in 0.98s]: IP: 139.99.39.10 / OK / HTTP status: 200
- [2025-02-24 11:36:24 in 1.04s]: IP: 139.99.39.10 / OK / HTTP status: 200
- [2025-02-24 10:35:33 in 1.06s]: IP: 139.99.39.10 / OK / HTTP status: 200
- [2025-02-24 09:30:05 in 2.18s]: IP: 139.99.39.10 / OK / HTTP status: 200
- [2025-02-24 07:52:25 in 0.94s]: IP: 139.99.39.10 / OK / HTTP status: 200
- [2025-02-24 05:56:42 in 0.92s]: IP: 139.99.39.10 / OK / HTTP status: 200
- [2025-02-24 04:01:20 in 0.97s]: IP: 139.99.39.10 / OK / HTTP status: 200
- [2025-02-23 22:41:26 in 0.99s]: IP: 139.99.39.10 / OK / HTTP status: 200