tylernguyen.social — tylernguyen's m
Details
up since 2024-09-19 22:04 (46.0 days ago)
- Uptime: 97.69%
- Users: 1 (1 active this month, 1 active last six months)
- Posts: 0
- Posts per user: 0.00
- Peers: 3802
- Version: mastodon 4.3.1
- Registrations: Invite
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-10-22 19:56 — 2024-11-04 21:58
users: 1 (0.00/day)
min/max/avg/stddev: 1 / 1 / 1.00 / 0.00
⋯ ⋯posts: 0 (0.00/day)
min/max/avg/stddev: 0 / 0 / 0.00 / 0.00
⋯ ⋯peers: 3802 (3.68/day)
min/max/avg/stddev: 3751 / 3802 / 3776.18 / 15.32
response_time: 4.803 (0.00/day)
min/max/avg/stddev: 0 / 5 / 1.97 / 1.22
Crawling Info
First contact: 2023-10-03 (13.1 months ago)
Last successful contact: 2024-11-04 (13.1 minutes ago)
Contact: 30232 successful, 8655 failed.
Average fetch time: 1.97s
Next attempt scheduled for 116.9 seconds from now.
Found through social.treehouse.systems (up)
IP address: 104.21.60.190 (and fakerelay.tylernguyen.social.)
Staff
tylernguyen@tylernguyen.social
[No bio.]
[No bio.]
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-11-04 21:11:15 in 0.00s]: IP: 104.21.60.190 / Error: http / HTTP status: -1
- [2024-11-04 20:22:34 in 0.00s]: IP: 104.21.60.190 / Error: http / HTTP status: -1
- [2024-11-04 19:14:21 in 0.00s]: IP: 172.67.200.60 / Error: http / HTTP status: -1
- [2024-11-04 18:09:14 in 0.00s]: IP: 172.67.200.60 / Error: http / HTTP status: -1
- [2024-11-04 16:32:05 in 0.00s]: IP: 104.21.60.190 / Error: http / HTTP status: -1
- [2024-11-04 14:55:43 in 0.00s]: IP: 104.21.60.190 / Error: http / HTTP status: -1
- [2024-11-04 13:51:58 in 0.00s]: IP: 104.21.60.190 / Error: http / HTTP status: -1
- [2024-11-04 13:03:23 in 0.00s]: IP: 172.67.200.60 / Error: http / HTTP status: -1
- [2024-11-04 12:47:12 in 0.00s]: IP: 172.67.200.60 / Error: http / HTTP status: -1
- [2024-11-04 11:59:04 in 0.00s]: IP: 104.21.60.190 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-11-04 21:58:36 in 0.64s]: IP: 104.21.60.190 / OK / HTTP status: 200
- [2024-11-04 21:42:53 in 0.10s]: IP: 104.21.60.190 / OK / HTTP status: 200
- [2024-11-04 21:27:08 in 0.53s]: IP: 172.67.200.60 / OK / HTTP status: 200
- [2024-11-04 20:55:39 in 0.13s]: IP: 172.67.200.60 / OK / HTTP status: 200
- [2024-11-04 20:39:42 in 0.11s]: IP: 172.67.200.60 / OK / HTTP status: 200
- [2024-11-04 20:05:18 in 0.61s]: IP: 172.67.200.60 / OK / HTTP status: 200
- [2024-11-04 19:47:38 in 0.13s]: IP: 104.21.60.190 / OK / HTTP status: 200
- [2024-11-04 19:31:04 in 0.13s]: IP: 104.21.60.190 / OK / HTTP status: 200
- [2024-11-04 18:58:02 in 0.12s]: IP: 104.21.60.190 / OK / HTTP status: 200
- [2024-11-04 18:41:19 in 0.70s]: IP: 172.67.200.60 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-11-04 21:58:36 in 0.55s]: IP: 104.21.60.190 / OK / HTTP status: 200
- [2024-11-04 11:24:06 in 0.12s]: IP: 104.21.60.190 / OK / HTTP status: 200
- [2024-11-04 02:38:43 in 0.12s]: IP: 172.67.200.60 / OK / HTTP status: 200
- [2024-11-03 18:33:53 in 0.10s]: IP: 172.67.200.60 / OK / HTTP status: 200
- [2024-11-03 10:18:58 in 0.56s]: IP: 104.21.60.190 / OK / HTTP status: 200
- [2024-11-03 00:59:08 in 0.13s]: IP: 172.67.200.60 / OK / HTTP status: 200
- [2024-11-02 15:57:19 in 0.09s]: IP: 104.21.60.190 / OK / HTTP status: 200
- [2024-11-02 07:32:23 in 0.10s]: IP: 172.67.200.60 / OK / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2024-11-04 21:58:35 in 2.22s]: IP: 104.21.60.190 / OK / HTTP status: 200
- [2024-11-04 21:42:53 in 0.37s]: IP: 104.21.60.190 / OK / HTTP status: 200
- [2024-11-04 21:27:08 in 2.27s]: IP: 172.67.200.60 / OK / HTTP status: 200
- [2024-11-04 20:55:39 in 0.57s]: IP: 172.67.200.60 / OK / HTTP status: 200
- [2024-11-04 20:39:42 in 0.37s]: IP: 172.67.200.60 / OK / HTTP status: 200
- [2024-11-04 20:05:18 in 2.70s]: IP: 172.67.200.60 / OK / HTTP status: 200
- [2024-11-04 19:47:38 in 0.46s]: IP: 104.21.60.190 / OK / HTTP status: 200
- [2024-11-04 19:31:04 in 0.43s]: IP: 104.21.60.190 / OK / HTTP status: 200
- [2024-11-04 18:58:02 in 0.42s]: IP: 104.21.60.190 / OK / HTTP status: 200
- [2024-11-04 18:41:19 in 2.19s]: IP: 172.67.200.60 / OK / HTTP status: 200