pleroma.polyserv.xyz — Pleroma
Pleroma: An efficient and flexible fediverse server
Details
up since 2024-07-03 00:03 (12.0 hours ago)
- Uptime: 99.53%
- Users: 10 (1 active this month, 3 active last six months)
- Posts: 39
- Posts per user: 3.90
- Peers: 4343
- Version: pleroma 2.5.0
- Source code: https://git.pleroma.social/pleroma/pleroma
- Registrations: Invite
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-06-20 11:10 — 2024-07-03 11:16
users: 10 (0.00/day)
min/max/avg/stddev: 10 / 10 / 10.00 / 0.00
⋯ ⋯posts: 39 (0.00/day)
min/max/avg/stddev: 39 / 39 / 39.00 / 0.00
⋯ ⋯peers: 4343 (0.96/day)
min/max/avg/stddev: 4330 / 4343 / 4336.50 / 4.03
⋯response_time: 1.532 (-6.87/day)
min/max/avg/stddev: 1 / 95 / 37.54 / 31.17
Crawling Info
First contact: 2023-02-01 (17.0 months ago)
Last successful contact: 2024-07-03 (159.7 minutes ago)
Latest attempt: 2024-07-03 (48.3 minutes ago)
Contact: 14504 successful, 2173 failed.
Average fetch time: 37.54s
Next attempt scheduled for 6.7 minutes from now.
Found through social.domov.de (up)
IP address: 92.124.132.108
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-07-03 11:16:51 in 0.00s]: IP: 92.124.132.108 / Error: http / HTTP status: -1
- [2024-07-03 10:21:29 in 0.00s]: IP: 92.124.132.108 / Error: http / HTTP status: -1
- [2024-07-03 04:43:18 in 0.00s]: IP: 92.124.132.108 / Error: http / HTTP status: -1
- [2024-07-02 23:07:16 in 0.00s]: IP: 92.124.132.108 / Error: http / HTTP status: -1
- [2024-07-02 22:09:57 in 0.00s]: IP: 92.124.132.108 / Error: http / HTTP status: -1
- [2024-07-02 21:12:43 in 0.00s]: IP: 92.124.132.108 / Error: http / HTTP status: -1
- [2024-07-02 20:16:24 in 0.00s]: IP: 92.124.132.108 / Error: http / HTTP status: -1
- [2024-07-02 19:19:40 in 0.00s]: IP: 92.124.132.108 / Error: http / HTTP status: -1
- [2024-07-02 18:21:41 in 0.00s]: IP: 92.124.132.108 / Error: http / HTTP status: -1
- [2024-07-02 16:27:00 in 0.00s]: IP: 92.124.132.108 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-07-03 09:25:25 in 0.23s]: IP: 92.124.132.108 / OK / HTTP status: 200
- [2024-07-03 08:28:47 in 0.22s]: IP: 92.124.132.108 / OK / HTTP status: 200
- [2024-07-03 07:31:49 in 0.22s]: IP: 92.124.132.108 / OK / HTTP status: 200
- [2024-07-03 06:35:58 in 0.22s]: IP: 92.124.132.108 / OK / HTTP status: 200
- [2024-07-03 05:39:33 in 0.23s]: IP: 92.124.132.108 / OK / HTTP status: 200
- [2024-07-03 03:46:22 in 0.23s]: IP: 92.124.132.108 / OK / HTTP status: 200
- [2024-07-03 02:50:11 in 0.23s]: IP: 92.124.132.108 / OK / HTTP status: 200
- [2024-07-03 01:54:30 in 0.22s]: IP: 92.124.132.108 / OK / HTTP status: 200
- [2024-07-03 00:58:49 in 0.23s]: IP: 92.124.132.108 / OK / HTTP status: 200
- [2024-07-03 00:03:46 in 0.22s]: IP: 92.124.132.108 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-07-01 23:45:12 in 0.23s]: IP: 92.124.132.108 / OK / HTTP status: 200
- /nodeinfo/2.1.json ₍⇗₎
- [2024-07-03 09:25:25 in 1.36s]: IP: 92.124.132.108 / OK / HTTP status: 200
- [2024-07-03 08:28:47 in 1.21s]: IP: 92.124.132.108 / OK / HTTP status: 200
- [2024-07-03 07:31:49 in 1.43s]: IP: 92.124.132.108 / OK / HTTP status: 200
- [2024-07-03 06:35:58 in 1.31s]: IP: 92.124.132.108 / OK / HTTP status: 200
- [2024-07-03 05:39:33 in 0.92s]: IP: 92.124.132.108 / OK / HTTP status: 200
- [2024-07-03 03:46:22 in 1.45s]: IP: 92.124.132.108 / OK / HTTP status: 200
- [2024-07-03 02:50:11 in 1.30s]: IP: 92.124.132.108 / OK / HTTP status: 200
- [2024-07-03 01:54:30 in 1.68s]: IP: 92.124.132.108 / OK / HTTP status: 200
- [2024-07-03 00:58:49 in 1.23s]: IP: 92.124.132.108 / OK / HTTP status: 200
- [2024-07-03 00:03:46 in 1.06s]: IP: 92.124.132.108 / OK / HTTP status: 200