rail.chat
Details
up since 2024-06-08 06:20 (30.7 days ago)
- Uptime: 99.83%
- Users: 339 (46 active this month, 80 active last six months)
- Posts: 19369
- Posts per user: 57.14
- Peers: 19837
- Version: mastodon 4.2.10
- Registrations: Approval Required
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-06-25 02:23 — 2024-07-08 22:22
users: 339 (0.10/day)
min/max/avg/stddev: 309 / 339 / 337.78 / 4.02
posts: 19369 (31.13/day)
min/max/avg/stddev: 10309 / 19369 / 19038.32 / 1213.69
peers: 19837 (13.90/day)
min/max/avg/stddev: 15792 / 19837 / 19697.94 / 542.69
response_time: 4.261 (0.01/day)
min/max/avg/stddev: 0 / 21 / 3.29 / 2.74
Crawling Info
First contact: 2022-04-28 (26.4 months ago)
Last successful contact: 2024-07-08 (92.7 minutes ago)
Latest attempt: 2024-07-08 (6.1 minutes ago)
Contact: 50038 successful, 6003 failed.
Average fetch time: 3.29s
Next attempt scheduled for 12.6 minutes from now.
Found through friendica.hellquist.eu (up)
IP address: 176.31.213.231 (and 142 others, including: chicken.rodeo (down), relay.plush.city (down), autonomous.zone (up), tentacle.social (up), nologo.social (up), badgay.net (down), blackrock.city (up), kilo.cafe (down), dobremiejsce.robmydobrze.pl (down), lotus-eyes.net (down))
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 ₍⇗₎
- [2024-07-08 19:57:56 in 0.00s]: IP: 176.31.213.231 / Error: http / HTTP status: -1
- [2024-07-08 18:43:32 in 0.00s]: IP: 178.33.220.142 / Error: http / HTTP status: -1
- [2024-07-08 18:24:57 in 0.00s]: IP: 178.33.220.142 / Error: http / HTTP status: -1
- [2024-07-08 15:36:06 in 0.00s]: IP: 178.33.220.142 / Error: http / HTTP status: -1
- [2024-07-08 12:29:14 in 0.00s]: IP: 176.31.213.231 / Error: http / HTTP status: -1
- [2024-07-08 10:15:08 in 0.00s]: IP: 178.33.220.142 / Error: http / HTTP status: -1
- [2024-07-08 06:13:45 in 0.00s]: IP: 176.31.213.231 / Error: http / HTTP status: -1
- [2024-07-08 02:42:39 in 0.00s]: IP: 178.33.220.142 / Error: http / HTTP status: -1
- [2024-07-07 22:22:10 in 0.00s]: IP: 176.31.213.231 / Error: http / HTTP status: -1
- [2024-07-07 20:50:01 in 0.00s]: IP: 178.33.220.142 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-07-08 20:55:33 in 0.16s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-07-08 20:36:10 in 0.16s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2024-07-08 20:17:03 in 0.39s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2024-07-08 19:20:27 in 0.68s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2024-07-08 19:01:59 in 0.34s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-07-08 18:06:19 in 0.16s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2024-07-08 17:47:15 in 0.35s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-07-08 17:28:21 in 0.18s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2024-07-08 17:09:50 in 0.20s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-07-08 16:51:09 in 0.16s]: IP: 176.31.213.231 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-07-08 16:32:17 in 0.18s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-07-08 08:03:46 in 0.17s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-07-07 20:31:54 in 0.17s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2024-07-07 11:59:17 in 0.18s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2024-07-06 23:50:30 in 0.17s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-07-06 15:09:42 in 0.18s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-07-06 05:09:28 in 0.17s]: IP: 178.33.220.142 / OK / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2024-07-08 22:22:11 in 1.90s]: IP: 176.31.213.231 / Error: unparseable / HTTP status: 200
- [2024-07-08 21:58:11 in 3.79s]: IP: 178.33.220.142 / Error: unparseable / HTTP status: 200
- [2024-07-08 21:35:43 in 1.09s]: IP: 178.33.220.142 / Error: unparseable / HTTP status: 200
- [2024-07-08 21:15:03 in 0.75s]: IP: 178.33.220.142 / Error: unparseable / HTTP status: 200
- [2024-07-08 20:55:33 in 0.97s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-07-08 20:36:10 in 1.09s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2024-07-08 20:17:03 in 1.80s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2024-07-08 19:39:12 in 2.30s]: IP: 178.33.220.142 / Error: unparseable / HTTP status: 200
- [2024-07-08 19:20:27 in 4.55s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2024-07-08 19:01:54 in 3.02s]: IP: 178.33.220.142 / OK / HTTP status: 200