mastodon.gatewayy.net — Mastodon.Gatewayy. Net
Details
up since 2024-12-03 02:11 (83.3 days ago)
- Uptime: 99.77%
- Users: 3 (2 active this month, 3 active last six months)
- Posts: 2821
- Posts per user: 940.33
- Peers: 16357
- Version: mastodon 4.3.3
- Registrations: Invite
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2025-02-22 18:49 — 2025-02-24 08:38
users: 3 (0.00/day)
min/max/avg/stddev: 3 / 3 / 3.00 / 0.00
⋯ ⋯posts: 2821 (-0.63/day)
min/max/avg/stddev: 2821 / 2822 / 2821.78 / 0.42
peers: 16357 (20.30/day)
min/max/avg/stddev: 16325 / 16357 / 16341.44 / 11.20
response_time: 1.95 (-2.55/day)
min/max/avg/stddev: 1 / 5 / 2.96 / 1.26
Crawling Info
First contact: 2023-02-09 (24.5 months ago)
Last successful contact: 2025-02-24 (56.8 minutes ago)
Contact: 44648 successful, 4319 failed.
Average fetch time: 2.96s
Next attempt scheduled for 34.4 minutes ago.
Found through dnsimple.social (up)
IP address: 54.38.247.97 (and 1039 others, including: mastodon.matthewmcvickar.com (up), mastodon.heiperlan.de (down), social.kistler.dev (down), social.cereza.de (down), social.postninja.net (down), social.goldenhillsoftware.com (down), freunde.nettesheim.eu (down), mastodon.goroundtrip.co (up), masto.a15a.co (down), social.pixels.pizza (down))
Staff

I guess I’m “middle aged” now even though I still feel like I’m 25 inside my brain. I’m a life long techie and geek that used to be a Systems Engineer for the Bass Pro Shops and Cabelas websites.
- ☕ Enthusiastic consumer of Coffee.
- 📱 Wannabe gadget hoarder.
- 💻Tech / Cyber Security Enthusiast.
- :docker: UNRAID / Docker / Container Enthusiast.
- 📊 Analytics nerd.
- 🎧 Voracious consumer of podcasts / Audio Books.
Formally @Gatewayy. Also, I am searchable.
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2025-02-24 03:01:52 in 0.00s]: IP: 54.38.247.97 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2025-02-24 08:38:59 in 0.19s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2025-02-24 06:53:59 in 0.19s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2025-02-24 05:10:47 in 0.18s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2025-02-24 00:24:11 in 0.36s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2025-02-23 22:11:08 in 0.19s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2025-02-23 19:44:57 in 0.19s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2025-02-23 17:03:25 in 0.19s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2025-02-23 14:18:46 in 0.19s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2025-02-23 11:28:14 in 0.19s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2025-02-23 08:34:48 in 0.44s]: IP: 54.38.247.97 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2025-02-24 06:53:59 in 0.18s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2025-02-23 17:03:25 in 0.17s]: IP: 54.38.247.97 / OK / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2025-02-24 08:38:59 in 1.10s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2025-02-24 06:53:59 in 1.08s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2025-02-24 05:10:47 in 1.11s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2025-02-24 00:24:11 in 2.91s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2025-02-23 22:11:08 in 1.09s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2025-02-23 19:44:57 in 1.08s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2025-02-23 17:03:25 in 1.07s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2025-02-23 14:18:46 in 1.06s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2025-02-23 11:28:14 in 1.09s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2025-02-23 08:34:48 in 2.87s]: IP: 54.38.247.97 / OK / HTTP status: 200