pleroma.nospy.net — My_Pleroma
Details
up since 2024-11-02 03:34 (3.9 days ago)
- Uptime: 96.29%
- Users: 1 (1 active this month, 1 active last six months)
- Posts: 0
- Posts per user: 0.00
- Peers: 952
- Version: pleroma 2.6.2
- Source code: https://git.pleroma.social/pleroma/pleroma
- Registrations: Closed
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-10-23 08:40 — 2024-11-06 00:00
users: 1 (0.00/day)
min/max/avg/stddev: 1 / 1 / 1.00 / 0.00
⋯ ⋯posts: 0 (0.00/day)
min/max/avg/stddev: 0 / 0 / 0.00 / 0.00
⋯ ⋯peers: 952 (14.07/day)
min/max/avg/stddev: 748 / 952 / 854.79 / 62.64
response_time: 61.542 (3.89/day)
min/max/avg/stddev: 0 / 105 / 30.52 / 34.90
Crawling Info
First contact: 2024-09-26 (40.3 days ago)
Last successful contact: 2024-11-05 (76.9 minutes ago)
Latest attempt: 2024-11-06 (13.6 minutes ago)
Contact: 1140 successful, 489 failed.
Average fetch time: 30.52s
Next attempt scheduled for 48.5 minutes from now.
Found through haunt.graveyard.boo (up)
IP address: 91.66.233.94 (and 14 others, including: misskey.nospy.net (up), f.nospy.net (down), hb.nospy.net (down), pt.nospy.net (down), sharkey.nospy.net (up), troet.nospy.net (down), mk.nospy.net (down), masto.nospy.net (down), iceshrimp.nospy.net (up), friends.joinfediverse.online (down))
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-11-06 00:00:04 in 0.00s]: IP: 91.66.233.94 / Error: http / HTTP status: -1
- [2024-11-05 18:45:25 in 0.00s]: IP: 91.66.233.94 / Error: http / HTTP status: -1
- [2024-11-05 16:39:24 in 0.00s]: IP: 91.66.233.94 / Error: http / HTTP status: -1
- [2024-11-05 15:35:49 in 0.00s]: IP: 91.66.233.94 / Error: http / HTTP status: -1
- [2024-11-05 12:26:52 in 0.00s]: IP: 91.66.233.94 / Error: http / HTTP status: -1
- [2024-11-05 09:18:14 in 0.00s]: IP: 91.66.233.94 / Error: http / HTTP status: -1
- [2024-11-05 07:10:27 in 0.00s]: IP: 91.66.233.94 / Error: http / HTTP status: -1
- [2024-11-05 06:07:55 in 0.00s]: IP: 91.66.233.94 / Error: http / HTTP status: -1
- [2024-11-04 23:55:25 in 0.00s]: IP: 91.66.233.94 / Error: http / HTTP status: -1
- [2024-11-04 19:46:38 in 0.00s]: IP: 91.66.233.94 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-11-05 22:56:48 in 0.22s]: IP: 91.66.233.94 / OK / HTTP status: 200
- [2024-11-05 21:54:24 in 0.22s]: IP: 91.66.233.94 / OK / HTTP status: 200
- [2024-11-05 20:51:21 in 0.22s]: IP: 91.66.233.94 / OK / HTTP status: 200
- [2024-11-05 19:48:27 in 0.21s]: IP: 91.66.233.94 / OK / HTTP status: 200
- [2024-11-05 17:42:33 in 0.21s]: IP: 91.66.233.94 / OK / HTTP status: 200
- [2024-11-05 14:32:28 in 0.22s]: IP: 91.66.233.94 / OK / HTTP status: 200
- [2024-11-05 13:29:25 in 0.21s]: IP: 91.66.233.94 / OK / HTTP status: 200
- [2024-11-05 11:24:26 in 0.22s]: IP: 91.66.233.94 / OK / HTTP status: 200
- [2024-11-05 10:21:58 in 0.21s]: IP: 91.66.233.94 / OK / HTTP status: 200
- [2024-11-05 08:13:25 in 0.23s]: IP: 91.66.233.94 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-11-04 20:49:02 in 0.21s]: IP: 91.66.233.94 / OK / HTTP status: 200
- /nodeinfo/2.1.json ₍⇗₎
- [2024-11-05 22:56:48 in 1.23s]: IP: 91.66.233.94 / OK / HTTP status: 200
- [2024-11-05 21:54:24 in 1.23s]: IP: 91.66.233.94 / OK / HTTP status: 200
- [2024-11-05 20:51:21 in 1.30s]: IP: 91.66.233.94 / OK / HTTP status: 200
- [2024-11-05 19:48:27 in 1.38s]: IP: 91.66.233.94 / OK / HTTP status: 200
- [2024-11-05 17:42:33 in 1.26s]: IP: 91.66.233.94 / OK / HTTP status: 200
- [2024-11-05 14:32:28 in 1.22s]: IP: 91.66.233.94 / OK / HTTP status: 200
- [2024-11-05 13:29:24 in 1.37s]: IP: 91.66.233.94 / OK / HTTP status: 200
- [2024-11-05 11:24:26 in 1.21s]: IP: 91.66.233.94 / OK / HTTP status: 200
- [2024-11-05 10:21:58 in 1.16s]: IP: 91.66.233.94 / OK / HTTP status: 200
- [2024-11-05 08:13:24 in 1.08s]: IP: 91.66.233.94 / OK / HTTP status: 200