pleroma.rooset.org
Pleroma: An efficient and flexible fediverse server
Details
up since 2024-10-28 20:52 (8.3 days ago)
- Uptime: 99.95%
- Users: 2 (0 active this month, 2 active last six months)
- Posts: 21
- Posts per user: 10.50
- Peers: 2
- Version: pleroma 2.7.0-70-g36d469cf
- Source code: https://git.pleroma.social/pleroma/pleroma
- Registrations: Open
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-11-01 05:45 — 2024-11-06 02:45
users: 2 (0.00/day)
min/max/avg/stddev: 2 / 2 / 2.00 / 0.00
⋯ —posts: 21 (0.00/day)
min/max/avg/stddev: 21 / 21 / 21.00 / 0.00
⋯ —peers: 2 (0.00/day)
min/max/avg/stddev: 2 / 2 / 2.00 / 0.00
⋯ —response_time: 4.737 (-0.07/day)
min/max/avg/stddev: 4 / 6 / 5.57 / 0.92
Crawling Info
First contact: 2024-09-18 (49.1 days ago)
Last successful contact: 2024-11-06 (18.4 minutes ago)
Contact: 5364 successful, 851 failed.
Average fetch time: 5.57s
Next attempt scheduled for 11.9 minutes from now.
Found through activitypub.academy (up)
IP address: 209.38.30.110
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-11-06 01:47:45 in 0.00s]: IP: 209.38.30.110 / Error: http / HTTP status: -1
- [2024-11-05 19:05:42 in 0.00s]: IP: 209.38.30.110 / Error: http / HTTP status: -1
- [2024-11-05 17:38:31 in 0.00s]: IP: 209.38.30.110 / Error: http / HTTP status: -1
- [2024-11-05 15:06:55 in 0.00s]: IP: 209.38.30.110 / Error: http / HTTP status: -1
- [2024-11-05 12:42:19 in 0.00s]: IP: 209.38.30.110 / Error: http / HTTP status: -1
- [2024-11-05 12:14:24 in 0.00s]: IP: 209.38.30.110 / Error: http / HTTP status: -1
- [2024-11-05 07:40:21 in 0.00s]: IP: 209.38.30.110 / Error: http / HTTP status: -1
- [2024-11-05 07:12:34 in 0.00s]: IP: 209.38.30.110 / Error: http / HTTP status: -1
- [2024-11-05 04:36:57 in 0.00s]: IP: 209.38.30.110 / Error: http / HTTP status: -1
- [2024-11-05 03:42:36 in 0.00s]: IP: 209.38.30.110 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-11-06 02:45:26 in 0.60s]: IP: 209.38.30.110 / OK / HTTP status: 200
- [2024-11-06 02:16:46 in 0.18s]: IP: 209.38.30.110 / OK / HTTP status: 200
- [2024-11-06 01:15:29 in 0.76s]: IP: 209.38.30.110 / OK / HTTP status: 200
- [2024-11-06 00:43:34 in 0.53s]: IP: 209.38.30.110 / OK / HTTP status: 200
- [2024-11-06 00:12:29 in 0.63s]: IP: 209.38.30.110 / OK / HTTP status: 200
- [2024-11-05 23:43:31 in 0.19s]: IP: 209.38.30.110 / OK / HTTP status: 200
- [2024-11-05 23:14:44 in 0.18s]: IP: 209.38.30.110 / OK / HTTP status: 200
- [2024-11-05 22:45:04 in 0.18s]: IP: 209.38.30.110 / OK / HTTP status: 200
- [2024-11-05 22:14:37 in 0.18s]: IP: 209.38.30.110 / OK / HTTP status: 200
- [2024-11-05 21:42:58 in 0.19s]: IP: 209.38.30.110 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-11-06 02:45:26 in 0.53s]: IP: 209.38.30.110 / OK / HTTP status: 200
- [2024-11-05 14:36:18 in 0.17s]: IP: 209.38.30.110 / OK / HTTP status: 200
- [2024-11-05 05:35:25 in 0.61s]: IP: 209.38.30.110 / OK / HTTP status: 200
- [2024-11-04 18:37:49 in 0.18s]: IP: 209.38.30.110 / OK / HTTP status: 200
- [2024-11-04 10:07:08 in 0.69s]: IP: 209.38.30.110 / OK / HTTP status: 200
- [2024-11-03 20:50:05 in 0.17s]: IP: 209.38.30.110 / OK / HTTP status: 200
- [2024-11-03 10:29:22 in 0.61s]: IP: 209.38.30.110 / OK / HTTP status: 200
- /nodeinfo/2.1.json ₍⇗₎
- [2024-11-06 02:45:26 in 2.23s]: IP: 209.38.30.110 / OK / HTTP status: 200
- [2024-11-06 02:16:45 in 0.75s]: IP: 209.38.30.110 / OK / HTTP status: 200
- [2024-11-06 01:15:29 in 2.55s]: IP: 209.38.30.110 / OK / HTTP status: 200
- [2024-11-06 00:43:34 in 2.17s]: IP: 209.38.30.110 / OK / HTTP status: 200
- [2024-11-06 00:12:29 in 2.60s]: IP: 209.38.30.110 / OK / HTTP status: 200
- [2024-11-05 23:43:31 in 0.88s]: IP: 209.38.30.110 / OK / HTTP status: 200
- [2024-11-05 23:14:44 in 0.71s]: IP: 209.38.30.110 / OK / HTTP status: 200
- [2024-11-05 22:45:04 in 0.75s]: IP: 209.38.30.110 / OK / HTTP status: 200
- [2024-11-05 22:14:37 in 0.84s]: IP: 209.38.30.110 / OK / HTTP status: 200
- [2024-11-05 21:42:58 in 1.02s]: IP: 209.38.30.110 / OK / HTTP status: 200