vaughan.social — The Vaughan Social Network
A personal Mastodon instance for the Vaughan family. Our family is large and all are welcome. We strive to be welcoming, inclusive, and respectful.
Details
up since 2024-06-29 09:19 (5.5 hours ago)
- Uptime: 97.90%
- Users: 3 (1 active this month, 2 active last six months)
- Posts: 64
- Posts per user: 21.33
- Peers: 95204
- Version: mastodon 4.2.9
- Registrations: Approval Required
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-06-15 20:50 — 2024-06-29 14:29
users: 3 (0.00/day)
min/max/avg/stddev: 3 / 3 / 3.00 / 0.00
⋯ ⋯posts: 64 (0.00/day)
min/max/avg/stddev: 64 / 64 / 64.00 / 0.00
⋯ ⋯peers: 95204 (5.68/day)
min/max/avg/stddev: 95129 / 95204 / 95166.25 / 23.13
response_time: 2.684 (-0.00/day)
min/max/avg/stddev: 0 / 15 / 3.82 / 3.01
Crawling Info
First contact: 2022-05-27 (25.1 months ago)
Last successful contact: 2024-06-29 (17.8 minutes ago)
Contact: 33824 successful, 14312 failed.
Average fetch time: 3.82s
Next attempt scheduled for 161.1 seconds from now.
Found through twitter.1d4.us (down)
IP address: 172.67.205.250
Staff
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-06-29 14:07:00 in 2.40s]: IP: 104.21.77.89 / Error: http / HTTP status: 403
- [2024-06-29 13:25:05 in 2.52s]: IP: 172.67.205.250 / Error: http / HTTP status: 403
- [2024-06-29 12:42:44 in 2.35s]: IP: 104.21.77.89 / Error: http / HTTP status: 403
- [2024-06-29 12:21:58 in 2.13s]: IP: 172.67.205.250 / Error: http / HTTP status: 403
- [2024-06-29 11:20:30 in 1.78s]: IP: 172.67.205.250 / Error: http / HTTP status: 403
- [2024-06-29 11:00:32 in 1.36s]: IP: 172.67.205.250 / Error: http / HTTP status: 403
- [2024-06-29 10:40:42 in 0.00s]: IP: 172.67.205.250 / Error: http / HTTP status: -1
- [2024-06-29 10:00:19 in 1.90s]: IP: 104.21.77.89 / Error: http / HTTP status: 403
- [2024-06-29 09:40:01 in 2.07s]: IP: 104.21.77.89 / Error: http / HTTP status: 403
- [2024-06-29 08:57:30 in 0.00s]: IP: 104.21.77.89 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-06-29 14:29:32 in 0.17s]: IP: 172.67.205.250 / OK / HTTP status: 200
- [2024-06-29 13:46:13 in 0.14s]: IP: 104.21.77.89 / OK / HTTP status: 200
- [2024-06-29 13:03:54 in 0.17s]: IP: 104.21.77.89 / OK / HTTP status: 200
- [2024-06-29 12:01:33 in 0.26s]: IP: 172.67.205.250 / OK / HTTP status: 200
- [2024-06-29 11:40:40 in 0.28s]: IP: 104.21.77.89 / OK / HTTP status: 200
- [2024-06-29 10:20:32 in 0.26s]: IP: 172.67.205.250 / OK / HTTP status: 200
- [2024-06-29 09:19:56 in 0.20s]: IP: 104.21.77.89 / OK / HTTP status: 200
- [2024-06-29 05:30:58 in 0.26s]: IP: 104.21.77.89 / OK / HTTP status: 200
- [2024-06-29 05:09:23 in 0.14s]: IP: 172.67.205.250 / OK / HTTP status: 200
- [2024-06-29 03:49:09 in 0.16s]: IP: 172.67.205.250 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-06-28 19:31:39 in 0.32s]: IP: 104.21.77.89 / Error: unparseable / HTTP status: 200
- [2024-06-28 08:52:24 in 0.23s]: IP: 104.21.77.89 / Error: unparseable / HTTP status: 200
- [2024-06-27 21:43:22 in 0.33s]: IP: 172.67.205.250 / Error: unparseable / HTTP status: 200
- [2024-06-27 10:30:24 in 0.48s]: IP: 104.21.77.89 / Error: unparseable / HTTP status: 200
- [2024-06-26 21:03:30 in 0.24s]: IP: 104.21.77.89 / Error: unparseable / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2024-06-29 14:29:32 in 0.51s]: IP: 172.67.205.250 / OK / HTTP status: 200
- [2024-06-29 13:46:13 in 0.51s]: IP: 104.21.77.89 / OK / HTTP status: 200
- [2024-06-29 13:03:54 in 0.57s]: IP: 104.21.77.89 / OK / HTTP status: 200
- [2024-06-29 12:01:33 in 0.69s]: IP: 172.67.205.250 / OK / HTTP status: 200
- [2024-06-29 11:40:40 in 0.55s]: IP: 104.21.77.89 / OK / HTTP status: 200
- [2024-06-29 10:20:32 in 0.70s]: IP: 172.67.205.250 / OK / HTTP status: 200
- [2024-06-29 09:19:56 in 0.50s]: IP: 104.21.77.89 / OK / HTTP status: 200
- [2024-06-29 05:30:58 in 0.53s]: IP: 104.21.77.89 / OK / HTTP status: 200
- [2024-06-29 05:09:23 in 0.64s]: IP: 172.67.205.250 / OK / HTTP status: 200
- [2024-06-29 03:49:09 in 0.55s]: IP: 172.67.205.250 / OK / HTTP status: 200