techhangout.social — Tech Hangout
Details
up since 2024-07-01 03:13 (16.9 hours ago)
- Uptime: 99.29%
- Users: 11 (2 active this month, 2 active last six months)
- Posts: 7516
- Posts per user: 683.27
- Peers: 9612
- Version: mastodon 4.2.9
- Registrations: Approval Required
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-06-17 22:18 — 2024-07-01 20:01
users: 11 (0.01/day)
min/max/avg/stddev: 9 / 11 / 10.75 / 0.45
posts: 7516 (13.38/day)
min/max/avg/stddev: 3730 / 7516 / 7405.81 / 365.35
peers: 9612 (7.34/day)
min/max/avg/stddev: 7534 / 9612 / 9566.71 / 201.31
response_time: 2.91 (0.01/day)
min/max/avg/stddev: 0 / 61 / 3.98 / 7.22
Crawling Info
First contact: 2023-02-10 (16.7 months ago)
Last successful contact: 2024-07-01 (8.5 minutes ago)
Contact: 21141 successful, 6275 failed.
Average fetch time: 3.98s
Next attempt scheduled for 12.3 minutes from now.
Found through dice.camp (up)
IP address: 172.67.158.3 (and 2 others: mk.plasmatrap.com (down), pixelfed.techhangout.social (up))
Staff
patrice@techhangout.social
I’m an avid podcaster and leader. She/her pronouns. Work as VP in health care software. I love to cook, maintain OS projects, create content,...
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-07-01 18:56:11 in 1.42s]: IP: 104.21.66.88 / Error: http / HTTP status: 403
- [2024-07-01 17:03:18 in 0.00s]: IP: 104.21.66.88 / Error: http / HTTP status: -1
- [2024-07-01 16:40:17 in 0.99s]: IP: 104.21.66.88 / Error: http / HTTP status: 403
- [2024-07-01 15:31:54 in 2.87s]: IP: 172.67.158.3 / Error: http / HTTP status: 403
- [2024-07-01 15:09:54 in 0.00s]: IP: 172.67.158.3 / Error: http / HTTP status: -1
- [2024-07-01 14:46:30 in 0.00s]: IP: 172.67.158.3 / Error: http / HTTP status: -1
- [2024-07-01 13:17:04 in 1.21s]: IP: 172.67.158.3 / Error: http / HTTP status: 403
- [2024-07-01 12:55:23 in 0.00s]: IP: 172.67.158.3 / Error: http / HTTP status: -1
- [2024-07-01 12:33:43 in 1.86s]: IP: 172.67.158.3 / Error: http / HTTP status: 403
- [2024-07-01 11:49:41 in 3.06s]: IP: 172.67.158.3 / Error: http / HTTP status: 403
- /api/v1/instance ₍⇗₎
- [2024-07-01 20:01:42 in 0.27s]: IP: 172.67.158.3 / OK / HTTP status: 200
- [2024-07-01 19:39:29 in 0.23s]: IP: 104.21.66.88 / OK / HTTP status: 200
- [2024-07-01 19:17:48 in 0.24s]: IP: 172.67.158.3 / OK / HTTP status: 200
- [2024-07-01 18:34:56 in 0.22s]: IP: 104.21.66.88 / OK / HTTP status: 200
- [2024-07-01 18:12:22 in 0.21s]: IP: 172.67.158.3 / OK / HTTP status: 200
- [2024-07-01 17:48:22 in 0.22s]: IP: 172.67.158.3 / OK / HTTP status: 200
- [2024-07-01 17:25:07 in 0.21s]: IP: 104.21.66.88 / OK / HTTP status: 200
- [2024-07-01 16:16:30 in 0.22s]: IP: 172.67.158.3 / OK / HTTP status: 200
- [2024-07-01 15:54:09 in 0.22s]: IP: 172.67.158.3 / OK / HTTP status: 200
- [2024-07-01 14:23:06 in 0.22s]: IP: 172.67.158.3 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-07-01 16:16:30 in 0.43s]: IP: 172.67.158.3 / OK / HTTP status: 200
- [2024-07-01 06:29:35 in 0.39s]: IP: 104.21.66.88 / OK / HTTP status: 200
- [2024-06-30 17:46:37 in 0.38s]: IP: 172.67.158.3 / OK / HTTP status: 200
- [2024-06-30 03:27:38 in 0.39s]: IP: 104.21.66.88 / OK / HTTP status: 200
- [2024-06-29 17:58:25 in 0.40s]: IP: 104.21.66.88 / OK / HTTP status: 200
- [2024-06-29 02:32:46 in 0.38s]: IP: 172.67.158.3 / OK / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2024-07-01 20:01:41 in 0.85s]: IP: 172.67.158.3 / OK / HTTP status: 200
- [2024-07-01 19:39:29 in 0.86s]: IP: 104.21.66.88 / OK / HTTP status: 200
- [2024-07-01 19:17:48 in 1.19s]: IP: 172.67.158.3 / OK / HTTP status: 200
- [2024-07-01 18:34:56 in 0.91s]: IP: 104.21.66.88 / OK / HTTP status: 200
- [2024-07-01 18:12:22 in 0.84s]: IP: 172.67.158.3 / OK / HTTP status: 200
- [2024-07-01 17:48:22 in 0.79s]: IP: 172.67.158.3 / OK / HTTP status: 200
- [2024-07-01 17:25:07 in 0.84s]: IP: 104.21.66.88 / OK / HTTP status: 200
- [2024-07-01 16:16:30 in 0.81s]: IP: 172.67.158.3 / OK / HTTP status: 200
- [2024-07-01 15:54:09 in 0.83s]: IP: 172.67.158.3 / OK / HTTP status: 200
- [2024-07-01 14:23:06 in 0.79s]: IP: 172.67.158.3 / OK / HTTP status: 200