social.trans.gg — TransGG Social
A TransGG Sharkey Instance - Invite only for now <3
Details
up since 2024-06-25 01:57 (36.4 hours ago)
- Uptime: 99.07%
- Users: 3
- Posts: 1
- Posts per user: 0.33
- Peers: 10
- Version: sharkey 2024.3.3
- Source code: https://activitypub.software/TransFem-org/Sharkey/
- Registrations: Closed
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-06-13 02:47 — 2024-06-26 14:06
users: 3 (0.00/day)
min/max/avg/stddev: 3 / 3 / 3.00 / 0.00
⋯ —posts: 1 (0.00/day)
min/max/avg/stddev: 1 / 1 / 1.00 / 0.00
⋯ —peers: 10 (0.33/day)
min/max/avg/stddev: 9 / 10 / 9.50 / 0.50
—response_time: 3.711 (-0.03/day)
min/max/avg/stddev: 3 / 3 / 3.76 / 0.05
—
Crawling Info
First contact: 2024-06-07 (19.6 days ago)
Last successful contact: 2024-06-26 (12.3 minutes ago)
Contact: 1577 successful, 665 failed.
Average fetch time: 3.76s
Next attempt scheduled for 7.0 minutes from now.
Found through transfem.social (up)
IP address: 172.67.212.53 (and eeruwang.me.)
Staff
TransGG@social.trans.gg
Admin account for social.trans.gg
Admin account for social.trans.gg
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-06-26 13:06:16 in 2.11s]: IP: 172.67.212.53 / Error: http / HTTP status: 403
- [2024-06-26 11:43:55 in 2.55s]: IP: 104.21.69.192 / Error: http / HTTP status: 403
- [2024-06-26 11:09:57 in 0.00s]: IP: 172.67.212.53 / Error: http / HTTP status: -1
- [2024-06-26 10:54:25 in 0.00s]: IP: 172.67.212.53 / Error: http / HTTP status: -1
- [2024-06-26 10:38:29 in 0.00s]: IP: 172.67.212.53 / Error: http / HTTP status: -1
- [2024-06-26 09:19:38 in 1.68s]: IP: 172.67.212.53 / Error: http / HTTP status: 403
- [2024-06-26 08:23:02 in 1.31s]: IP: 172.67.212.53 / Error: http / HTTP status: 403
- [2024-06-26 07:29:22 in 1.03s]: IP: 172.67.212.53 / Error: http / HTTP status: 403
- [2024-06-26 06:51:16 in 1.29s]: IP: 172.67.212.53 / Error: http / HTTP status: 403
- [2024-06-26 06:08:49 in 1.24s]: IP: 104.21.69.192 / Error: http / HTTP status: 403
- /api/v1/instance ₍⇗₎
- [2024-06-26 14:06:47 in 0.58s]: IP: 172.67.212.53 / OK / HTTP status: 200
- [2024-06-26 13:45:57 in 0.87s]: IP: 104.21.69.192 / OK / HTTP status: 200
- [2024-06-26 13:26:16 in 0.66s]: IP: 104.21.69.192 / OK / HTTP status: 200
- [2024-06-26 12:45:36 in 0.66s]: IP: 104.21.69.192 / OK / HTTP status: 200
- [2024-06-26 12:24:40 in 0.58s]: IP: 172.67.212.53 / OK / HTTP status: 200
- [2024-06-26 12:04:50 in 0.69s]: IP: 172.67.212.53 / OK / HTTP status: 200
- [2024-06-26 11:25:38 in 1.59s]: IP: 172.67.212.53 / OK / HTTP status: 200
- [2024-06-26 10:17:09 in 1.54s]: IP: 172.67.212.53 / OK / HTTP status: 200
- [2024-06-26 09:57:02 in 0.49s]: IP: 104.21.69.192 / OK / HTTP status: 200
- [2024-06-26 09:38:25 in 0.61s]: IP: 172.67.212.53 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-06-26 09:57:02 in 0.19s]: IP: 104.21.69.192 / OK / HTTP status: 200
- [2024-06-26 01:32:42 in 0.20s]: IP: 172.67.212.53 / OK / HTTP status: 200
- [2024-06-25 16:21:12 in 0.21s]: IP: 172.67.212.53 / OK / HTTP status: 200
- [2024-06-24 12:03:35 in 0.20s]: IP: 104.21.69.192 / OK / HTTP status: 200
- [2024-06-24 02:38:44 in 0.20s]: IP: 104.21.69.192 / OK / HTTP status: 200
- [2024-06-23 16:22:26 in 0.20s]: IP: 104.21.69.192 / OK / HTTP status: 200
- /nodeinfo/2.1 ₍⇗₎
- [2024-06-26 14:06:47 in 0.80s]: IP: 172.67.212.53 / OK / HTTP status: 200
- [2024-06-26 13:45:57 in 1.09s]: IP: 104.21.69.192 / OK / HTTP status: 200
- [2024-06-26 13:26:16 in 0.87s]: IP: 104.21.69.192 / OK / HTTP status: 200
- [2024-06-26 12:45:36 in 0.91s]: IP: 104.21.69.192 / OK / HTTP status: 200
- [2024-06-26 12:24:40 in 0.80s]: IP: 172.67.212.53 / OK / HTTP status: 200
- [2024-06-26 12:04:50 in 0.95s]: IP: 172.67.212.53 / OK / HTTP status: 200
- [2024-06-26 11:25:38 in 0.84s]: IP: 172.67.212.53 / OK / HTTP status: 200
- [2024-06-26 10:17:09 in 0.82s]: IP: 172.67.212.53 / OK / HTTP status: 200
- [2024-06-26 09:57:02 in 0.82s]: IP: 104.21.69.192 / OK / HTTP status: 200
- [2024-06-26 09:38:25 in 0.81s]: IP: 172.67.212.53 / OK / HTTP status: 200