bochum.collabfc.com — Bochum
Details
up since 2024-09-18 13:48 (26.5 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 15:19 — 2024-09-19 16:14
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.72/day)
min/max/avg/stddev: 5 / 10 / 7.80 / 1.72
response_time: 2.843 (1.42/day)
min/max/avg/stddev: 0 / 2 / 1.69 / 0.87
Crawling Info
First contact: 2024-09-18 (26.5 hours ago)
Last successful contact: 2024-09-19 (70.8 seconds ago)
Contact: 140 successful, 32 failed.
Average fetch time: 1.69s
Next attempt scheduled for 13.8 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), kiel.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))
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-09-19 14:55:16 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- [2024-09-19 14:39:44 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 13:06:11 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- [2024-09-19 12:50:37 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- [2024-09-19 12:19:33 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- [2024-09-19 11:17:26 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- [2024-09-19 11:02:04 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 10:15:26 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- [2024-09-19 09:28:56 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 09:13:25 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-09-19 16:14:03 in 0.21s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 15:58:28 in 0.21s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 15:42:16 in 0.19s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 15:26:29 in 0.21s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 15:10:59 in 0.20s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 14:24:11 in 0.21s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 14:08:26 in 0.20s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 13:53:02 in 0.21s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 13:37:19 in 0.20s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 13:21:46 in 0.20s]: IP: 104.21.50.187 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-09-19 15:10:59 in 0.45s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 06:54:08 in 0.19s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-18 22:27:27 in 0.20s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-18 13:48:15 in 0.22s]: IP: 104.21.50.187 / OK / HTTP status: 200
- /nodeinfo/2.1.json ₍⇗₎
- [2024-09-19 16:14:03 in 1.13s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 15:58:28 in 0.73s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 15:42:16 in 0.74s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 15:26:28 in 0.71s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 15:10:59 in 0.76s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 14:24:11 in 0.76s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 14:08:26 in 0.73s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 13:53:02 in 0.80s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 13:37:19 in 0.71s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 13:21:46 in 0.73s]: IP: 104.21.50.187 / OK / HTTP status: 200