pf.floofy.city — Pixelfed
Pixelfed instance for floofy.city
Details
up since 2024-09-20 02:56 (14.8 days ago)
- Uptime: 95.78%
- Users: 4 (3 active this month, 4 active last six months)
- Posts: 1462
- Posts per user: 365.50
- Peers: 262
- Version: pixelfed 3.5.3 (compatible; Pixelfed 0.12.1)
- Registrations: Closed
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-10-01 05:31 — 2024-10-04 21:39
users: 4 (0.00/day)
min/max/avg/stddev: 4 / 4 / 4.00 / 0.00
⋯ —posts: 1462 (0.00/day)
min/max/avg/stddev: 1462 / 1462 / 1462.00 / 0.00
⋯ —peers: 262 (0.07/day)
min/max/avg/stddev: 261 / 262 / 261.50 / 0.50
—response_time: 4.772 (-0.06/day)
min/max/avg/stddev: 4 / 5 / 5.24 / 0.47
—
Crawling Info
First contact: 2024-05-31 (4.1 months ago)
Last successful contact: 2024-10-04 (5.8 minutes ago)
Contact: 10019 successful, 1745 failed.
Average fetch time: 5.24s
Next attempt scheduled for 23.4 minutes from now.
Found through heckin.how (up)
IP address: 79.139.56.50 (and 2 others: asahi.floofy.city (down), floofy.city (down))
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-10-04 20:43:19 in 0.00s]: IP: 79.139.56.50 / Error: http / HTTP status: -1
- [2024-10-04 19:23:13 in 0.00s]: IP: 79.139.56.50 / Error: http / HTTP status: -1
- [2024-10-04 15:43:02 in 0.00s]: IP: 79.139.56.50 / Error: http / HTTP status: -1
- [2024-10-04 13:57:23 in 0.00s]: IP: 79.139.56.50 / Error: http / HTTP status: -1
- [2024-10-04 13:07:49 in 0.00s]: IP: 79.139.56.50 / Error: http / HTTP status: -1
- [2024-10-04 12:43:30 in 0.00s]: IP: 79.139.56.50 / Error: http / HTTP status: -1
- [2024-10-04 05:30:00 in 0.00s]: IP: 79.139.56.50 / Error: http / HTTP status: -1
- [2024-10-04 04:38:58 in 0.00s]: IP: 79.139.56.50 / Error: http / HTTP status: -1
- [2024-10-04 01:49:24 in 0.00s]: IP: 79.139.56.50 / Error: http / HTTP status: -1
- [2024-10-04 00:53:52 in 0.00s]: IP: 79.139.56.50 / Error: http / HTTP status: -1
- /api/nodeinfo/2.0.json ₍⇗₎
- [2024-10-04 21:39:16 in 1.65s]: IP: 79.139.56.50 / OK / HTTP status: 200
- [2024-10-04 21:08:10 in 3.08s]: IP: 79.139.56.50 / OK / HTTP status: 200
- [2024-10-04 20:14:58 in 1.76s]: IP: 79.139.56.50 / OK / HTTP status: 200
- [2024-10-04 19:47:58 in 1.48s]: IP: 79.139.56.50 / OK / HTTP status: 200
- [2024-10-04 18:53:30 in 1.50s]: IP: 79.139.56.50 / OK / HTTP status: 200
- [2024-10-04 18:25:42 in 1.00s]: IP: 79.139.56.50 / OK / HTTP status: 200
- [2024-10-04 17:57:18 in 1.48s]: IP: 79.139.56.50 / OK / HTTP status: 200
- [2024-10-04 17:29:27 in 0.97s]: IP: 79.139.56.50 / OK / HTTP status: 200
- [2024-10-04 17:01:26 in 1.46s]: IP: 79.139.56.50 / OK / HTTP status: 200
- [2024-10-04 16:33:18 in 1.40s]: IP: 79.139.56.50 / OK / HTTP status: 200
- /api/v1/instance ₍⇗₎
- [2024-10-04 21:39:16 in 0.36s]: IP: 79.139.56.50 / OK / HTTP status: 200
- [2024-10-04 21:08:10 in 0.91s]: IP: 79.139.56.50 / OK / HTTP status: 200
- [2024-10-04 20:14:58 in 0.45s]: IP: 79.139.56.50 / OK / HTTP status: 200
- [2024-10-04 19:47:58 in 0.48s]: IP: 79.139.56.50 / OK / HTTP status: 200
- [2024-10-04 18:53:30 in 0.36s]: IP: 79.139.56.50 / OK / HTTP status: 200
- [2024-10-04 18:25:42 in 0.32s]: IP: 79.139.56.50 / OK / HTTP status: 200
- [2024-10-04 17:57:18 in 0.31s]: IP: 79.139.56.50 / OK / HTTP status: 200
- [2024-10-04 17:29:27 in 0.31s]: IP: 79.139.56.50 / OK / HTTP status: 200
- [2024-10-04 17:01:26 in 0.42s]: IP: 79.139.56.50 / OK / HTTP status: 200
- [2024-10-04 16:33:18 in 0.34s]: IP: 79.139.56.50 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-10-04 18:53:30 in 0.39s]: IP: 79.139.56.50 / Error: http / HTTP status: 404
- [2024-10-04 10:44:30 in 0.52s]: IP: 79.139.56.50 / Error: http / HTTP status: 404
- [2024-10-03 23:50:45 in 0.36s]: IP: 79.139.56.50 / Error: http / HTTP status: 404
- [2024-10-03 10:39:58 in 0.35s]: IP: 79.139.56.50 / Error: http / HTTP status: 404
- [2024-10-02 23:08:02 in 0.59s]: IP: 79.139.56.50 / Error: http / HTTP status: 404
- [2024-10-02 14:17:41 in 0.65s]: IP: 79.139.56.50 / Error: http / HTTP status: 404
- [2024-10-02 04:33:36 in 0.33s]: IP: 79.139.56.50 / Error: http / HTTP status: 404