social.aylett.co.uk — Aylett
Pleroma: An efficient and flexible fediverse server
Details
up since 2024-06-10 16:45 (20.8 days ago)
- Uptime: 71.52%
- Users: 1 (0 active this month, 0 active last six months)
- Posts: 94
- Posts per user: 94.00
- Peers: 3962
- Version: pleroma 2.4.53-906-gf40ccce7-develop
- Source code: https://git.pleroma.social/pleroma/pleroma
- Registrations: Invite
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-06-17 17:49 — 2024-07-01 10:55
users: 1 (0.00/day)
min/max/avg/stddev: 1 / 1 / 1.00 / 0.00
⋯ —posts: 94 (0.00/day)
min/max/avg/stddev: 94 / 94 / 94.00 / 0.00
⋯ —peers: 3962 (0.10/day)
min/max/avg/stddev: 3960 / 3962 / 3961.00 / 0.82
⋯response_time: 7.456 (0.22/day)
min/max/avg/stddev: 2 / 7 / 4.24 / 2.28
Crawling Info
First contact: 2023-01-09 (17.7 months ago)
Last successful contact: 2024-07-01 (50.6 minutes ago)
Latest attempt: 2024-07-01 (21.6 minutes ago)
Contact: 17502 successful, 1315 failed.
Average fetch time: 4.24s
Next attempt scheduled for 47.1 seconds ago.
Found through libranet.de (down)
IP address: 168.220.83.133
Staff
andrew@social.aylett.co.uk
Christian software engineer from Edinburgh, UK.
If you're interested in anything I've been posting about, or technology in general, come and talk to me :).
Christian software engineer from Edinburgh, UK.
If you're interested in anything I've been posting about, or technology in general, come and talk to me :).
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-07-01 10:55:40 in 0.00s]: IP: 168.220.83.133 / Error: http / HTTP status: -1
- [2024-07-01 09:16:56 in 0.00s]: IP: 168.220.83.133 / Error: http / HTTP status: -1
- [2024-07-01 05:59:12 in 0.00s]: IP: 168.220.83.133 / Error: http / HTTP status: -1
- [2024-07-01 02:24:24 in 0.00s]: IP: 168.220.83.133 / Error: http / HTTP status: -1
- [2024-07-01 00:00:40 in 0.00s]: IP: 168.220.83.133 / Error: http / HTTP status: -1
- [2024-06-30 23:27:44 in 0.00s]: IP: 168.220.83.133 / Error: http / HTTP status: -1
- [2024-06-30 23:11:00 in 0.00s]: IP: 168.220.83.133 / Error: http / HTTP status: -1
- [2024-06-30 22:36:36 in 0.00s]: IP: 168.220.83.133 / Error: http / HTTP status: -1
- [2024-06-30 19:21:01 in 0.00s]: IP: 168.220.83.133 / Error: http / HTTP status: -1
- [2024-06-30 07:21:03 in 0.00s]: IP: 168.220.83.133 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-07-01 10:26:39 in 0.69s]: IP: 168.220.83.133 / OK / HTTP status: 200
- [2024-07-01 10:10:25 in 0.36s]: IP: 168.220.83.133 / OK / HTTP status: 200
- [2024-07-01 09:54:09 in 0.15s]: IP: 168.220.83.133 / OK / HTTP status: 200
- [2024-07-01 09:35:22 in 0.66s]: IP: 168.220.83.133 / OK / HTTP status: 200
- [2024-07-01 08:57:05 in 0.15s]: IP: 168.220.83.133 / OK / HTTP status: 200
- [2024-07-01 08:39:29 in 0.16s]: IP: 168.220.83.133 / OK / HTTP status: 200
- [2024-07-01 08:19:45 in 0.14s]: IP: 168.220.83.133 / OK / HTTP status: 200
- [2024-07-01 07:56:50 in 0.40s]: IP: 168.220.83.133 / OK / HTTP status: 200
- [2024-07-01 07:33:20 in 0.68s]: IP: 168.220.83.133 / OK / HTTP status: 200
- [2024-07-01 07:08:50 in 4.27s]: IP: 168.220.83.133 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-07-01 05:25:12 in 0.15s]: IP: 168.220.83.133 / OK / HTTP status: 200
- [2024-06-30 20:58:21 in 0.15s]: IP: 168.220.83.133 / OK / HTTP status: 200
- [2024-06-30 12:02:11 in 0.17s]: IP: 168.220.83.133 / OK / HTTP status: 200
- [2024-06-30 02:18:03 in 0.28s]: IP: 168.220.83.133 / OK / HTTP status: 200
- [2024-06-29 17:00:50 in 0.15s]: IP: 168.220.83.133 / OK / HTTP status: 200
- [2024-06-29 08:37:18 in 0.80s]: IP: 168.220.83.133 / OK / HTTP status: 200
- [2024-06-29 00:30:32 in 0.15s]: IP: 168.220.83.133 / OK / HTTP status: 200
- [2024-06-28 16:15:21 in 0.15s]: IP: 168.220.83.133 / OK / HTTP status: 200
- /nodeinfo/2.1.json ₍⇗₎
- [2024-07-01 10:26:39 in 12.73s]: IP: 168.220.83.133 / OK / HTTP status: 200
- [2024-07-01 10:10:25 in 1.10s]: IP: 168.220.83.133 / OK / HTTP status: 200
- [2024-07-01 09:54:09 in 0.50s]: IP: 168.220.83.133 / OK / HTTP status: 200
- [2024-07-01 09:35:22 in 3.12s]: IP: 168.220.83.133 / OK / HTTP status: 200
- [2024-07-01 08:57:05 in 0.47s]: IP: 168.220.83.133 / OK / HTTP status: 200
- [2024-07-01 08:39:29 in 0.52s]: IP: 168.220.83.133 / OK / HTTP status: 200
- [2024-07-01 08:19:45 in 0.47s]: IP: 168.220.83.133 / OK / HTTP status: 200
- [2024-07-01 07:56:49 in 1.44s]: IP: 168.220.83.133 / OK / HTTP status: 200
- [2024-07-01 07:33:20 in 2.22s]: IP: 168.220.83.133 / OK / HTTP status: 200
- [2024-07-01 07:08:50 in 2.12s]: IP: 168.220.83.133 / OK / HTTP status: 200