freiburg.collabfc.com — Freiburg
Details
up since 2024-09-18 13:48 (26.7 hours ago)
- Uptime: 100.00%
- Users: 4 (2 active this month, 2 active last six months)
- Posts: 1
- Posts per user: 0.25
- 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:27
users: 4 (0.00/day)
min/max/avg/stddev: 4 / 4 / 4.00 / 0.00
⋯ —posts: 1 (5.38/day)
min/max/avg/stddev: 0 / 1 / 0.33 / 0.47
peers: 21 (86.13/day)
min/max/avg/stddev: 5 / 21 / 11.00 / 7.12
response_time: 2.245 (-2.20/day)
min/max/avg/stddev: 1 / 2 / 2.00 / 0.66
Crawling Info
First contact: 2024-09-18 (26.7 hours ago)
Last successful contact: 2024-09-19 (4.2 minutes ago)
Contact: 137 successful, 37 failed.
Average fetch time: 2.00s
Next attempt scheduled for 10.8 minutes from now.
Found through augsburg.collabfc.com (up)
IP address: 172.67.165.136 (and 24 others, including: dortmund.collabfc.com (up), leipzig.collabfc.com (up), wolfsburg.collabfc.com (up), kiel.collabfc.com (up), gladbach.collabfc.com (up), heidenheim.collabfc.com (up), sheffieldutd.collabfc.com (up), crystalpalace.collabfc.com (up), stpauli.collabfc.com (up), germanrelay.collabfc.com (up))
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-09-19 15:56:39 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 15:24:45 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- [2024-09-19 12:17:43 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 11:46:30 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 11:31:06 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- [2024-09-19 10:59:59 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 10:44:26 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 10:28:56 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- [2024-09-19 09:42:49 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- [2024-09-19 08:40:44 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-09-19 16:27:47 in 0.21s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 16:12:14 in 0.20s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 15:40:27 in 0.21s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 15:09:19 in 0.21s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 14:53:23 in 0.20s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 14:37:35 in 0.22s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 14:22:13 in 0.20s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 14:06:39 in 0.21s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 13:51:10 in 0.48s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 13:35:36 in 0.20s]: IP: 104.21.50.187 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-09-19 11:15:33 in 0.18s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 02:59:31 in 0.20s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-18 15:56:33 in 0.25s]: IP: 104.21.50.187 / OK / HTTP status: 200
- /nodeinfo/2.1.json ₍⇗₎
- [2024-09-19 16:27:47 in 0.72s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 16:12:14 in 0.73s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 15:40:27 in 0.72s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 15:09:19 in 0.81s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 14:53:23 in 0.74s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 14:37:35 in 0.81s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 14:22:13 in 0.73s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 14:06:39 in 0.72s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 13:51:10 in 0.73s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 13:35:36 in 0.75s]: IP: 104.21.50.187 / OK / HTTP status: 200