social.harter.us — Harter Social
Details
up since 2024-06-28 15:54 (4.8 days ago)
- Uptime: 96.02%
- Users: 3 (2 active this month, 2 active last six months)
- Posts: 694
- Posts per user: 231.33
- Peers: 8516
- Version: mastodon 4.2.9
- Registrations: Closed
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-06-20 11:51 — 2024-07-03 10:53
users: 3 (0.00/day)
min/max/avg/stddev: 3 / 3 / 3.00 / 0.00
⋯ ⋯posts: 694 (0.80/day)
min/max/avg/stddev: 466 / 694 / 668.21 / 61.63
peers: 8516 (7.75/day)
min/max/avg/stddev: 6307 / 8516 / 8258.09 / 598.09
response_time: 2.132 (0.01/day)
min/max/avg/stddev: 0 / 117 / 49.68 / 42.80
Crawling Info
First contact: 2022-11-24 (19.3 months ago)
Last successful contact: 2024-07-03 (34.5 minutes ago)
Contact: 21070 successful, 5618 failed.
Average fetch time: 49.68s
Next attempt scheduled for 25.0 minutes from now.
Found through social.azkware.net (down)
IP address: 217.180.233.84 (and 2 others: harter.us (down), books.harter.house (down))
Staff
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-07-03 04:49:46 in 0.00s]: IP: 217.180.233.84 / Error: http / HTTP status: -1
- [2024-07-03 00:50:48 in 0.00s]: IP: 217.180.233.84 / Error: http / HTTP status: -1
- [2024-07-02 20:49:03 in 0.00s]: IP: 217.180.233.84 / Error: http / HTTP status: -1
- [2024-07-02 16:47:24 in 0.00s]: IP: 217.180.233.84 / Error: http / HTTP status: -1
- [2024-07-02 14:47:09 in 0.00s]: IP: 217.180.233.84 / Error: http / HTTP status: -1
- [2024-07-02 12:43:14 in 0.00s]: IP: 217.180.233.84 / Error: http / HTTP status: -1
- [2024-07-02 11:40:54 in 0.00s]: IP: 217.180.233.84 / Error: http / HTTP status: -1
- [2024-07-02 10:40:02 in 0.00s]: IP: 217.180.233.84 / Error: http / HTTP status: -1
- [2024-07-02 07:38:57 in 0.00s]: IP: 217.180.233.84 / Error: http / HTTP status: -1
- [2024-07-02 03:37:36 in 0.00s]: IP: 217.180.233.84 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-07-03 10:53:06 in 0.08s]: IP: 217.180.233.84 / OK / HTTP status: 200
- [2024-07-03 09:52:38 in 0.09s]: IP: 217.180.233.84 / OK / HTTP status: 200
- [2024-07-03 08:52:08 in 0.09s]: IP: 217.180.233.84 / OK / HTTP status: 200
- [2024-07-03 07:51:49 in 0.09s]: IP: 217.180.233.84 / OK / HTTP status: 200
- [2024-07-03 06:49:52 in 0.10s]: IP: 217.180.233.84 / OK / HTTP status: 200
- [2024-07-03 05:49:19 in 0.09s]: IP: 217.180.233.84 / OK / HTTP status: 200
- [2024-07-03 03:49:12 in 0.10s]: IP: 217.180.233.84 / OK / HTTP status: 200
- [2024-07-03 02:49:27 in 0.14s]: IP: 217.180.233.84 / OK / HTTP status: 200
- [2024-07-03 01:50:13 in 0.10s]: IP: 217.180.233.84 / OK / HTTP status: 200
- [2024-07-02 23:49:47 in 0.09s]: IP: 217.180.233.84 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-07-02 19:48:00 in 0.08s]: IP: 217.180.233.84 / OK / HTTP status: 200
- [2024-06-30 12:42:39 in 0.10s]: IP: 217.180.233.84 / OK / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2024-07-03 10:53:06 in 0.35s]: IP: 217.180.233.84 / OK / HTTP status: 200
- [2024-07-03 09:52:38 in 0.34s]: IP: 217.180.233.84 / OK / HTTP status: 200
- [2024-07-03 08:52:08 in 0.33s]: IP: 217.180.233.84 / OK / HTTP status: 200
- [2024-07-03 07:51:49 in 0.38s]: IP: 217.180.233.84 / OK / HTTP status: 200
- [2024-07-03 06:49:52 in 0.34s]: IP: 217.180.233.84 / OK / HTTP status: 200
- [2024-07-03 05:49:19 in 0.37s]: IP: 217.180.233.84 / OK / HTTP status: 200
- [2024-07-03 03:49:12 in 0.35s]: IP: 217.180.233.84 / OK / HTTP status: 200
- [2024-07-03 02:49:27 in 0.36s]: IP: 217.180.233.84 / OK / HTTP status: 200
- [2024-07-03 01:50:12 in 0.38s]: IP: 217.180.233.84 / OK / HTTP status: 200
- [2024-07-02 23:49:46 in 0.35s]: IP: 217.180.233.84 / OK / HTTP status: 200