mastodon.techtriage.guru — Mastodon
Details
up since 2023-10-31 03:35 (8.1 months ago)
- Uptime: 100.00%
- Users: 2 (1 active this month, 2 active last six months)
- Posts: 79
- Posts per user: 39.50
- Peers: 1780
- Version: mastodon 4.2.1
- Registrations: Approval Required
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-06-19 14:35 — 2024-07-03 12:11
users: 2 (0.00/day)
min/max/avg/stddev: 2 / 2 / 2.00 / 0.00
⋯ ⋯posts: 79 (0.15/day)
min/max/avg/stddev: 77 / 79 / 78.95 / 0.32
peers: 1780 (2.26/day)
min/max/avg/stddev: 1749 / 1787 / 1771.55 / 10.54
response_time: 1.962 (-0.15/day)
min/max/avg/stddev: 0 / 15 / 3.55 / 3.77
Crawling Info
First contact: 2023-10-31 (8.1 months ago)
Last successful contact: 2024-07-03 (17.2 minutes ago)
Contact: 14845 successful, 690 failed.
Average fetch time: 3.55s
Next attempt scheduled for 90.5 seconds from now.
Found through the.tonytiger.club (up)
IP address: 139.144.29.31 (and 2 others: pixelfed.techtriage.guru (up), lemmy.techtriage.guru (up))
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-07-03 10:14:29 in 0.00s]: IP: 139.144.29.31 / Error: http / HTTP status: -1
- [2024-07-03 09:55:31 in 0.00s]: IP: 139.144.29.31 / Error: http / HTTP status: -1
- [2024-07-03 09:36:39 in 0.00s]: IP: 139.144.29.31 / Error: http / HTTP status: -1
- [2024-07-03 03:44:35 in 0.00s]: IP: 139.144.29.31 / Error: http / HTTP status: -1
- [2024-07-03 01:46:52 in 0.00s]: IP: 139.144.29.31 / Error: http / HTTP status: -1
- [2024-07-02 23:48:58 in 0.00s]: IP: 139.144.29.31 / Error: http / HTTP status: -1
- [2024-07-02 23:29:24 in 0.00s]: IP: 139.144.29.31 / Error: http / HTTP status: -1
- [2024-07-02 20:32:31 in 0.00s]: IP: 139.144.29.31 / Error: http / HTTP status: -1
- [2024-07-02 17:38:02 in 0.00s]: IP: 139.144.29.31 / Error: http / HTTP status: -1
- [2024-07-02 16:20:47 in 0.00s]: IP: 139.144.29.31 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-07-03 12:11:20 in 0.07s]: IP: 139.144.29.31 / OK / HTTP status: 200
- [2024-07-03 11:51:14 in 0.44s]: IP: 139.144.29.31 / OK / HTTP status: 200
- [2024-07-03 11:31:58 in 0.12s]: IP: 139.144.29.31 / OK / HTTP status: 200
- [2024-07-03 11:12:50 in 0.10s]: IP: 139.144.29.31 / OK / HTTP status: 200
- [2024-07-03 10:53:11 in 0.07s]: IP: 139.144.29.31 / OK / HTTP status: 200
- [2024-07-03 10:33:18 in 0.92s]: IP: 139.144.29.31 / OK / HTTP status: 200
- [2024-07-03 09:17:15 in 0.07s]: IP: 139.144.29.31 / OK / HTTP status: 200
- [2024-07-03 08:57:24 in 0.66s]: IP: 139.144.29.31 / OK / HTTP status: 200
- [2024-07-03 08:38:02 in 0.72s]: IP: 139.144.29.31 / OK / HTTP status: 200
- [2024-07-03 08:18:48 in 0.10s]: IP: 139.144.29.31 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-07-03 06:42:03 in 0.54s]: IP: 139.144.29.31 / OK / HTTP status: 200
- [2024-07-02 22:30:19 in 0.10s]: IP: 139.144.29.31 / OK / HTTP status: 200
- [2024-07-02 13:44:25 in 0.16s]: IP: 139.144.29.31 / OK / HTTP status: 200
- [2024-07-02 05:28:50 in 0.17s]: IP: 139.144.29.31 / OK / HTTP status: 200
- [2024-07-01 17:56:21 in 3.05s]: IP: 139.144.29.31 / OK / HTTP status: 200
- [2024-07-01 06:34:46 in 0.17s]: IP: 139.144.29.31 / OK / HTTP status: 200
- [2024-06-30 21:39:07 in 0.10s]: IP: 139.144.29.31 / OK / HTTP status: 200
- [2024-06-30 13:34:12 in 0.69s]: IP: 139.144.29.31 / OK / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2024-07-03 12:11:20 in 0.20s]: IP: 139.144.29.31 / OK / HTTP status: 200
- [2024-07-03 11:51:14 in 1.72s]: IP: 139.144.29.31 / OK / HTTP status: 200
- [2024-07-03 11:31:58 in 0.39s]: IP: 139.144.29.31 / OK / HTTP status: 200
- [2024-07-03 11:12:50 in 0.41s]: IP: 139.144.29.31 / OK / HTTP status: 200
- [2024-07-03 10:53:11 in 0.21s]: IP: 139.144.29.31 / OK / HTTP status: 200
- [2024-07-03 10:33:18 in 8.26s]: IP: 139.144.29.31 / OK / HTTP status: 200
- [2024-07-03 09:17:15 in 0.31s]: IP: 139.144.29.31 / OK / HTTP status: 200
- [2024-07-03 08:57:24 in 2.53s]: IP: 139.144.29.31 / OK / HTTP status: 200
- [2024-07-03 08:38:02 in 2.83s]: IP: 139.144.29.31 / OK / HTTP status: 200
- [2024-07-03 08:18:48 in 0.53s]: IP: 139.144.29.31 / OK / HTTP status: 200