social.dilavni.com — Dilavni Social
Dilavni Social
Details
up since 2024-07-01 16:00 (3.7 hours ago)
- Uptime: 81.14%
- Users: 9
- Posts: 37
- Posts per user: 4.11
- Peers: 563
- Version: pleroma 2.4.4
- Source code: https://git.pleroma.social/pleroma/pleroma
- Registrations: Open
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-06-24 11:28 — 2024-07-01 19:36
users: 9 (0.00/day)
min/max/avg/stddev: 9 / 9 / 9.00 / 0.00
⋯ —posts: 37 (0.01/day)
min/max/avg/stddev: 35 / 37 / 36.50 / 0.87
peers: 563 (0.22/day)
min/max/avg/stddev: 502 / 563 / 547.50 / 26.27
response_time: 2.921 (0.01/day)
min/max/avg/stddev: 0 / 4 / 3.15 / 1.72
Crawling Info
First contact: 2022-04-27 (26.1 months ago)
Last successful contact: 2024-07-01 (7.0 minutes ago)
Contact: 22654 successful, 9416 failed.
Average fetch time: 3.15s
Next attempt scheduled for 9.2 minutes from now.
Found through fedi.absturztau.be (up)
IP address: 104.21.55.32
Staff
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-07-01 19:18:09 in 1.63s]: IP: 104.21.55.32 / Error: http / HTTP status: 403
- [2024-07-01 18:41:51 in 2.16s]: IP: 104.21.55.32 / Error: http / HTTP status: 403
- [2024-07-01 17:27:01 in 0.00s]: IP: 104.21.55.32 / Error: http / HTTP status: -1
- [2024-07-01 17:04:35 in 3.82s]: IP: 172.67.170.88 / Error: http / HTTP status: 403
- [2024-07-01 16:17:32 in 1.87s]: IP: 104.21.55.32 / Error: http / HTTP status: 403
- [2024-07-01 15:44:06 in 0.83s]: IP: 104.21.55.32 / Error: http / HTTP status: 403
- [2024-07-01 15:27:05 in 0.00s]: IP: 104.21.55.32 / Error: http / HTTP status: -1
- [2024-07-01 15:10:01 in 0.00s]: IP: 172.67.170.88 / Error: http / HTTP status: -1
- [2024-07-01 14:49:36 in 2.07s]: IP: 104.21.55.32 / Error: http / HTTP status: 403
- [2024-07-01 14:29:34 in 2.48s]: IP: 172.67.170.88 / Error: http / HTTP status: 403
- /api/v1/instance ₍⇗₎
- [2024-07-01 19:36:01 in 0.19s]: IP: 104.21.55.32 / OK / HTTP status: 200
- [2024-07-01 19:00:09 in 0.18s]: IP: 104.21.55.32 / OK / HTTP status: 200
- [2024-07-01 18:24:21 in 0.19s]: IP: 172.67.170.88 / OK / HTTP status: 200
- [2024-07-01 18:06:40 in 0.18s]: IP: 104.21.55.32 / OK / HTTP status: 200
- [2024-07-01 17:47:08 in 0.17s]: IP: 104.21.55.32 / OK / HTTP status: 200
- [2024-07-01 16:42:40 in 0.18s]: IP: 104.21.55.32 / OK / HTTP status: 200
- [2024-07-01 16:00:25 in 0.18s]: IP: 172.67.170.88 / OK / HTTP status: 200
- [2024-07-01 13:54:40 in 0.18s]: IP: 172.67.170.88 / OK / HTTP status: 200
- [2024-07-01 13:17:47 in 0.19s]: IP: 104.21.55.32 / OK / HTTP status: 200
- [2024-07-01 12:59:41 in 0.18s]: IP: 172.67.170.88 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-07-01 16:42:40 in 0.18s]: IP: 104.21.55.32 / OK / HTTP status: 200
- [2024-07-01 08:40:00 in 0.18s]: IP: 172.67.170.88 / OK / HTTP status: 200
- [2024-06-30 22:22:38 in 0.18s]: IP: 172.67.170.88 / OK / HTTP status: 200
- [2024-06-30 12:13:56 in 0.17s]: IP: 104.21.55.32 / OK / HTTP status: 200
- [2024-06-30 01:53:28 in 0.66s]: IP: 104.21.55.32 / OK / HTTP status: 200
- [2024-06-29 17:47:10 in 0.18s]: IP: 172.67.170.88 / OK / HTTP status: 200
- [2024-06-29 09:37:51 in 0.17s]: IP: 104.21.55.32 / OK / HTTP status: 200
- [2024-06-29 00:10:00 in 0.17s]: IP: 172.67.170.88 / OK / HTTP status: 200
- /nodeinfo/2.1.json ₍⇗₎
- [2024-07-01 19:36:01 in 0.84s]: IP: 104.21.55.32 / OK / HTTP status: 200
- [2024-07-01 19:00:09 in 0.91s]: IP: 104.21.55.32 / OK / HTTP status: 200
- [2024-07-01 18:24:21 in 0.69s]: IP: 172.67.170.88 / OK / HTTP status: 200
- [2024-07-01 18:06:40 in 0.84s]: IP: 104.21.55.32 / OK / HTTP status: 200
- [2024-07-01 17:47:08 in 0.77s]: IP: 104.21.55.32 / OK / HTTP status: 200
- [2024-07-01 16:42:40 in 0.72s]: IP: 104.21.55.32 / OK / HTTP status: 200
- [2024-07-01 16:00:25 in 0.76s]: IP: 172.67.170.88 / OK / HTTP status: 200
- [2024-07-01 13:54:39 in 0.69s]: IP: 172.67.170.88 / OK / HTTP status: 200
- [2024-07-01 13:17:47 in 0.69s]: IP: 104.21.55.32 / OK / HTTP status: 200
- [2024-07-01 12:59:41 in 0.73s]: IP: 172.67.170.88 / OK / HTTP status: 200