threads.beep.computer — Lioverse
Details
down since 2025-03-20 03:48 (17.6 hours ago)
- Uptime: 24.00%
- Users: 13 (10 active this month, 16 active last six months)
- Posts: 2949
- Posts per user: 226.85
- Peers: 15552
- Version: mastodon 4.3.4+glitch
- Registrations: Closed
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2025-03-06 21:26 — 2025-03-20 21:17
users: 13 (0.00/day)
min/max/avg/stddev: 13 / 13 / 13.00 / 0.00
⋯ ⋯posts: 2949 (-15.28/day)
min/max/avg/stddev: 2943 / 3148 / 3077.99 / 47.64
peers: 15552 (6.99/day)
min/max/avg/stddev: 15477 / 15552 / 15512.67 / 30.73
response_time: 0.707 (-0.30/day)
min/max/avg/stddev: 0 / 9 / 1.91 / 1.32
Crawling Info
First contact: 2023-12-31 (14.6 months ago)
Last successful contact: 2025-03-19 (23.3 hours ago)
Latest attempt: 2025-03-20 (6.0 minutes ago)
Contact: 4268 successful, 1380 failed.
Average fetch time: 1.91s
Next attempt scheduled for 9.0 minutes from now.
Found through mozilla.social (down)
IP address: 92.119.127.37 (and 11 others, including: toot.beep.computer (up), shitpost.beep.computer (down), pics.beep.computer (down), rants.beep.computer (down), beep.beep.computer (down), activityrelay.beep.computer (up), pixelfed.beep.computer (down), lemmy.beep.computer (down), toots.beep.computer (down), key.beep.computer (down))
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2025-03-20 21:17:41 in 0.00s]: IP: 92.119.127.37 / Error: http / HTTP status: -1
- [2025-03-20 21:02:34 in 0.00s]: IP: 92.119.127.37 / Error: http / HTTP status: -1
- [2025-03-20 20:46:16 in 0.00s]: IP: 92.119.127.37 / Error: http / HTTP status: -1
- [2025-03-20 20:26:58 in 0.00s]: IP: 92.119.127.37 / Error: http / HTTP status: -1
- [2025-03-20 20:10:42 in 0.00s]: IP: 92.119.127.37 / Error: http / HTTP status: -1
- [2025-03-20 19:48:45 in 0.00s]: IP: 92.119.127.37 / Error: http / HTTP status: -1
- [2025-03-20 19:26:03 in 0.00s]: IP: 92.119.127.37 / Error: http / HTTP status: -1
- [2025-03-20 19:07:11 in 0.00s]: IP: 92.119.127.37 / Error: http / HTTP status: -1
- [2025-03-20 18:51:46 in 0.00s]: IP: 92.119.127.37 / Error: http / HTTP status: -1
- [2025-03-20 18:32:58 in 0.00s]: IP: 92.119.127.37 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2025-03-19 22:04:32 in 0.14s]: IP: 94.130.149.141 / Error: http / HTTP status: 403
- [2025-03-19 10:14:23 in 0.14s]: IP: 94.130.149.141 / Error: http / HTTP status: 403
- [2025-03-19 02:12:28 in 0.14s]: IP: 94.130.149.141 / Error: http / HTTP status: 403
- [2025-03-18 15:46:06 in 0.14s]: IP: 94.130.149.141 / OK / HTTP status: 200
- [2025-03-17 22:48:14 in 0.14s]: IP: 94.130.149.141 / Error: http / HTTP status: 403
- [2025-03-17 17:43:08 in 0.14s]: IP: 94.130.149.141 / Error: http / HTTP status: 403
- [2025-03-17 09:30:54 in 0.14s]: IP: 94.130.149.141 / Error: http / HTTP status: 403
- [2025-03-17 04:38:38 in 0.14s]: IP: 94.130.149.141 / Error: http / HTTP status: 403
- [2025-03-17 01:10:33 in 0.14s]: IP: 94.130.149.141 / Error: http / HTTP status: 403
- [2025-03-16 21:17:35 in 0.14s]: IP: 94.130.149.141 / Error: http / HTTP status: 403
- /api/v1/instance/peers ₍⇗₎
- [2025-03-19 11:35:43 in 0.14s]: IP: 94.130.149.141 / Error: http / HTTP status: 403
- [2025-03-19 00:00:43 in 0.14s]: IP: 94.130.149.141 / Error: http / HTTP status: 403
- [2025-03-18 13:27:40 in 0.14s]: IP: 94.130.149.141 / Error: http / HTTP status: 403
- [2025-03-18 03:43:21 in 0.14s]: IP: 94.130.149.141 / Error: http / HTTP status: 403
- [2025-03-17 03:58:23 in 0.14s]: IP: 94.130.149.141 / Error: http / HTTP status: 403
- [2025-03-16 18:08:45 in 0.14s]: IP: 94.130.149.141 / Error: http / HTTP status: 403
- [2025-03-16 09:27:59 in 0.14s]: IP: 94.130.149.141 / Error: http / HTTP status: 403
- [2025-03-16 01:20:33 in 0.14s]: IP: 94.130.149.141 / Error: http / HTTP status: 403
- [2025-03-15 17:19:03 in 0.50s]: IP: 94.130.149.141 / Error: http / HTTP status: 403
- [2025-03-15 01:30:10 in 0.14s]: IP: 94.130.149.141 / Error: http / HTTP status: 403
- /nodeinfo/2.0 ₍⇗₎
- [2025-03-19 22:04:32 in 0.85s]: IP: 94.130.149.141 / OK / HTTP status: 200
- [2025-03-19 21:17:17 in 1.57s]: IP: 94.130.149.141 / Error: unparseable / HTTP status: 200
- [2025-03-19 20:30:00 in 0.70s]: IP: 94.130.149.141 / OK / HTTP status: 200
- [2025-03-19 19:44:22 in 1.21s]: IP: 94.130.149.141 / OK / HTTP status: 200
- [2025-03-19 18:49:16 in 1.11s]: IP: 94.130.149.141 / OK / HTTP status: 200
- [2025-03-19 17:23:42 in 0.96s]: IP: 94.130.149.141 / OK / HTTP status: 200
- [2025-03-19 16:40:18 in 0.85s]: IP: 94.130.149.141 / OK / HTTP status: 200
- [2025-03-19 15:53:37 in 0.70s]: IP: 94.130.149.141 / OK / HTTP status: 200
- [2025-03-19 15:01:24 in 0.71s]: IP: 94.130.149.141 / OK / HTTP status: 200
- [2025-03-19 14:18:46 in 1.11s]: IP: 94.130.149.141 / OK / HTTP status: 200
Federation Info
Peers: 15552
Federation restrictions
Unsalted hashes of "threads.beep.computer"
- MD5: 3d67c39f7ca6c09147b8b0589dd9a5ef
- SHA1: 0de72fdf318542baa9b3b1a8562c8058cdc24993
- SHA256: a3059989d1da557362c89f55f134b2f2dd1d519d3199da26c349bd1c1ca6054e