leverkusen.collabfc.com — Leverkusen
Details
up since 2024-09-18 13:48 (26.6 hours ago)
- Uptime: 100.00%
- Users: 4 (2 active this month, 2 active last six months)
- Posts: 2
- Posts per user: 0.50
- Peers: 21
- Version: pleroma 2.6.50-888-g1d941583.main+soapbox
- Source code: https://gitlab.com/soapbox-pub/rebased
- Registrations: Approval Required
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-09-18 14:52 — 2024-09-19 16:13
users: 4 (0.00/day)
min/max/avg/stddev: 4 / 4 / 4.00 / 0.00
⋯ ⋯posts: 2 (1.83/day)
min/max/avg/stddev: 0 / 2 / 0.60 / 0.80
peers: 21 (14.68/day)
min/max/avg/stddev: 5 / 21 / 12.40 / 7.09
response_time: 2.236 (-0.21/day)
min/max/avg/stddev: 0 / 2 / 1.78 / 0.93
Crawling Info
First contact: 2024-09-18 (26.6 hours ago)
Last successful contact: 2024-09-19 (10.3 minutes ago)
Contact: 149 successful, 28 failed.
Average fetch time: 1.78s
Next attempt scheduled for 4.7 minutes from now.
Found through augsburg.collabfc.com (up)
IP address: 172.67.165.136 (and 18 others, including: frankfurt.collabfc.com (up), dortmund.collabfc.com (up), leipzig.collabfc.com (up), stuttgart.collabfc.com (up), sheffieldutd.collabfc.com (up), germanrelay.collabfc.com (up), fulham.collabfc.com (up), werder.collabfc.com (up), hoffenheim.collabfc.com (up), luton.collabfc.com (up))
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-09-19 13:20:50 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- [2024-09-19 12:50:00 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 12:34:29 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- [2024-09-19 12:18:58 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 10:14:42 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 09:59:12 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- [2024-09-19 09:43:37 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 09:28:19 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- [2024-09-19 08:10:49 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 07:08:42 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-09-19 16:13:31 in 0.20s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 15:57:54 in 0.47s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 15:41:32 in 0.21s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 15:25:52 in 0.20s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 15:10:17 in 0.20s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 14:54:30 in 0.20s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 14:38:52 in 0.20s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 14:23:17 in 0.21s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 14:07:42 in 0.20s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 13:52:07 in 0.23s]: IP: 104.21.50.187 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-09-19 10:30:09 in 0.19s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 02:29:19 in 0.19s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-18 16:57:22 in 0.25s]: IP: 172.67.165.136 / OK / HTTP status: 200
- /nodeinfo/2.1.json ₍⇗₎
- [2024-09-19 16:13:31 in 0.79s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 15:57:54 in 0.72s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 15:41:32 in 0.79s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 15:25:52 in 0.74s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 15:10:17 in 1.00s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 14:54:30 in 0.73s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 14:38:51 in 0.74s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 14:23:17 in 0.72s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 14:07:42 in 0.75s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 13:52:07 in 0.72s]: IP: 104.21.50.187 / OK / HTTP status: 200