rickyleong.me — Ricky Leong on Mastodon
Details
up since 2024-12-02 21:06 (83.1 days ago)
- Uptime: 99.81%
- Users: 2 (2 active this month, 2 active last six months)
- Posts: 25
- Posts per user: 12.50
- Peers: 1059
- Version: mastodon 4.3.3
- Registrations: Invite
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2025-02-22 16:43 — 2025-02-23 23:52
users: 2 (0.00/day)
min/max/avg/stddev: 2 / 2 / 2.00 / 0.00
⋯ ⋯posts: 25 (0.00/day)
min/max/avg/stddev: 25 / 25 / 25.00 / 0.00
⋯ ⋯peers: 1059 (0.00/day)
min/max/avg/stddev: 1059 / 1060 / 1059.40 / 0.49
response_time: 3.029 (-1.67/day)
min/max/avg/stddev: 2 / 5 / 3.82 / 1.21
Crawling Info
First contact: 2023-07-04 (19.7 months ago)
Last successful contact: 2025-02-23 (18.2 minutes ago)
Contact: 31452 successful, 3999 failed.
Average fetch time: 3.82s
Next attempt scheduled for 11.0 minutes from now.
Found through mstdn.social (up)
IP address: 176.31.213.231 (and 147 others, including: chicken.rodeo (down), dobremiejsce.robmydobrze.pl (down), mysound.directory (down), pizzahut.systems (down), podcastindex.social (up), electricpea.ch (down), gayweeb.vip (up), matheson.it (down), theotherdell.com (down), montpellier.buzz (up))
Staff
🖖 🚇 🚌 📻 📸 Random musings about such varied subjects as photography, urban planning, transit/transportation, travel, Star Trek, shortwave radio and more. He/him. rickyleong.me(at)proton.me 📰 For miscellaneous news and current affairs, I operate https://rickyleong.me/@dailytusk 📍 Calgary, Alberta, Canada 🇨🇦
Responses
- /api/v1/instance ₍⇗₎
- [2025-02-23 23:52:05 in 0.18s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2025-02-23 21:32:37 in 0.16s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2025-02-23 18:59:41 in 0.17s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2025-02-23 16:12:31 in 0.32s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2025-02-23 13:34:11 in 0.18s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2025-02-23 10:48:42 in 0.19s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2025-02-23 07:57:36 in 0.18s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2025-02-22 16:43:40 in 0.24s]: IP: 178.33.220.142 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2025-02-23 18:59:41 in 0.16s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2025-02-23 07:57:36 in 0.16s]: IP: 178.33.220.142 / OK / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2025-02-23 23:52:05 in 1.13s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2025-02-23 21:32:37 in 1.01s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2025-02-23 18:59:41 in 1.13s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2025-02-23 16:12:31 in 2.48s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2025-02-23 13:34:11 in 1.11s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2025-02-23 10:48:42 in 1.14s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2025-02-23 07:57:36 in 1.17s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2025-02-22 16:43:40 in 1.78s]: IP: 178.33.220.142 / OK / HTTP status: 200