family.dieschburg.com
Dieschburg family photos
Details
up since 2024-11-04 10:22 (20.5 hours ago)
- Uptime: 100.00%
- Users: 2 (2 active this month, 2 active last six months)
- Posts: 51
- Posts per user: 25.50
- Peers: 3
- Version: pixelfed 3.5.3 (compatible; Pixelfed 0.12.3)
- Registrations: Open
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-11-04 20:14 — 2024-11-05 06:35
users: 2 (0.00/day)
min/max/avg/stddev: 2 / 2 / 2.00 / 0.00
⋯ —posts: 51 (0.00/day)
min/max/avg/stddev: 51 / 51 / 51.00 / 0.00
⋯ —peers: 3 (0.00/day)
min/max/avg/stddev: 3 / 3 / 3.00 / 0.00
⋯ —response_time: 1.223 (0.36/day)
min/max/avg/stddev: 0 / 1 / 1.16 / 0.17
Crawling Info
First contact: 2024-11-04 (20.5 hours ago)
Last successful contact: 2024-11-05 (15.9 minutes ago)
Contact: 109 successful, 16 failed.
Average fetch time: 1.16s
Next attempt scheduled for 55.2 seconds ago.
Found through social.reapers.de (up)
IP address: 193.70.46.138 (and blog.dieschburg.com.)
Staff
ndieschburg@family.dieschburg.com
[No bio.]
[No bio.]
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-11-05 06:19:27 in 0.00s]: IP: 193.70.46.138 / Error: http / HTTP status: -1
- [2024-11-05 03:55:23 in 0.00s]: IP: 193.70.46.138 / Error: http / HTTP status: -1
- [2024-11-05 03:08:00 in 0.00s]: IP: 193.70.46.138 / Error: http / HTTP status: -1
- [2024-11-05 02:36:59 in 0.00s]: IP: 193.70.46.138 / Error: http / HTTP status: -1
- [2024-11-05 02:21:33 in 0.00s]: IP: 193.70.46.138 / Error: http / HTTP status: -1
- [2024-11-04 23:57:20 in 0.00s]: IP: 193.70.46.138 / Error: http / HTTP status: -1
- [2024-11-04 22:53:26 in 0.00s]: IP: 193.70.46.138 / Error: http / HTTP status: -1
- [2024-11-04 22:06:08 in 0.00s]: IP: 193.70.46.138 / Error: http / HTTP status: -1
- [2024-11-04 20:14:16 in 0.00s]: IP: 193.70.46.138 / Error: http / HTTP status: -1
- [2024-11-04 19:57:00 in 0.00s]: IP: 193.70.46.138 / Error: http / HTTP status: -1
- /api/nodeinfo/2.0.json ₍⇗₎
- [2024-11-05 06:35:05 in 0.75s]: IP: 193.70.46.138 / OK / HTTP status: 200
- [2024-11-05 06:03:42 in 0.73s]: IP: 193.70.46.138 / OK / HTTP status: 200
- [2024-11-05 05:47:25 in 0.74s]: IP: 193.70.46.138 / OK / HTTP status: 200
- [2024-11-05 05:31:37 in 0.75s]: IP: 193.70.46.138 / OK / HTTP status: 200
- [2024-11-05 05:14:32 in 1.56s]: IP: 193.70.46.138 / OK / HTTP status: 200
- [2024-11-05 04:58:38 in 0.93s]: IP: 193.70.46.138 / OK / HTTP status: 200
- [2024-11-05 04:42:54 in 0.68s]: IP: 193.70.46.138 / OK / HTTP status: 200
- [2024-11-05 04:27:03 in 1.50s]: IP: 193.70.46.138 / OK / HTTP status: 200
- [2024-11-05 04:10:57 in 0.87s]: IP: 193.70.46.138 / OK / HTTP status: 200
- [2024-11-05 03:39:40 in 2.28s]: IP: 193.70.46.138 / OK / HTTP status: 200
- /api/v1/instance ₍⇗₎
- [2024-11-05 06:35:05 in 0.17s]: IP: 193.70.46.138 / OK / HTTP status: 200
- [2024-11-05 06:03:42 in 0.17s]: IP: 193.70.46.138 / OK / HTTP status: 200
- [2024-11-05 05:47:25 in 0.17s]: IP: 193.70.46.138 / OK / HTTP status: 200
- [2024-11-05 05:31:37 in 0.17s]: IP: 193.70.46.138 / OK / HTTP status: 200
- [2024-11-05 05:14:33 in 0.36s]: IP: 193.70.46.138 / OK / HTTP status: 200
- [2024-11-05 04:58:38 in 0.18s]: IP: 193.70.46.138 / OK / HTTP status: 200
- [2024-11-05 04:42:54 in 0.17s]: IP: 193.70.46.138 / OK / HTTP status: 200
- [2024-11-05 04:27:03 in 1.01s]: IP: 193.70.46.138 / OK / HTTP status: 200
- [2024-11-05 04:10:57 in 0.16s]: IP: 193.70.46.138 / OK / HTTP status: 200
- [2024-11-05 03:39:40 in 0.35s]: IP: 193.70.46.138 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-11-05 05:14:33 in 0.45s]: IP: 193.70.46.138 / OK / HTTP status: 200
- [2024-11-04 20:47:12 in 0.16s]: IP: 193.70.46.138 / OK / HTTP status: 200
- [2024-11-04 10:22:22 in 0.23s]: IP: 193.70.46.138 / OK / HTTP status: 200