stuttgart.collabfc.com — Stuttgart
Details
up since 2024-09-18 13:48 (26.8 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:52 — 2024-09-19 16:25
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.74/day)
min/max/avg/stddev: 5 / 10 / 7.80 / 1.72
response_time: 2.648 (0.49/day)
min/max/avg/stddev: 0 / 2 / 1.78 / 0.94
Crawling Info
First contact: 2024-09-18 (26.8 hours ago)
Last successful contact: 2024-09-19 (8.4 minutes ago)
Contact: 161 successful, 25 failed.
Average fetch time: 1.78s
Next attempt scheduled for 6.6 minutes from now.
Found through augsburg.collabfc.com (up)
IP address: 104.21.50.187 (and 16 others, including: leverkusen.collabfc.com (up), bayern.collabfc.com (up), frankfurt.collabfc.com (up), spurs.collabfc.com (up), augsburg.collabfc.com (up), union.collabfc.com (up), werder.collabfc.com (up), hoffenheim.collabfc.com (up), luton.collabfc.com (up), wolves.collabfc.com (up))
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-09-19 14:35:11 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:31:13 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- [2024-09-19 10:26:44 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- [2024-09-19 10:11:00 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 05:16:02 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- [2024-09-19 04:13:40 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- [2024-09-19 02:56:38 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- [2024-09-19 01:39:55 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2024-09-19 01:09:41 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-09-19 16:25:24 in 0.20s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 16:10:04 in 0.20s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 15:54:10 in 0.21s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 15:38:15 in 0.20s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 15:22:11 in 0.21s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 15:06:59 in 0.21s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 14:51:07 in 0.20s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 14:20:00 in 0.20s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 14:04:07 in 0.20s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 13:48:44 in 0.22s]: IP: 104.21.50.187 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-09-19 13:02:22 in 0.19s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 03:11:42 in 0.19s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-18 18:28:34 in 0.25s]: IP: 104.21.50.187 / OK / HTTP status: 200
- /nodeinfo/2.1.json ₍⇗₎
- [2024-09-19 16:25:24 in 0.73s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 16:10:04 in 0.72s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 15:54:10 in 0.76s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 15:38:15 in 0.73s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 15:22:11 in 0.74s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 15:06:59 in 0.72s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 14:51:07 in 0.75s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 14:20:00 in 0.72s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2024-09-19 14:04:07 in 0.73s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2024-09-19 13:48:44 in 0.70s]: IP: 104.21.50.187 / OK / HTTP status: 200