jasdemi.com — Jasdemi
Details
up since 2024-07-01 11:25 (30.2 minutes ago)
- Uptime: 92.87%
- Users: 5 (2 active this month, 2 active last six months)
- Posts: 596
- Posts per user: 119.20
- Peers: 4841
- Version: gotosocial 0.16.1-SNAPSHOT+git-235bea0
- Registrations: Closed
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-06-17 12:33 — 2024-07-01 11:44
users: 5 (0.01/day)
min/max/avg/stddev: 1 / 5 / 4.79 / 0.89
posts: 596 (1.35/day)
min/max/avg/stddev: 212 / 596 / 562.97 / 83.01
peers: 4841 (14.87/day)
min/max/avg/stddev: 623 / 4841 / 4539.36 / 923.54
response_time: 0.624 (0.00/day)
min/max/avg/stddev: 0 / 54 / 3.39 / 5.53
Crawling Info
First contact: 2023-07-02 (12.0 months ago)
Last successful contact: 2024-07-01 (30.2 minutes ago)
Latest attempt: 2024-07-01 (11.3 minutes ago)
Contact: 13349 successful, 5357 failed.
Average fetch time: 3.38s
Next attempt scheduled for 6.6 minutes from now.
Found through libranet.de (down)
IP address: 172.67.146.25 (and phototalk.cafeludwig.com.)
Staff
jasdemi@jasdemi.com
I'm mostly interested in gaming.
Fascinated by the #fediverse.
Self-hosting my #gotosocial instance.
#fedi22
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-07-01 11:44:35 in 0.00s]: IP: 172.67.146.25 / Error: http / HTTP status: -1
- [2024-07-01 11:06:31 in 0.00s]: IP: 104.21.39.139 / Error: http / HTTP status: -1
- [2024-07-01 10:46:05 in 0.00s]: IP: 172.67.146.25 / Error: http / HTTP status: -1
- [2024-07-01 10:26:35 in 2.79s]: IP: 104.21.39.139 / Error: http / HTTP status: 403
- [2024-07-01 10:08:36 in 2.30s]: IP: 104.21.39.139 / Error: http / HTTP status: 403
- [2024-07-01 09:49:47 in 1.02s]: IP: 172.67.146.25 / Error: http / HTTP status: 403
- [2024-07-01 09:29:30 in 1.64s]: IP: 172.67.146.25 / Error: http / HTTP status: 403
- [2024-07-01 09:06:13 in 1.76s]: IP: 104.21.39.139 / Error: http / HTTP status: 403
- [2024-07-01 08:45:13 in 1.30s]: IP: 104.21.39.139 / Error: http / HTTP status: 403
- [2024-07-01 08:23:06 in 1.40s]: IP: 104.21.39.139 / Error: http / HTTP status: 403
- /api/v1/instance ₍⇗₎
- [2024-07-01 11:25:41 in 0.20s]: IP: 104.21.39.139 / OK / HTTP status: 200
- [2024-07-01 08:01:03 in 0.55s]: IP: 172.67.146.25 / OK / HTTP status: 200
- [2024-07-01 07:38:42 in 0.21s]: IP: 172.67.146.25 / OK / HTTP status: 200
- [2024-07-01 06:33:49 in 0.20s]: IP: 104.21.39.139 / OK / HTTP status: 200
- [2024-07-01 06:12:04 in 0.20s]: IP: 104.21.39.139 / OK / HTTP status: 200
- [2024-07-01 05:51:19 in 0.19s]: IP: 104.21.39.139 / OK / HTTP status: 200
- [2024-07-01 05:31:02 in 0.19s]: IP: 172.67.146.25 / OK / HTTP status: 200
- [2024-07-01 05:10:15 in 0.20s]: IP: 104.21.39.139 / OK / HTTP status: 200
- [2024-07-01 04:29:22 in 0.21s]: IP: 104.21.39.139 / OK / HTTP status: 200
- [2024-07-01 03:29:10 in 0.20s]: IP: 104.21.39.139 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-06-30 14:36:17 in 0.18s]: IP: 104.21.39.139 / Error: http / HTTP status: 401
- [2024-06-30 04:24:12 in 0.19s]: IP: 172.67.146.25 / Error: http / HTTP status: 401
- [2024-06-29 16:22:40 in 0.49s]: IP: 172.67.146.25 / Error: http / HTTP status: 401
- [2024-06-29 07:31:06 in 0.19s]: IP: 172.67.146.25 / Error: http / HTTP status: 401
- [2024-06-28 19:05:09 in 0.50s]: IP: 172.67.146.25 / Error: http / HTTP status: 401
- /nodeinfo/2.0 ₍⇗₎
- [2024-07-01 11:25:41 in 0.73s]: IP: 104.21.39.139 / OK / HTTP status: 200
- [2024-07-01 08:01:03 in 2.00s]: IP: 172.67.146.25 / OK / HTTP status: 200
- [2024-07-01 07:38:42 in 0.80s]: IP: 172.67.146.25 / OK / HTTP status: 200
- [2024-07-01 06:33:49 in 0.77s]: IP: 104.21.39.139 / OK / HTTP status: 200
- [2024-07-01 06:12:04 in 0.70s]: IP: 104.21.39.139 / OK / HTTP status: 200
- [2024-07-01 05:51:19 in 0.75s]: IP: 104.21.39.139 / OK / HTTP status: 200
- [2024-07-01 05:31:02 in 0.74s]: IP: 172.67.146.25 / OK / HTTP status: 200
- [2024-07-01 05:10:15 in 0.73s]: IP: 104.21.39.139 / OK / HTTP status: 200
- [2024-07-01 04:29:22 in 0.74s]: IP: 104.21.39.139 / OK / HTTP status: 200
- [2024-07-01 03:29:10 in 0.71s]: IP: 104.21.39.139 / OK / HTTP status: 200