Details
up since 2024-11-29 01:06 (3.7 months ago)
- Uptime: 45.29%
- Users: 2 (1 active this month, 2 active last six months)
- Posts: 0
- Posts per user: 0.00
- Peers: 0
- Version: lemmy 0.19.10
- Source code: https://github.com/LemmyNet/lemmy
- Registrations: Closed
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2025-03-21 11:46 — 2025-03-22 10:12
users: 2 (0.00/day)
min/max/avg/stddev: 2 / 2 / 2.00 / 0.00
⋯ —posts: 0 (0.00/day)
min/max/avg/stddev: 0 / 0 / 0.00 / 0.00
⋯ —response_time: 1.514 (0.01/day)
min/max/avg/stddev: 1 / 1 / 1.41 / 0.10
—
Crawling Info
First contact: 2023-07-16 (20.2 months ago)
Last successful contact: 2025-03-22 (43.8 seconds ago)
Contact: 6922 successful, 3812 failed.
Average fetch time: 1.41s
Next attempt scheduled for 14.3 minutes from now.
Found through rytter.me (down)
IP address: 143.198.118.78
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2025-03-21 07:43:58 in 0.00s]: IP: 143.198.118.78 / Error: http / HTTP status: -1
- [2025-03-21 03:56:40 in 0.00s]: IP: 143.198.118.78 / Error: http / HTTP status: -1
- [2025-03-20 17:03:03 in 0.00s]: IP: 143.198.118.78 / Error: http / HTTP status: -1
- [2025-03-20 15:36:51 in 0.00s]: IP: 143.198.118.78 / Error: http / HTTP status: -1
- [2025-03-19 20:43:32 in 0.00s]: IP: 143.198.118.78 / Error: http / HTTP status: -1
- [2025-03-19 19:08:08 in 0.00s]: IP: 143.198.118.78 / Error: http / HTTP status: -1
- [2025-03-19 13:52:10 in 0.00s]: IP: 143.198.118.78 / Error: http / HTTP status: -1
- [2025-03-19 04:17:22 in 0.00s]: IP: 143.198.118.78 / Error: http / HTTP status: -1
- [2025-03-18 20:23:21 in 0.00s]: IP: 143.198.118.78 / Error: http / HTTP status: -1
- [2025-03-18 06:30:38 in 0.00s]: IP: 143.198.118.78 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2025-03-22 09:28:11 in 0.07s]: IP: 143.198.118.78 / Error: http / HTTP status: 404
- [2025-03-21 06:55:25 in 0.24s]: IP: 143.198.118.78 / Error: http / HTTP status: 404
- [2025-03-21 02:34:16 in 0.07s]: IP: 143.198.118.78 / Error: http / HTTP status: 404
- [2025-03-19 11:49:03 in 0.07s]: IP: 143.198.118.78 / Error: http / HTTP status: 404
- [2025-03-19 11:08:40 in 0.07s]: IP: 143.198.118.78 / Error: http / HTTP status: 404
- [2025-03-19 02:04:43 in 0.07s]: IP: 143.198.118.78 / Error: http / HTTP status: 404
- [2025-03-19 01:21:24 in 0.07s]: IP: 143.198.118.78 / Error: http / HTTP status: 404
- [2025-03-18 13:18:50 in 0.07s]: IP: 143.198.118.78 / Error: http / HTTP status: 404
- [2025-03-18 10:34:57 in 0.07s]: IP: 143.198.118.78 / Error: http / HTTP status: 404
- [2025-03-18 02:38:05 in 0.07s]: IP: 143.198.118.78 / Error: http / HTTP status: 404
- /api/v1/instance/peers ₍⇗₎
- [2025-03-21 21:57:23 in 0.07s]: IP: 143.198.118.78 / Error: http / HTTP status: 404
- [2025-03-21 05:18:11 in 0.07s]: IP: 143.198.118.78 / Error: http / HTTP status: 404
- [2025-03-20 19:22:38 in 0.07s]: IP: 143.198.118.78 / Error: http / HTTP status: 404
- [2025-03-20 05:07:10 in 0.07s]: IP: 143.198.118.78 / Error: http / HTTP status: 404
- [2025-03-19 16:54:01 in 0.07s]: IP: 143.198.118.78 / Error: http / HTTP status: 404
- [2025-03-19 05:39:27 in 0.07s]: IP: 143.198.118.78 / Error: http / HTTP status: 404
- [2025-03-18 16:25:41 in 0.07s]: IP: 143.198.118.78 / Error: http / HTTP status: 404
- [2025-03-18 07:56:21 in 0.07s]: IP: 143.198.118.78 / Error: http / HTTP status: 404
- [2025-03-17 22:33:10 in 0.07s]: IP: 143.198.118.78 / Error: http / HTTP status: 404
- [2025-03-17 14:33:04 in 0.07s]: IP: 143.198.118.78 / Error: http / HTTP status: 404
- /nodeinfo/2.0.json ₍⇗₎
- [2025-03-21 11:46:16 in 0.31s]: IP: 143.198.118.78 / OK / HTTP status: 200
- [2025-03-21 11:04:31 in 0.36s]: IP: 143.198.118.78 / OK / HTTP status: 200
- [2025-03-21 10:21:20 in 0.35s]: IP: 143.198.118.78 / OK / HTTP status: 200
- [2025-03-21 09:41:24 in 0.36s]: IP: 143.198.118.78 / OK / HTTP status: 200
- [2025-03-21 06:55:25 in 1.86s]: IP: 143.198.118.78 / OK / HTTP status: 200
- [2025-03-21 06:03:29 in 0.30s]: IP: 143.198.118.78 / OK / HTTP status: 200
- [2025-03-21 05:18:11 in 0.31s]: IP: 143.198.118.78 / OK / HTTP status: 200
- [2025-03-21 04:38:08 in 0.31s]: IP: 143.198.118.78 / OK / HTTP status: 200
- [2025-03-21 03:18:58 in 0.36s]: IP: 143.198.118.78 / OK / HTTP status: 200
- [2025-03-21 02:34:16 in 0.35s]: IP: 143.198.118.78 / OK / HTTP status: 200
- /nodeinfo/2.1 ₍⇗₎
- [2025-03-22 10:12:17 in 0.31s]: IP: 143.198.118.78 / OK / HTTP status: 200
- [2025-03-22 09:28:11 in 0.37s]: IP: 143.198.118.78 / OK / HTTP status: 200
- [2025-03-22 08:34:47 in 0.36s]: IP: 143.198.118.78 / OK / HTTP status: 200
- [2025-03-22 07:48:23 in 0.41s]: IP: 143.198.118.78 / OK / HTTP status: 200
- [2025-03-22 06:55:39 in 0.42s]: IP: 143.198.118.78 / OK / HTTP status: 200
- [2025-03-22 06:04:28 in 1.10s]: IP: 143.198.118.78 / OK / HTTP status: 200
- [2025-03-22 05:07:26 in 1.37s]: IP: 143.198.118.78 / OK / HTTP status: 200
- [2025-03-22 04:03:13 in 0.51s]: IP: 143.198.118.78 / OK / HTTP status: 200
- [2025-03-22 02:50:42 in 0.46s]: IP: 143.198.118.78 / OK / HTTP status: 200
- [2025-03-22 01:30:19 in 0.63s]: IP: 143.198.118.78 / OK / HTTP status: 200
Federation Info
Peers:
Federation restrictions
Unsalted hashes of "roanoke.social"
- MD5: d78ef7f763cb1171fe0f5bfb9208a04e
- SHA1: 9d154cf1c9c451b48207a06e8d698669a4de8c45
- SHA256: 06212b064a9b614d6524199872afa91e9746cd1eb5e3b17c883d96de776eaf53