shonk.reimu.info — Netgear Sharkey
a Sharkey instance that runs on a Netgear r7900p router. it is currently on fire trying to run this fullstack javascript code
Details
up since 2024-07-02 06:18 (27.2 hours ago)
- Uptime: 99.13%
- Users: 2
- Posts: 323
- Posts per user: 161.50
- Peers: 2406
- Version: sharkey 2024.3.2
- Source code: https://activitypub.software/TransFem-org/Sharkey/
- Registrations: Closed
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-06-19 14:28 — 2024-07-03 09:16
users: 2 (0.00/day)
min/max/avg/stddev: 2 / 2 / 2.00 / 0.00
⋯ ⋯posts: 323 (0.00/day)
min/max/avg/stddev: 323 / 323 / 323.00 / 0.00
⋯ ⋯peers: 2406 (7.63/day)
min/max/avg/stddev: 2297 / 2406 / 2351.61 / 31.01
response_time: 2.287 (-0.01/day)
min/max/avg/stddev: 0 / 20 / 3.46 / 3.22
Crawling Info
First contact: 2024-01-21 (5.4 months ago)
Last successful contact: 2024-07-03 (53.7 minutes ago)
Latest attempt: 2024-07-03 (16.1 minutes ago)
Contact: 8986 successful, 3059 failed.
Average fetch time: 3.46s
Next attempt scheduled for 110.9 seconds from now.
Found through makai.chaotic.ninja (up)
IP address: 172.67.217.180 (and stream2.reimu.info.)
Staff
ezio@shonk.reimu.info
I run this instance on a netgear router for no reason other then to torture it for fun time to see if this thing catches on fire alt of @ezio@akko.wtf and @ezio@fedi.reimu.info
I run this instance on a netgear router for no reason other then to torture it for fun time to see if this thing catches on fire alt of @ezio@akko.wtf and @ezio@fedi.reimu.info
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-07-03 09:16:09 in 1.06s]: IP: 172.67.217.180 / Error: http / HTTP status: 403
- [2024-07-03 08:57:16 in 0.91s]: IP: 104.21.45.175 / Error: http / HTTP status: 403
- [2024-07-03 07:41:22 in 0.95s]: IP: 172.67.217.180 / Error: http / HTTP status: 403
- [2024-07-03 06:44:44 in 1.29s]: IP: 104.21.45.175 / Error: http / HTTP status: 403
- [2024-07-03 06:24:34 in 0.00s]: IP: 104.21.45.175 / Error: http / HTTP status: -1
- [2024-07-03 06:04:28 in 2.53s]: IP: 172.67.217.180 / Error: http / HTTP status: 403
- [2024-07-03 05:08:11 in 1.02s]: IP: 172.67.217.180 / Error: http / HTTP status: 403
- [2024-07-03 04:49:33 in 1.22s]: IP: 104.21.45.175 / Error: http / HTTP status: 403
- [2024-07-03 04:12:13 in 1.27s]: IP: 172.67.217.180 / Error: http / HTTP status: 403
- [2024-07-03 03:53:17 in 2.63s]: IP: 104.21.45.175 / Error: http / HTTP status: 403
- /api/v1/instance ₍⇗₎
- [2024-07-03 08:38:31 in 0.59s]: IP: 172.67.217.180 / OK / HTTP status: 200
- [2024-07-03 08:19:39 in 0.79s]: IP: 172.67.217.180 / OK / HTTP status: 200
- [2024-07-03 08:00:38 in 0.79s]: IP: 104.21.45.175 / OK / HTTP status: 200
- [2024-07-03 07:22:27 in 1.35s]: IP: 104.21.45.175 / OK / HTTP status: 200
- [2024-07-03 07:03:41 in 0.70s]: IP: 172.67.217.180 / OK / HTTP status: 200
- [2024-07-03 05:45:27 in 0.85s]: IP: 104.21.45.175 / OK / HTTP status: 200
- [2024-07-03 05:26:47 in 1.00s]: IP: 104.21.45.175 / OK / HTTP status: 200
- [2024-07-03 04:31:01 in 0.78s]: IP: 172.67.217.180 / OK / HTTP status: 200
- [2024-07-03 03:14:32 in 0.86s]: IP: 172.67.217.180 / OK / HTTP status: 200
- [2024-07-03 02:55:03 in 3.51s]: IP: 104.21.45.175 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-07-03 01:39:28 in 0.34s]: IP: 104.21.45.175 / OK / HTTP status: 200
- [2024-07-02 17:28:05 in 0.41s]: IP: 172.67.217.180 / OK / HTTP status: 200
- [2024-07-02 07:33:49 in 0.41s]: IP: 104.21.45.175 / OK / HTTP status: 200
- [2024-07-01 22:24:49 in 0.34s]: IP: 104.21.45.175 / OK / HTTP status: 200
- [2024-07-01 14:22:17 in 0.54s]: IP: 172.67.217.180 / OK / HTTP status: 200
- [2024-07-01 05:53:33 in 0.65s]: IP: 104.21.45.175 / OK / HTTP status: 200
- [2024-06-30 20:48:33 in 0.69s]: IP: 104.21.45.175 / OK / HTTP status: 200
- [2024-06-30 10:07:22 in 0.39s]: IP: 172.67.217.180 / OK / HTTP status: 200
- /nodeinfo/2.1 ₍⇗₎
- [2024-07-03 08:38:31 in 0.65s]: IP: 172.67.217.180 / OK / HTTP status: 200
- [2024-07-03 08:19:39 in 0.33s]: IP: 172.67.217.180 / OK / HTTP status: 200
- [2024-07-03 08:00:38 in 0.66s]: IP: 104.21.45.175 / OK / HTTP status: 200
- [2024-07-03 07:22:27 in 0.38s]: IP: 104.21.45.175 / OK / HTTP status: 200
- [2024-07-03 07:03:41 in 0.55s]: IP: 172.67.217.180 / OK / HTTP status: 200
- [2024-07-03 05:45:27 in 0.42s]: IP: 104.21.45.175 / OK / HTTP status: 200
- [2024-07-03 05:26:47 in 0.50s]: IP: 104.21.45.175 / OK / HTTP status: 200
- [2024-07-03 04:31:01 in 0.52s]: IP: 172.67.217.180 / OK / HTTP status: 200
- [2024-07-03 03:14:32 in 5.04s]: IP: 172.67.217.180 / OK / HTTP status: 200
- [2024-07-03 02:55:03 in 0.74s]: IP: 104.21.45.175 / OK / HTTP status: 200