social.aviating.com — Aviating.com Social
Details
up since 2023-08-27 05:32 (8.2 months ago)
- Uptime: 99.29%
- Users: 34 (3 active this month, 12 active last six months)
- Posts: 482
- Posts per user: 14.18
- Peers: 9721
- Version: mastodon 4.3.0-alpha.3+glitch
- Registrations: Approval Required
Stats 2024-04-19 00:23 — 2024-05-02 22:26
users: 34 (0.00/day)
min/max/avg/stddev: 34 / 34 / 34.00 / 0.00
⋯ ⋯posts: 482 (0.00/day)
min/max/avg/stddev: 482 / 482 / 482.00 / 0.00
⋯ ⋯peers: 9721 (4.14/day)
min/max/avg/stddev: 9704 / 9721 / 9712.06 / 5.32
response_time: 817.247 (196.88/day)
min/max/avg/stddev: 1 / 817 / 68.04 / 188.35
Crawling Info
First contact: 2022-11-12 (17.7 months ago)
Last successful contact: 2024-05-02 (48.5 minutes ago)
Contact: 26803 successful, 408 failed.
Average fetch time: 68.04s
Next attempt scheduled for 15.1 minutes from now.
Found through mastodon.pirati.cz (up)
IP address: 198.137.202.23
Staff
Mastodon admin contact for social.aviating.com.
AWS Linux developer. Ex Red Hat, SUSE, rPath, NRAO, Transmeta, kernel.org, among others.
Veteran x2. NAPS/USNA/VT/UVa alum. Pilot. Ump. Crazy cat gentleman.
Roanoke, Virginia (by way of Charlottesville, then Richmond)
Typical assassination coördinates: https://flightaware.com/live/flight/N194V
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-05-01 22:48:50 in 0.00s]: IP: 198.137.202.23 / Error: http / HTTP status: -1
- [2024-05-01 17:42:07 in 0.00s]: IP: 198.137.202.23 / Error: http / HTTP status: -1
- [2024-04-30 19:14:35 in 0.00s]: IP: 198.137.202.23 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-05-02 22:26:46 in 0.15s]: IP: 198.137.202.23 / OK / HTTP status: 200
- [2024-05-02 21:22:33 in 0.15s]: IP: 198.137.202.23 / OK / HTTP status: 200
- [2024-05-02 20:18:22 in 0.58s]: IP: 198.137.202.23 / OK / HTTP status: 200
- [2024-05-02 19:15:25 in 0.15s]: IP: 198.137.202.23 / OK / HTTP status: 200
- [2024-05-02 18:11:59 in 0.15s]: IP: 198.137.202.23 / OK / HTTP status: 200
- [2024-05-02 17:09:18 in 0.15s]: IP: 198.137.202.23 / OK / HTTP status: 200
- [2024-05-02 16:07:09 in 0.79s]: IP: 198.137.202.23 / OK / HTTP status: 200
- [2024-05-02 15:04:36 in 1.00s]: IP: 198.137.202.23 / OK / HTTP status: 200
- [2024-05-02 14:02:45 in 1.19s]: IP: 198.137.202.23 / OK / HTTP status: 200
- [2024-05-02 13:01:24 in 0.65s]: IP: 198.137.202.23 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-05-02 16:07:09 in 0.74s]: IP: 198.137.202.23 / OK / HTTP status: 200
- [2024-05-02 04:54:07 in 0.62s]: IP: 198.137.202.23 / OK / HTTP status: 200
- [2024-05-01 18:43:08 in 0.19s]: IP: 198.137.202.23 / OK / HTTP status: 200
- [2024-05-01 07:43:14 in 0.19s]: IP: 198.137.202.23 / OK / HTTP status: 200
- [2024-04-30 18:13:26 in 0.19s]: IP: 198.137.202.23 / OK / HTTP status: 200
- [2024-04-30 09:16:53 in 0.18s]: IP: 198.137.202.23 / OK / HTTP status: 200
- [2024-04-29 23:34:25 in 0.19s]: IP: 198.137.202.23 / OK / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2024-05-02 22:26:46 in 0.51s]: IP: 198.137.202.23 / OK / HTTP status: 200
- [2024-05-02 21:22:33 in 0.47s]: IP: 198.137.202.23 / OK / HTTP status: 200
- [2024-05-02 20:18:22 in 4.14s]: IP: 198.137.202.23 / OK / HTTP status: 200
- [2024-05-02 19:15:25 in 0.51s]: IP: 198.137.202.23 / OK / HTTP status: 200
- [2024-05-02 18:11:59 in 0.44s]: IP: 198.137.202.23 / OK / HTTP status: 200
- [2024-05-02 17:09:18 in 0.44s]: IP: 198.137.202.23 / OK / HTTP status: 200
- [2024-05-02 16:07:09 in 3.49s]: IP: 198.137.202.23 / OK / HTTP status: 200
- [2024-05-02 15:04:36 in 3.05s]: IP: 198.137.202.23 / OK / HTTP status: 200
- [2024-05-02 14:02:45 in 8.87s]: IP: 198.137.202.23 / OK / HTTP status: 200
- [2024-05-02 13:01:24 in 2.17s]: IP: 198.137.202.23 / OK / HTTP status: 200