bayern.collabfc.com — Bayern
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: 28
- Posts per user: 7.00
- 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:47 — 2024-09-19 16:24
users: 4 (0.00/day)
min/max/avg/stddev: 4 / 4 / 4.00 / 0.00
⋯ ⋯posts: 28 (19.14/day)
min/max/avg/stddev: 7 / 28 / 17.84 / 6.23
peers: 21 (1.90/day)
min/max/avg/stddev: 19 / 21 / 20.89 / 0.45
response_time: 1.223 (1.10/day)
min/max/avg/stddev: 0 / 2 / 1.04 / 0.80
Crawling Info
First contact: 2024-09-18 (26.7 hours ago)
Last successful contact: 2024-09-19 (4.2 minutes ago)
Contact: 119 successful, 46 failed.
Average fetch time: 1.05s
Next attempt scheduled for 10.8 minutes from now.
Found through lounge.collabfc.com (up)
IP address: 104.21.50.187 (and 19 others, including: astonvilla.collabfc.com (up), frankfurt.collabfc.com (up), stpauli.collabfc.com (up), stuttgart.collabfc.com (up), spurs.collabfc.com (up), augsburg.collabfc.com (up), bochum.collabfc.com (up), union.collabfc.com (up), mainz.collabfc.com (up), wolves.collabfc.com (up))
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-09-19 15:05:30 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- [2024-09-19 14:49:55 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- [2024-09-19 14:34:11 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 13:47:39 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- [2024-09-19 13:16:32 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- [2024-09-19 12:45:41 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- [2024-09-19 12:14:49 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 11:59:00 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 11:43:28 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- [2024-09-19 09:39:13 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-09-19 16:24:18 in 0.22s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 16:08:47 in 0.23s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 15:53:02 in 0.21s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 15:36:53 in 0.22s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 15:21:00 in 0.23s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 14:18:41 in 0.21s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 14:03:03 in 0.21s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 13:32:08 in 0.20s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 13:01:06 in 0.46s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 12:30:10 in 0.21s]: IP: 172.67.165.136 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-09-19 11:12:24 in 0.20s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 01:54:42 in 0.20s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-18 15:07:42 in 0.24s]: IP: 104.21.50.187 / OK / HTTP status: 200
- /nodeinfo/2.1.json ₍⇗₎
- [2024-09-19 16:24:17 in 0.78s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 16:08:47 in 0.78s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 15:53:02 in 0.76s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 15:36:53 in 0.76s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 15:21:00 in 0.80s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 14:18:40 in 0.79s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 14:03:03 in 0.75s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 13:32:06 in 0.97s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 13:01:06 in 0.73s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 12:30:10 in 0.76s]: IP: 172.67.165.136 / OK / HTTP status: 200