glitch.hanntac.net — Mastodon Glitch Edition
Details
up since 2024-06-10 14:19 (3.2 months ago)
- Uptime: 99.29%
- Users: 2 (2 active this month, 2 active last six months)
- Posts: 303
- Posts per user: 151.50
- Peers: 3932
- Version: mastodon 4.3.0-nightly.2024-02-10+glitch
- Registrations: Invite
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-09-03 00:37 — 2024-09-16 19:06
users: 2 (0.00/day)
min/max/avg/stddev: 2 / 2 / 2.00 / 0.00
⋯ ⋯posts: 303 (-0.70/day)
min/max/avg/stddev: 303 / 313 / 309.33 / 3.06
peers: 3932 (4.21/day)
min/max/avg/stddev: 3872 / 3932 / 3905.95 / 17.57
response_time: 1.599 (-0.10/day)
min/max/avg/stddev: 0 / 61 / 3.57 / 7.21
Crawling Info
First contact: 2024-02-11 (7.2 months ago)
Last successful contact: 2024-09-16 (6.3 minutes ago)
Contact: 19340 successful, 1395 failed.
Average fetch time: 3.57s
Next attempt scheduled for 15.7 minutes from now.
Found through mastodon.cgx.me (up)
IP address: 51.75.140.78 (and 2 others: social.hanntac.net (up), ounse.hanntac.net (up))
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-09-16 18:44:07 in 0.00s]: IP: 51.75.140.78 / Error: http / HTTP status: -1
- [2024-09-16 18:21:13 in 0.00s]: IP: 51.75.140.78 / Error: http / HTTP status: -1
- [2024-09-16 17:58:35 in 0.00s]: IP: 51.75.140.78 / Error: http / HTTP status: -1
- [2024-09-16 15:17:54 in 0.00s]: IP: 51.75.140.78 / Error: http / HTTP status: -1
- [2024-09-16 13:23:37 in 0.00s]: IP: 51.75.140.78 / Error: http / HTTP status: -1
- [2024-09-16 13:01:13 in 0.00s]: IP: 51.75.140.78 / Error: http / HTTP status: -1
- [2024-09-16 12:38:48 in 0.00s]: IP: 51.75.140.78 / Error: http / HTTP status: -1
- [2024-09-16 12:16:25 in 0.00s]: IP: 51.75.140.78 / Error: http / HTTP status: -1
- [2024-09-16 11:53:57 in 0.00s]: IP: 51.75.140.78 / Error: http / HTTP status: -1
- [2024-09-16 10:46:22 in 0.00s]: IP: 51.75.140.78 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-09-16 19:06:57 in 0.24s]: IP: 51.75.140.78 / OK / HTTP status: 200
- [2024-09-16 17:35:31 in 0.19s]: IP: 51.75.140.78 / OK / HTTP status: 200
- [2024-09-16 17:12:41 in 0.23s]: IP: 51.75.140.78 / OK / HTTP status: 200
- [2024-09-16 16:49:37 in 0.43s]: IP: 51.75.140.78 / OK / HTTP status: 200
- [2024-09-16 16:26:41 in 0.67s]: IP: 51.75.140.78 / OK / HTTP status: 200
- [2024-09-16 16:03:52 in 0.36s]: IP: 51.75.140.78 / OK / HTTP status: 200
- [2024-09-16 15:40:58 in 0.24s]: IP: 51.75.140.78 / OK / HTTP status: 200
- [2024-09-16 14:55:00 in 0.35s]: IP: 51.75.140.78 / OK / HTTP status: 200
- [2024-09-16 14:32:10 in 0.17s]: IP: 51.75.140.78 / OK / HTTP status: 200
- [2024-09-16 14:09:13 in 0.23s]: IP: 51.75.140.78 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-09-16 16:03:52 in 0.18s]: IP: 51.75.140.78 / OK / HTTP status: 200
- [2024-09-16 07:20:48 in 0.19s]: IP: 51.75.140.78 / OK / HTTP status: 200
- [2024-09-15 21:12:26 in 0.20s]: IP: 51.75.140.78 / OK / HTTP status: 200
- [2024-09-15 12:52:37 in 0.24s]: IP: 51.75.140.78 / OK / HTTP status: 200
- [2024-09-15 03:25:12 in 0.42s]: IP: 51.75.140.78 / OK / HTTP status: 200
- [2024-09-14 17:05:17 in 0.16s]: IP: 51.75.140.78 / OK / HTTP status: 200
- [2024-09-14 08:25:46 in 0.18s]: IP: 51.75.140.78 / OK / HTTP status: 200
- [2024-09-13 22:12:33 in 0.18s]: IP: 51.75.140.78 / OK / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2024-09-16 19:06:57 in 1.07s]: IP: 51.75.140.78 / OK / HTTP status: 200
- [2024-09-16 17:35:31 in 1.04s]: IP: 51.75.140.78 / OK / HTTP status: 200
- [2024-09-16 17:12:41 in 0.63s]: IP: 51.75.140.78 / OK / HTTP status: 200
- [2024-09-16 16:49:37 in 1.01s]: IP: 51.75.140.78 / OK / HTTP status: 200
- [2024-09-16 16:26:41 in 0.64s]: IP: 51.75.140.78 / OK / HTTP status: 200
- [2024-09-16 16:03:52 in 0.65s]: IP: 51.75.140.78 / OK / HTTP status: 200
- [2024-09-16 15:40:58 in 1.04s]: IP: 51.75.140.78 / OK / HTTP status: 200
- [2024-09-16 14:55:00 in 1.05s]: IP: 51.75.140.78 / OK / HTTP status: 200
- [2024-09-16 14:32:10 in 0.72s]: IP: 51.75.140.78 / OK / HTTP status: 200
- [2024-09-16 14:09:12 in 0.92s]: IP: 51.75.140.78 / OK / HTTP status: 200