social.transsafety.network — Trans Safety Network
Details
up since 2024-10-26 21:22 (5.1 days ago)
- Uptime: 99.60%
- Users: 7 (2 active this month, 5 active last six months)
- Posts: 278
- Posts per user: 39.71
- Peers: 6771
- Version: mastodon 4.0.0rc1
- Registrations: Closed
[View Timeline] (← Broken) | [View Timeline Media]
Stats
No successful contact during the given timeframe.
Crawling Info
First contact: 2022-11-08 (23.8 months ago)
Last successful contact: 2024-11-01 (8.4 minutes ago)
Contact: 32035 successful, 8183 failed.
Average fetch time: 2.72s
Next attempt scheduled for 8.6 minutes from now.
Found through social.bckr.me (nxdomain)
IP address: 104.21.17.50 (and social.mlsy.uk.)
Staff
tsn@social.transsafety.network
Monitoring organised harm targeting trans and gender diverse people in the UK.
chican3ry@social.transsafety.network
[No bio.]
[No bio.]
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-10-31 23:00:47 in 0.00s]: IP: 104.21.17.50 / Error: http / HTTP status: -1
- [2024-10-31 22:44:56 in 0.00s]: IP: 172.67.222.80 / Error: http / HTTP status: -1
- [2024-10-31 22:29:14 in 0.00s]: IP: 104.21.17.50 / Error: http / HTTP status: -1
- [2024-10-31 21:57:34 in 0.00s]: IP: 104.21.17.50 / Error: http / HTTP status: -1
- [2024-10-31 20:35:12 in 0.00s]: IP: 104.21.17.50 / Error: http / HTTP status: -1
- [2024-10-31 20:15:21 in 0.00s]: IP: 104.21.17.50 / Error: http / HTTP status: -1
- [2024-10-31 16:10:16 in 0.00s]: IP: 104.21.17.50 / Error: http / HTTP status: -1
- [2024-10-31 15:36:53 in 0.00s]: IP: 104.21.17.50 / Error: http / HTTP status: -1
- [2024-10-31 15:01:12 in 0.00s]: IP: 104.21.17.50 / Error: http / HTTP status: -1
- [2024-10-31 12:54:26 in 0.00s]: IP: 104.21.17.50 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-11-01 00:28:51 in 0.19s]: IP: 104.21.17.50 / OK / HTTP status: 200
- [2024-11-01 00:10:01 in 0.19s]: IP: 172.67.222.80 / OK / HTTP status: 200
- [2024-10-31 23:48:33 in 0.46s]: IP: 104.21.17.50 / OK / HTTP status: 200
- [2024-10-31 23:32:45 in 0.19s]: IP: 104.21.17.50 / OK / HTTP status: 200
- [2024-10-31 23:16:57 in 0.19s]: IP: 172.67.222.80 / OK / HTTP status: 200
- [2024-10-31 22:13:27 in 0.19s]: IP: 172.67.222.80 / OK / HTTP status: 200
- [2024-10-31 21:36:44 in 0.19s]: IP: 172.67.222.80 / OK / HTTP status: 200
- [2024-10-31 21:13:44 in 0.35s]: IP: 104.21.17.50 / OK / HTTP status: 200
- [2024-10-31 20:52:38 in 0.40s]: IP: 172.67.222.80 / OK / HTTP status: 200
- [2024-10-31 19:43:01 in 0.62s]: IP: 172.67.222.80 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-10-31 17:59:02 in 0.34s]: IP: 104.21.17.50 / OK / HTTP status: 200
- [2024-10-31 08:06:36 in 0.38s]: IP: 104.21.17.50 / OK / HTTP status: 200
- [2024-10-30 23:22:34 in 0.31s]: IP: 172.67.222.80 / OK / HTTP status: 200
- [2024-10-30 15:05:38 in 0.34s]: IP: 104.21.17.50 / OK / HTTP status: 200
- [2024-10-30 02:56:29 in 0.50s]: IP: 104.21.17.50 / OK / HTTP status: 200
- [2024-10-29 18:17:39 in 0.37s]: IP: 172.67.222.80 / OK / HTTP status: 200
- [2024-10-29 07:06:04 in 0.34s]: IP: 104.21.17.50 / OK / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2024-11-01 00:28:51 in 0.81s]: IP: 104.21.17.50 / OK / HTTP status: 200
- [2024-11-01 00:10:01 in 0.72s]: IP: 172.67.222.80 / OK / HTTP status: 200
- [2024-10-31 23:48:33 in 1.78s]: IP: 104.21.17.50 / OK / HTTP status: 200
- [2024-10-31 23:32:45 in 0.75s]: IP: 104.21.17.50 / OK / HTTP status: 200
- [2024-10-31 23:16:57 in 0.93s]: IP: 172.67.222.80 / OK / HTTP status: 200
- [2024-10-31 22:13:27 in 0.95s]: IP: 172.67.222.80 / OK / HTTP status: 200
- [2024-10-31 21:36:44 in 0.93s]: IP: 172.67.222.80 / OK / HTTP status: 200
- [2024-10-31 21:13:44 in 1.59s]: IP: 104.21.17.50 / OK / HTTP status: 200
- [2024-10-31 20:52:38 in 2.02s]: IP: 172.67.222.80 / OK / HTTP status: 200
- [2024-10-31 19:43:01 in 3.23s]: IP: 172.67.222.80 / OK / HTTP status: 200