atleticomadrid.collabfc.com — Atletico Madrid
Details
up since 2025-02-26 07:30 (4.6 days ago)
- Uptime: 99.44%
- Users: 4 (1 active this month, 4 active last six months)
- Posts: 445
- Posts per user: 111.25
- Peers: 82
- 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 18:16 — 2025-03-02 21:41
users: 4 (0.00/day)
min/max/avg/stddev: 4 / 4 / 4.00 / 0.00
⋯ ⋯posts: 445 (4.07/day)
min/max/avg/stddev: 412 / 445 / 429.12 / 9.68
peers: 82 (0.00/day)
min/max/avg/stddev: 82 / 82 / 82.00 / 0.00
⋯ ⋯response_time: 4.814 (0.09/day)
min/max/avg/stddev: 0 / 10 / 3.34 / 1.87
Crawling Info
First contact: 2024-10-01 (5.0 months ago)
Last successful contact: 2025-03-02 (17.9 minutes ago)
Contact: 7503 successful, 1470 failed.
Average fetch time: 3.34s
Next attempt scheduled for 5.6 minutes from now.
Found through lounge.collabfc.com (up)
IP address: 104.21.50.187 (and 38 others, including: westham.collabfc.com (up), liverpool.collabfc.com (up), napoli.collabfc.com (up), athleticbilbao.collabfc.com (up), mallorca.collabfc.com (up), arsenal.collabfc.com (up), brightonandhove.collabfc.com (up), bayern.collabfc.com (up), fiorentina.collabfc.com (up), mancity.collabfc.com (up))
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2025-03-02 05:51:37 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- [2025-03-01 07:14:23 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2025-03-01 06:24:01 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2025-03-01 04:44:18 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2025-03-01 02:11:04 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2025-02-28 14:16:20 in 0.00s]: IP: 172.67.165.136 / Error: http / HTTP status: -1
- [2025-02-28 13:23:52 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- [2025-02-28 11:41:23 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- [2025-02-28 05:36:52 in 0.00s]: IP: 104.21.50.187 / Error: http / HTTP status: -1
- [2025-02-27 16:36:32 in 0.57s]: IP: 172.67.165.136 / Error: http / HTTP status: 502
- /api/v1/instance ₍⇗₎
- [2025-03-02 21:41:05 in 1.34s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2025-03-02 20:52:13 in 0.19s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2025-03-02 20:01:16 in 0.19s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2025-03-02 19:12:13 in 0.21s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2025-03-02 18:23:25 in 0.19s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2025-03-02 17:34:20 in 0.20s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2025-03-02 16:43:50 in 0.21s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2025-03-02 15:55:07 in 0.20s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2025-03-02 15:02:59 in 0.45s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2025-03-02 14:13:11 in 0.18s]: IP: 172.67.165.136 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2025-03-02 09:09:35 in 0.20s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2025-03-01 20:37:02 in 0.29s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2025-03-01 12:11:36 in 0.20s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2025-03-01 03:02:14 in 0.20s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2025-02-28 15:09:18 in 0.20s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2025-02-28 04:45:45 in 0.19s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2025-02-27 20:12:17 in 0.19s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2025-02-27 10:29:14 in 0.20s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2025-02-26 15:25:21 in 10.57s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2025-02-24 22:18:17 in 0.98s]: IP: 172.67.165.136 / OK / HTTP status: 200
- /nodeinfo/2.1.json ₍⇗₎
- [2025-03-02 21:41:05 in 2.21s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2025-03-02 20:52:13 in 0.74s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2025-03-02 20:01:16 in 1.06s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2025-03-02 19:12:13 in 0.73s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2025-03-02 18:23:25 in 0.69s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2025-03-02 17:34:20 in 0.74s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2025-03-02 16:43:50 in 0.71s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2025-03-02 15:55:07 in 0.70s]: IP: 172.67.165.136 / OK / HTTP status: 200
- [2025-03-02 15:02:59 in 1.38s]: IP: 104.21.50.187 / OK / HTTP status: 200
- [2025-03-02 14:13:11 in 0.70s]: IP: 172.67.165.136 / OK / HTTP status: 200