kiel.collabfc.com — Kiel
Details
up since 2024-09-18 13:48 (26.4 hours ago)
- Uptime: 100.00%
- Users: 4 (2 active this month, 2 active last six months)
- Posts: 0
- Posts per user: 0.00
- Peers: 10
- 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:53 — 2024-09-19 16:12
users: 4 (0.00/day)
min/max/avg/stddev: 4 / 4 / 4.00 / 0.00
⋯ ⋯posts: 0 (0.00/day)
min/max/avg/stddev: 0 / 0 / 0.00 / 0.00
⋯ ⋯peers: 10 (5.70/day)
min/max/avg/stddev: 5 / 10 / 7.80 / 1.72
response_time: 4.123 (1.46/day)
min/max/avg/stddev: 1 / 4 / 2.44 / 0.96
Crawling Info
First contact: 2024-09-18 (26.4 hours ago)
Last successful contact: 2024-09-19 (116.6 seconds ago)
Contact: 159 successful, 24 failed.
Average fetch time: 2.44s
Next attempt scheduled for 13.1 minutes from now.
Found through augsburg.collabfc.com (up)
IP address: 104.21.50.187 (and 27 others, including: dortmund.collabfc.com (up), leipzig.collabfc.com (up), wolfsburg.collabfc.com (up), crystalpalace.collabfc.com (up), gladbach.collabfc.com (up), heidenheim.collabfc.com (up), sheffieldutd.collabfc.com (up), stpauli.collabfc.com (up), spurs.collabfc.com (up), augsburg.collabfc.com (up))
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-09-19 14:30:19 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- [2024-09-19 14:14:12 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 13:12:17 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 12:25:34 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- [2024-09-19 10:21:36 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 09:35:15 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- [2024-09-19 08:16:51 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 06:10:22 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- [2024-09-19 04:21:53 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 04:06:27 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-09-19 16:12:34 in 0.21s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 15:55:02 in 0.21s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 15:32:50 in 0.20s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 15:16:54 in 0.20s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 15:01:42 in 0.21s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 14:45:48 in 0.21s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 13:58:55 in 0.20s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 13:43:23 in 0.20s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 13:27:45 in 0.20s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 12:56:43 in 0.20s]: IP: 104.21.50.187 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-09-19 08:47:40 in 0.21s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-18 23:31:05 in 0.19s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-18 14:20:40 in 0.24s]: IP: 172.67.165.136 / OK / HTTP status: 200
- /nodeinfo/2.1.json ₍⇗₎
- [2024-09-19 16:12:34 in 0.74s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 15:55:02 in 0.76s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 15:32:50 in 0.73s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 15:16:54 in 0.71s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 15:01:42 in 0.80s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 14:45:48 in 0.71s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 13:58:55 in 0.73s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 13:43:23 in 0.73s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 13:27:45 in 0.71s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 12:56:43 in 0.74s]: IP: 104.21.50.187 / OK / HTTP status: 200