dortmund.collabfc.com — Dortmund
Details
up since 2024-09-18 13:47 (26.7 hours ago)
- Uptime: 100.00%
- Users: 4 (2 active this month, 2 active last six months)
- Posts: 5
- Posts per user: 1.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 15:17 — 2024-09-19 16:18
users: 4 (0.00/day)
min/max/avg/stddev: 4 / 4 / 4.00 / 0.00
⋯ ⋯posts: 5 (5.27/day)
min/max/avg/stddev: 1 / 5 / 2.40 / 1.50
peers: 21 (6.49/day)
min/max/avg/stddev: 19 / 21 / 20.60 / 0.80
response_time: 8.706 (8.70/day)
min/max/avg/stddev: 1 / 8 / 2.86 / 2.95
Crawling Info
First contact: 2024-09-18 (26.7 hours ago)
Last successful contact: 2024-09-19 (11.3 minutes ago)
Contact: 125 successful, 42 failed.
Average fetch time: 2.86s
Next attempt scheduled for 6.7 minutes from now.
Found through lounge.collabfc.com (up)
IP address: 172.67.165.136 (and 22 others, including: 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), germanrelay.collabfc.com (up), fulham.collabfc.com (up), bochum.collabfc.com (up))
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-09-19 15:46:35 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 15:30:51 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- [2024-09-19 15:15:15 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 14:59:42 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- [2024-09-19 14:44:08 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 13:41:18 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 13:25:46 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 13:10:25 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 11:37:04 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 11:21:33 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-09-19 16:18:46 in 0.20s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 16:02:53 in 0.21s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 14:28:33 in 0.21s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 14:12:44 in 0.19s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 13:56:50 in 0.20s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 12:54:51 in 0.21s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 12:39:18 in 0.20s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 12:23:45 in 0.21s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 12:08:11 in 0.20s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 11:52:37 in 0.20s]: IP: 172.67.165.136 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-09-19 09:02:10 in 0.19s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 00:32:46 in 0.20s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-18 15:32:59 in 0.25s]: IP: 172.67.165.136 / OK / HTTP status: 200
- /nodeinfo/2.1.json ₍⇗₎
- [2024-09-19 16:18:46 in 0.75s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 16:02:31 in 0.76s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 14:28:33 in 0.73s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 14:12:44 in 0.73s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 13:56:50 in 0.75s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 12:54:50 in 0.80s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 12:39:18 in 0.72s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 12:23:45 in 0.82s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 12:08:10 in 1.03s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 11:52:37 in 0.70s]: IP: 172.67.165.136 / OK / HTTP status: 200