about.iftas.org — IFTAS
Details
up since 2023-11-08 23:44 (11.9 months ago)
- Uptime: 100.00%
- Users: 1 (1 active this month, 1 active last six months)
- Posts: 22
- Posts per user: 22.00
- Peers: 0
- Version: wordpress 6.6
- Registrations: Closed
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-10-26 06:17 — 2024-11-05 06:02
users: 1 (0.00/day)
min/max/avg/stddev: 1 / 1 / 1.00 / 0.00
⋯ ⋯posts: 22 (0.22/day)
min/max/avg/stddev: 19 / 22 / 20.86 / 0.99
response_time: 0.701 (-0.07/day)
min/max/avg/stddev: 0 / 2 / 1.30 / 0.68
Crawling Info
First contact: 2023-11-08 (11.9 months ago)
Last successful contact: 2024-11-04 (24.5 hours ago)
Latest attempt: 2024-11-05 (4.5 hours ago)
Contact: 2220 successful, 988 failed.
Average fetch time: 1.30s
Next attempt scheduled for 5.4 hours from now.
Found through social.weyr.org.uk (down)
IP address: 192.0.78.25 (and 1014 others, including: resinshops.com (up), renatopassalacqua.com (up), joshbelville.com (down), cybermedios.org (down), classicalwonders.com (up), thegnarlyblog.com (up), boldcityp.org (down), modayode.com (up), edwardcastronova.com (down), storiesfromindonesia.com (down))
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-11-05 06:02:34 in 0.00s]: IP: 192.0.78.25 / Error: http / HTTP status: -1
- [2024-11-04 20:03:49 in 0.00s]: IP: 192.0.78.24 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-11-04 10:03:37 in 0.73s]: IP: 192.0.78.24 / Error: http / HTTP status: 404
- [2024-11-02 18:04:40 in 0.39s]: IP: 192.0.78.25 / Error: http / HTTP status: 404
- /api/v1/instance/peers ₍⇗₎
- [2024-11-03 04:06:21 in 0.58s]: IP: 192.0.78.24 / Error: http / HTTP status: 404
- /wp-json/activitypub/1.0/nodeinfo ₍⇗₎
- [2024-11-04 10:03:37 in 1.20s]: IP: 192.0.78.24 / OK / HTTP status: 200
- [2024-11-04 00:04:15 in 0.09s]: IP: 192.0.78.25 / OK / HTTP status: 200
- [2024-11-03 14:05:25 in 0.09s]: IP: 192.0.78.24 / OK / HTTP status: 200
- [2024-11-03 04:06:21 in 3.14s]: IP: 192.0.78.24 / OK / HTTP status: 200
- [2024-11-02 18:04:40 in 0.11s]: IP: 192.0.78.25 / OK / HTTP status: 200