feyenoord.collabfc.com — Feyenoord
Details
up since 2025-02-26 05:41 (4.7 days ago)
- Uptime: 99.62%
- Users: 4 (2 active this month, 2 active last six months)
- Posts: 2374
- Posts per user: 593.50
- Peers: 15
- Version: pleroma 2.8.0-3-gfe3e61f6
- Source code: https://git.pleroma.social/pleroma/pleroma
- Registrations: Open
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2025-02-22 16:18 — 2025-03-02 21:30
users: 4 (0.00/day)
min/max/avg/stddev: 4 / 4 / 4.00 / 0.00
⋯ ⋯posts: 2374 (23.43/day)
min/max/avg/stddev: 2183 / 2374 / 2300.55 / 48.75
peers: 15 (0.00/day)
min/max/avg/stddev: 15 / 15 / 15.00 / 0.00
⋯ ⋯response_time: 2.446 (-0.66/day)
min/max/avg/stddev: 0 / 31 / 2.66 / 3.79
Crawling Info
First contact: 2024-10-01 (5.0 months ago)
Last successful contact: 2025-03-02 (31.9 minutes ago)
Contact: 7784 successful, 1522 failed.
Average fetch time: 2.66s
Next attempt scheduled for 13.0 minutes ago.
Found through lounge.collabfc.com (up)
IP address: 172.67.165.136 (and 44 others, including: lens.collabfc.com (up), brentford.collabfc.com (up), augsburg.collabfc.com (up), manu.collabfc.com (up), spurs.collabfc.com (up), heidenheim.collabfc.com (up), kiel.collabfc.com (up), realmadrid.collabfc.com (up), lounge.collabfc.com (up), inter.collabfc.com (up))
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2025-03-02 19:13:59 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2025-03-02 13:55:25 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- [2025-03-02 01:46:44 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2025-03-01 10:28:53 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- [2025-03-01 08:09:30 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- [2025-03-01 07:24:23 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2025-03-01 03:32:16 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2025-03-01 00:19:17 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2025-02-28 12:38:01 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- [2025-02-27 23:54:56 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2025-03-02 21:30:41 in 0.20s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2025-03-02 20:45:27 in 0.19s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2025-03-02 19:58:52 in 0.20s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2025-03-02 18:29:20 in 0.21s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2025-03-02 17:44:37 in 0.20s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2025-03-02 16:58:28 in 0.20s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2025-03-02 16:13:16 in 0.20s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2025-03-02 15:26:08 in 0.31s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2025-03-02 14:39:10 in 0.19s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2025-03-02 13:10:03 in 0.20s]: IP: 172.67.165.136 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2025-03-02 13:10:03 in 0.21s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2025-03-02 04:51:01 in 0.20s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2025-03-01 18:12:39 in 0.20s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2025-03-01 09:42:33 in 0.20s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2025-02-28 18:02:58 in 0.42s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2025-02-28 05:36:14 in 0.20s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2025-02-27 18:49:38 in 0.28s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2025-02-27 09:28:23 in 0.19s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2025-02-27 00:02:55 in 0.21s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2025-02-26 14:52:18 in 0.21s]: IP: 199.59.243.228 / OK / HTTP status: 200
- /nodeinfo/2.1.json ₍⇗₎
- [2025-03-02 21:30:41 in 0.75s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2025-03-02 20:45:27 in 0.71s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2025-03-02 19:58:51 in 0.73s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2025-03-02 18:29:20 in 0.81s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2025-03-02 17:44:37 in 0.74s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2025-03-02 16:58:28 in 0.71s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2025-03-02 16:13:16 in 0.76s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2025-03-02 15:26:08 in 1.20s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2025-03-02 14:39:10 in 1.12s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2025-03-02 13:10:03 in 0.73s]: IP: 172.67.165.136 / OK / HTTP status: 200