social.tgj.services — TGJ Social
Details
up since 2024-06-27 03:31 (55.4 hours ago)
- Uptime: 97.63%
- Users: 5 (1 active this month, 2 active last six months)
- Posts: 10
- Posts per user: 2.00
- Peers: 1612
- Version: mastodon 4.2.9
- Registrations: Closed
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-06-16 10:34 — 2024-06-29 10:01
users: 5 (0.00/day)
min/max/avg/stddev: 5 / 5 / 5.00 / 0.00
⋯ ⋯posts: 10 (0.00/day)
min/max/avg/stddev: 10 / 10 / 10.00 / 0.00
⋯ ⋯peers: 1612 (0.60/day)
min/max/avg/stddev: 1603 / 1612 / 1607.33 / 2.98
response_time: 90.977 (-0.97/day)
min/max/avg/stddev: 2 / 105 / 60.81 / 32.48
Crawling Info
First contact: 2023-04-26 (14.1 months ago)
Last successful contact: 2024-06-29 (3.0 hours ago)
Latest attempt: 2024-06-29 (56.5 minutes ago)
Contact: 11150 successful, 1719 failed.
Average fetch time: 60.81s
Next attempt scheduled for 6.1 minutes from now.
Found through meld.de (down)
IP address: 82.215.64.69
Staff
Jack@social.tgj.services
Network Engineer
Matrix: @Jack:matrix.tgj.services
https://thatguyjack.co.uk/
http://thatguyjack.co.uk/discord
http://[2a12:bec0:214::b00b]/
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-06-29 10:01:25 in 0.00s]: IP: 82.215.64.69 / Error: http / HTTP status: -1
- [2024-06-29 08:57:58 in 0.00s]: IP: 82.215.64.69 / Error: http / HTTP status: -1
- [2024-06-29 02:57:26 in 0.00s]: IP: 82.215.64.69 / Error: http / HTTP status: -1
- [2024-06-28 23:51:27 in 0.00s]: IP: 82.215.64.69 / Error: http / HTTP status: -1
- [2024-06-28 22:47:47 in 0.00s]: IP: 82.215.64.69 / Error: http / HTTP status: -1
- [2024-06-28 21:44:07 in 0.00s]: IP: 82.215.64.69 / Error: http / HTTP status: -1
- [2024-06-28 19:39:39 in 0.00s]: IP: 82.215.64.69 / Error: http / HTTP status: -1
- [2024-06-28 18:36:55 in 0.00s]: IP: 82.215.64.69 / Error: http / HTTP status: -1
- [2024-06-28 11:28:11 in 0.00s]: IP: 82.215.64.69 / Error: http / HTTP status: -1
- [2024-06-28 10:24:46 in 0.00s]: IP: 82.215.64.69 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-06-29 07:56:32 in 0.21s]: IP: 82.215.64.69 / OK / HTTP status: 200
- [2024-06-29 06:57:31 in 0.25s]: IP: 82.215.64.69 / OK / HTTP status: 200
- [2024-06-29 05:58:25 in 0.21s]: IP: 82.215.64.69 / OK / HTTP status: 200
- [2024-06-29 04:58:24 in 0.22s]: IP: 82.215.64.69 / OK / HTTP status: 200
- [2024-06-29 03:58:24 in 0.24s]: IP: 82.215.64.69 / OK / HTTP status: 200
- [2024-06-29 01:57:11 in 0.31s]: IP: 82.215.64.69 / OK / HTTP status: 200
- [2024-06-29 00:54:52 in 0.21s]: IP: 82.215.64.69 / OK / HTTP status: 200
- [2024-06-28 20:42:26 in 0.21s]: IP: 82.215.64.69 / OK / HTTP status: 200
- [2024-06-28 17:35:45 in 0.41s]: IP: 82.215.64.69 / OK / HTTP status: 200
- [2024-06-28 16:35:13 in 0.26s]: IP: 82.215.64.69 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-06-27 22:44:26 in 0.16s]: IP: 82.215.64.69 / OK / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2024-06-29 07:56:32 in 0.66s]: IP: 82.215.64.69 / OK / HTTP status: 200
- [2024-06-29 06:57:31 in 0.66s]: IP: 82.215.64.69 / OK / HTTP status: 200
- [2024-06-29 05:58:25 in 0.73s]: IP: 82.215.64.69 / OK / HTTP status: 200
- [2024-06-29 04:58:24 in 0.68s]: IP: 82.215.64.69 / OK / HTTP status: 200
- [2024-06-29 03:58:24 in 0.73s]: IP: 82.215.64.69 / OK / HTTP status: 200
- [2024-06-29 01:57:11 in 0.71s]: IP: 82.215.64.69 / OK / HTTP status: 200
- [2024-06-29 00:54:52 in 0.67s]: IP: 82.215.64.69 / OK / HTTP status: 200
- [2024-06-28 20:42:26 in 0.69s]: IP: 82.215.64.69 / OK / HTTP status: 200
- [2024-06-28 17:35:45 in 0.82s]: IP: 82.215.64.69 / OK / HTTP status: 200
- [2024-06-28 16:35:13 in 0.62s]: IP: 82.215.64.69 / OK / HTTP status: 200