tad.me — Mastodon
Details
up since 2024-09-21 10:47 (57.9 days ago)
- Uptime: 99.87%
- Users: 1 (1 active this month, 1 active last six months)
- Posts: 60
- Posts per user: 60.00
- Peers: 72917
- Version: mastodon 4.3.1
- Registrations: Closed
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-11-04 10:52 — 2024-11-18 08:28
users: 1 (0.00/day)
min/max/avg/stddev: 1 / 1 / 1.00 / 0.00
⋯ ⋯posts: 60 (0.07/day)
min/max/avg/stddev: 59 / 60 / 59.34 / 0.48
peers: 72917 (3.82/day)
min/max/avg/stddev: 72860 / 72918 / 72890.59 / 18.01
response_time: 2.782 (0.09/day)
min/max/avg/stddev: 0 / 13 / 3.00 / 2.08
Crawling Info
First contact: 2022-05-07 (30.4 months ago)
Last successful contact: 2024-11-18 (4.4 minutes ago)
Contact: 57950 successful, 8526 failed.
Average fetch time: 3.00s
Next attempt scheduled for 14.4 minutes from now.
Found through pl.cum.makeup (nxdomain)
IP address: 176.31.213.231 (and 131 others, including: chicken.rodeo (down), orbitalstation.one (up), liberal.city (up), dobremiejsce.robmydobrze.pl (down), lotus-eyes.net (down), pizzahut.systems (down), electricpea.ch (down), matheson.it (down), theotherdell.com (down), cat-b.us (down))
Staff
realtime software engineer, space buff, shutterbug, past JET ESL ALT near Hiroshima, thinks of Tucson as home. Ham callsign W7TAD.
#ispace employee, opinions my own
#space #astronomy #programming #ComputerScience #ai #HamRadio #AmateurRadio #RTOS #photography #anime #ScienceFiction #cats #japan #colorado #linux #mac #legos #fedi22
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-11-18 07:48:54 in 0.00s]: IP: 176.31.213.231 / Error: http / HTTP status: -1
- [2024-11-18 04:31:56 in 0.00s]: IP: 178.33.220.142 / Error: http / HTTP status: -1
- [2024-11-18 02:04:26 in 0.00s]: IP: 178.33.220.142 / Error: http / HTTP status: -1
- [2024-11-18 00:23:26 in 0.00s]: IP: 176.31.213.231 / Error: http / HTTP status: -1
- [2024-11-17 22:26:23 in 0.00s]: IP: 176.31.213.231 / Error: http / HTTP status: -1
- [2024-11-17 22:07:16 in 0.00s]: IP: 178.33.220.142 / Error: http / HTTP status: -1
- [2024-11-17 20:31:06 in 0.00s]: IP: 178.33.220.142 / Error: http / HTTP status: -1
- [2024-11-17 18:15:51 in 0.00s]: IP: 178.33.220.142 / Error: http / HTTP status: -1
- [2024-11-17 17:34:36 in 0.00s]: IP: 178.33.220.142 / Error: http / HTTP status: -1
- [2024-11-17 16:54:57 in 0.00s]: IP: 176.31.213.231 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-11-18 08:28:44 in 0.19s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2024-11-18 08:08:50 in 0.16s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-11-18 07:29:00 in 0.19s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-11-18 07:09:15 in 0.39s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2024-11-18 06:49:11 in 0.37s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-11-18 06:29:30 in 0.19s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2024-11-18 06:10:02 in 0.17s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-11-18 05:50:19 in 0.69s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2024-11-18 05:30:43 in 0.17s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-11-18 05:11:19 in 0.25s]: IP: 178.33.220.142 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-11-18 01:23:48 in 0.24s]: IP: 178.33.220.142 / Error: unparseable / HTTP status: 200
- [2024-11-17 17:14:41 in 0.34s]: IP: 178.33.220.142 / Error: unparseable / HTTP status: 200
- [2024-11-17 04:04:06 in 0.20s]: IP: 178.33.220.142 / Error: unparseable / HTTP status: 200
- [2024-11-16 18:05:27 in 0.42s]: IP: 176.31.213.231 / Error: unparseable / HTTP status: 200
- [2024-11-16 06:33:40 in 0.32s]: IP: 178.33.220.142 / Error: unparseable / HTTP status: 200
- [2024-11-15 20:42:06 in 0.18s]: IP: 176.31.213.231 / Error: unparseable / HTTP status: 200
- [2024-11-15 11:43:41 in 0.18s]: IP: 178.33.220.142 / Error: unparseable / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2024-11-18 08:28:44 in 0.97s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2024-11-18 08:08:50 in 0.98s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-11-18 07:29:00 in 1.03s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-11-18 07:09:15 in 2.33s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2024-11-18 06:49:11 in 5.07s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-11-18 06:29:30 in 0.96s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2024-11-18 06:10:02 in 0.97s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-11-18 05:50:19 in 0.98s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2024-11-18 05:30:43 in 1.13s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-11-18 05:11:19 in 0.96s]: IP: 178.33.220.142 / OK / HTTP status: 200