heidenheim.collabfc.com — Heidenheim
Details
up since 2024-09-18 13:48 (27.3 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 14:04 — 2024-09-19 16:58
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.75/day)
min/max/avg/stddev: 5 / 10 / 7.80 / 1.72
response_time: 2.001 (2.22/day)
min/max/avg/stddev: 0 / 2 / 1.38 / 0.92
Crawling Info
First contact: 2024-09-18 (27.3 hours ago)
Last successful contact: 2024-09-19 (9.3 minutes ago)
Contact: 145 successful, 35 failed.
Average fetch time: 1.38s
Next attempt scheduled for 5.7 minutes from now.
Found through augsburg.collabfc.com (up)
IP address: 104.21.50.187 (and 21 others, including: stpauli.collabfc.com (up), bayern.collabfc.com (up), frankfurt.collabfc.com (up), stuttgart.collabfc.com (up), leverkusen.collabfc.com (up), spurs.collabfc.com (up), augsburg.collabfc.com (up), germanrelay.collabfc.com (up), fulham.collabfc.com (up), mainz.collabfc.com (up))
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-09-19 16:41:10 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 15:54:05 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 14:04:01 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- [2024-09-19 13:02:05 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 12:46:47 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 12:15:43 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 10:57:46 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 10:42:15 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 09:55:43 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 08:38:02 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-09-19 16:58:43 in 0.20s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 16:25:18 in 0.21s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 16:09:46 in 0.20s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 15:38:13 in 0.20s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 15:22:10 in 0.21s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 15:06:56 in 0.20s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 14:51:02 in 0.22s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 14:35:08 in 0.21s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 14:19:54 in 0.20s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 13:48:40 in 0.20s]: IP: 172.67.165.136 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-09-19 11:28:37 in 0.19s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 02:41:02 in 0.19s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-18 15:54:08 in 0.25s]: IP: 104.21.50.187 / OK / HTTP status: 200
- /nodeinfo/2.1.json ₍⇗₎
- [2024-09-19 16:58:43 in 0.73s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 16:25:18 in 0.71s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 16:09:46 in 0.75s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 15:38:13 in 1.01s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 15:22:10 in 0.73s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 15:06:56 in 0.82s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 14:51:02 in 0.76s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 14:35:08 in 1.11s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 14:19:54 in 0.73s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 13:48:40 in 0.71s]: IP: 172.67.165.136 / OK / HTTP status: 200