gladbach.collabfc.com — Gladbach
Details
up since 2024-09-18 13:48 (26.9 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 13:48 — 2024-09-19 16:41
users: 4 (0.00/day)
min/max/avg/stddev: 4 / 4 / 4.00 / 0.00
⋯ ⋯posts: 1 (1.16/day)
min/max/avg/stddev: 0 / 1 / 0.20 / 0.40
peers: 21 (18.62/day)
min/max/avg/stddev: 5 / 21 / 10.00 / 5.66
response_time: 2.086 (2.31/day)
min/max/avg/stddev: 0 / 2 / 1.24 / 0.80
Crawling Info
First contact: 2024-09-18 (26.9 hours ago)
Last successful contact: 2024-09-19 (153.8 seconds ago)
Contact: 147 successful, 33 failed.
Average fetch time: 1.25s
Next attempt scheduled for 12.4 minutes from now.
Found through augsburg.collabfc.com (up)
IP address: 104.21.50.187 (and 15 others, including: wolfsburg.collabfc.com (up), crystalpalace.collabfc.com (up), leverkusen.collabfc.com (up), bayern.collabfc.com (up), leipzig.collabfc.com (up), germanrelay.collabfc.com (up), dortmund.collabfc.com (up), werder.collabfc.com (up), hoffenheim.collabfc.com (up), luton.collabfc.com (up))
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-09-19 16:09:44 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- [2024-09-19 15:54:03 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 15:22:09 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 14:51:06 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 14:04:06 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 13:17:39 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 12:15:44 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- [2024-09-19 09:55:42 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 09:24:37 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 08:22:47 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-09-19 16:41:08 in 0.20s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 16:25:16 in 0.21s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 15:38:12 in 0.20s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 15:06:58 in 0.21s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 14:35:12 in 0.20s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 14:19:58 in 0.20s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 13:48:44 in 0.20s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 13:33:10 in 0.20s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 13:02:22 in 0.20s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 12:46:49 in 0.21s]: IP: 172.67.165.136 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-09-19 14:35:12 in 0.19s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 06:17:55 in 0.19s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-18 21:50:14 in 0.19s]: IP: 104.21.50.187 / OK / HTTP status: 200
- /nodeinfo/2.1.json ₍⇗₎
- [2024-09-19 16:41:08 in 0.73s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 16:25:16 in 0.75s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 15:38:12 in 0.75s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 15:06:58 in 0.76s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 14:35:12 in 0.99s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 14:19:58 in 1.00s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 13:48:44 in 0.75s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 13:33:10 in 1.02s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 13:02:22 in 0.71s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 12:46:49 in 0.71s]: IP: 172.67.165.136 / OK / HTTP status: 200