rail.chat
Details
up since 2024-12-03 15:03 (82.2 days ago)
- Uptime: 99.84%
- Users: 362 (50 active this month, 74 active last six months)
- Posts: 24022
- Posts per user: 66.36
- Peers: 23095
- Version: mastodon 4.3.3
- Registrations: Approval Required
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2025-02-22 12:23 — 2025-02-23 18:52
users: 362 (0.00/day)
min/max/avg/stddev: 362 / 362 / 362.00 / 0.00
⋯ ⋯posts: 24022 (30.69/day)
min/max/avg/stddev: 23983 / 24022 / 24004.80 / 15.48
peers: 23095 (82.63/day)
min/max/avg/stddev: 22990 / 23095 / 23063.60 / 38.96
response_time: 4.323 (-1.03/day)
min/max/avg/stddev: 1 / 16 / 6.11 / 5.34
Crawling Info
First contact: 2022-04-28 (33.9 months ago)
Last successful contact: 2025-02-23 (23.3 minutes ago)
Contact: 68087 successful, 9163 failed.
Average fetch time: 6.11s
Next attempt scheduled for 17.0 minutes from now.
Found through friendica.hellquist.eu (up)
IP address: 176.31.213.231 (and 162 others, including: chicken.rodeo (down), queer.garden (up), blackrock.city (up), dobremiejsce.robmydobrze.pl (down), mo-na.space (up), mysound.directory (down), pizzahut.systems (down), piraten-partei.social (up), podcastindex.social (up), abolish.social (up))
Staff

Admin of https://Rail.chat Discussing passenger and freight rail, its connections to transit and other non-car options, and the economic, environmental and equity benefits of seamless mobility. Support Rail.chat by donating to All Aboard NW at https://allaboardnw.org/support
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2025-02-23 12:59:13 in 0.00s]: IP: 176.31.213.231 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2025-02-23 18:52:52 in 0.53s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2025-02-23 15:56:43 in 0.18s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2025-02-23 10:01:20 in 0.37s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2025-02-23 06:00:23 in 0.69s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2025-02-22 12:23:07 in 0.31s]: IP: 176.31.213.231 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2025-02-23 15:56:43 in 0.16s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2025-02-23 06:00:23 in 0.48s]: IP: 178.33.220.142 / OK / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2025-02-23 18:52:52 in 3.39s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2025-02-23 15:56:43 in 1.02s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2025-02-23 10:01:20 in 1.98s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2025-02-23 06:00:23 in 2.46s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2025-02-22 12:23:07 in 1.99s]: IP: 176.31.213.231 / OK / HTTP status: 200