grafton.me — Mastodon
Details
up since 2024-06-10 15:52 (22.9 days ago)
- Uptime: 99.78%
- Users: 1 (1 active this month, 1 active last six months)
- Posts: 21
- Posts per user: 21.00
- Peers: 10310
- Version: mastodon 4.2.9
- Registrations: Invite
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-06-19 14:39 — 2024-07-03 13:03
users: 1 (0.00/day)
min/max/avg/stddev: 1 / 1 / 1.00 / 0.00
⋯ ⋯posts: 21 (-0.02/day)
min/max/avg/stddev: 21 / 28 / 22.53 / 1.70
peers: 10310 (7.83/day)
min/max/avg/stddev: 8074 / 10310 / 10054.99 / 635.03
response_time: 2.31 (0.00/day)
min/max/avg/stddev: 0 / 17 / 3.42 / 3.73
Crawling Info
First contact: 2022-11-15 (19.6 months ago)
Last successful contact: 2024-07-03 (7.0 minutes ago)
Contact: 33091 successful, 825 failed.
Average fetch time: 3.42s
Next attempt scheduled for 10.7 minutes from now.
Found through f.haeder.net (down)
IP address: 174.138.116.250
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-07-03 03:45:41 in 0.00s]: IP: 174.138.116.250 / Error: http / HTTP status: -1
- [2024-07-03 02:12:56 in 0.00s]: IP: 174.138.116.250 / Error: http / HTTP status: -1
- [2024-07-03 00:23:50 in 0.00s]: IP: 174.138.116.250 / Error: http / HTTP status: -1
- [2024-07-03 00:05:41 in 0.00s]: IP: 174.138.116.250 / Error: http / HTTP status: -1
- [2024-07-02 20:48:08 in 0.00s]: IP: 174.138.116.250 / Error: http / HTTP status: -1
- [2024-07-02 14:31:13 in 0.00s]: IP: 174.138.116.250 / Error: http / HTTP status: -1
- [2024-07-02 11:10:16 in 0.00s]: IP: 174.138.116.250 / Error: http / HTTP status: -1
- [2024-07-02 10:17:10 in 0.00s]: IP: 174.138.116.250 / Error: http / HTTP status: -1
- [2024-07-02 09:59:21 in 0.00s]: IP: 174.138.116.250 / Error: http / HTTP status: -1
- [2024-07-02 04:19:45 in 0.00s]: IP: 174.138.116.250 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-07-03 13:03:46 in 0.46s]: IP: 174.138.116.250 / OK / HTTP status: 200
- [2024-07-03 12:45:34 in 0.11s]: IP: 174.138.116.250 / OK / HTTP status: 200
- [2024-07-03 12:27:13 in 0.10s]: IP: 174.138.116.250 / OK / HTTP status: 200
- [2024-07-03 12:08:10 in 0.13s]: IP: 174.138.116.250 / OK / HTTP status: 200
- [2024-07-03 11:48:39 in 1.46s]: IP: 174.138.116.250 / OK / HTTP status: 200
- [2024-07-03 11:29:56 in 0.10s]: IP: 174.138.116.250 / OK / HTTP status: 200
- [2024-07-03 11:11:18 in 0.11s]: IP: 174.138.116.250 / OK / HTTP status: 200
- [2024-07-03 10:52:50 in 0.09s]: IP: 174.138.116.250 / OK / HTTP status: 200
- [2024-07-03 10:34:26 in 0.59s]: IP: 174.138.116.250 / OK / HTTP status: 200
- [2024-07-03 10:16:22 in 0.08s]: IP: 174.138.116.250 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-07-03 12:08:10 in 0.08s]: IP: 174.138.116.250 / OK / HTTP status: 200
- [2024-07-03 03:26:42 in 0.47s]: IP: 174.138.116.250 / OK / HTTP status: 200
- [2024-07-02 18:59:34 in 0.90s]: IP: 174.138.116.250 / OK / HTTP status: 200
- [2024-07-02 09:06:02 in 0.08s]: IP: 174.138.116.250 / OK / HTTP status: 200
- [2024-07-02 00:07:51 in 0.96s]: IP: 174.138.116.250 / OK / HTTP status: 200
- [2024-07-01 15:55:41 in 0.85s]: IP: 174.138.116.250 / OK / HTTP status: 200
- [2024-07-01 05:29:47 in 0.08s]: IP: 174.138.116.250 / OK / HTTP status: 200
- [2024-06-30 18:46:35 in 1.73s]: IP: 174.138.116.250 / OK / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2024-07-03 13:03:46 in 1.45s]: IP: 174.138.116.250 / OK / HTTP status: 200
- [2024-07-03 12:45:34 in 0.34s]: IP: 174.138.116.250 / OK / HTTP status: 200
- [2024-07-03 12:27:13 in 0.40s]: IP: 174.138.116.250 / OK / HTTP status: 200
- [2024-07-03 12:08:10 in 0.44s]: IP: 174.138.116.250 / OK / HTTP status: 200
- [2024-07-03 11:48:39 in 4.70s]: IP: 174.138.116.250 / OK / HTTP status: 200
- [2024-07-03 11:29:56 in 0.31s]: IP: 174.138.116.250 / OK / HTTP status: 200
- [2024-07-03 11:11:18 in 0.31s]: IP: 174.138.116.250 / OK / HTTP status: 200
- [2024-07-03 10:52:50 in 0.39s]: IP: 174.138.116.250 / OK / HTTP status: 200
- [2024-07-03 10:34:26 in 3.06s]: IP: 174.138.116.250 / OK / HTTP status: 200
- [2024-07-03 10:16:22 in 0.30s]: IP: 174.138.116.250 / OK / HTTP status: 200