fietser.social
Details
up since 2024-06-09 12:42 (17.2 days ago)
- Uptime: 99.81%
- Users: 2 (1 active this month, 2 active last six months)
- Posts: 565
- Posts per user: 282.50
- Peers: 866
- Version: mastodon 4.2.9
- Registrations: Approval Required
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-06-13 00:29 — 2024-06-26 17:37
users: 2 (0.00/day)
min/max/avg/stddev: 2 / 2 / 2.00 / 0.00
⋯ ⋯posts: 565 (1.01/day)
min/max/avg/stddev: 551 / 565 / 557.59 / 4.26
peers: 866 (1.01/day)
min/max/avg/stddev: 852 / 866 / 859.41 / 4.16
response_time: 1.938 (-0.34/day)
min/max/avg/stddev: 1 / 20 / 5.59 / 4.01
Crawling Info
First contact: 2022-11-05 (19.7 months ago)
Last successful contact: 2024-06-26 (40.0 minutes ago)
Latest attempt: 2024-06-26 (14.1 minutes ago)
Contact: 26758 successful, 789 failed.
Average fetch time: 5.59s
Next attempt scheduled for 11.2 minutes from now.
Found through pirati.ca (up)
IP address: 178.33.220.142 (and 369 others, including: www.masto.pt (down), indieweb.social (up), hapyyr.com (up), yapstreams.com (up), rpvortex.online (up), hackdezorg.nl (down), planetarymessage.com (down), meinmuenster.land (up), femme.energy (down), benhutchings.com (down))
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-06-26 16:19:50 in 0.00s]: IP: 178.33.220.142 / Error: http / HTTP status: -1
- [2024-06-26 14:09:47 in 0.00s]: IP: 178.33.220.142 / Error: http / HTTP status: -1
- [2024-06-26 09:46:33 in 0.00s]: IP: 178.33.220.142 / Error: http / HTTP status: -1
- [2024-06-26 06:45:00 in 0.00s]: IP: 178.33.220.142 / Error: http / HTTP status: -1
- [2024-06-26 02:18:16 in 0.00s]: IP: 178.33.220.142 / Error: http / HTTP status: -1
- [2024-06-25 17:19:02 in 0.00s]: IP: 178.33.220.142 / Error: http / HTTP status: -1
- [2024-06-25 13:08:07 in 0.00s]: IP: 178.33.220.142 / Error: http / HTTP status: -1
- [2024-06-25 11:11:17 in 0.00s]: IP: 178.33.220.142 / Error: http / HTTP status: -1
- [2024-06-25 10:28:57 in 0.00s]: IP: 178.33.220.142 / Error: http / HTTP status: -1
- [2024-06-25 08:34:59 in 0.00s]: IP: 178.33.220.142 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-06-26 17:11:46 in 0.18s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-06-26 16:46:20 in 0.23s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-06-26 15:53:06 in 0.19s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-06-26 15:27:13 in 0.20s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-06-26 14:35:12 in 0.46s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-06-26 13:44:39 in 0.17s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-06-26 13:18:47 in 0.19s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-06-26 12:51:41 in 0.21s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-06-26 11:57:44 in 0.19s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-06-26 11:30:44 in 0.64s]: IP: 178.33.220.142 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-06-26 07:36:51 in 0.17s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-06-25 22:34:27 in 0.17s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-06-25 14:24:59 in 0.16s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-06-25 03:51:24 in 0.17s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-06-24 02:32:42 in 0.17s]: IP: 178.33.220.142 / OK / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2024-06-26 17:37:38 in 0.63s]: IP: 178.33.220.142 / Error: unparseable / HTTP status: 200
- [2024-06-26 17:11:46 in 1.07s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-06-26 16:46:20 in 1.04s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-06-26 15:53:06 in 1.00s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-06-26 15:27:13 in 1.09s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-06-26 15:00:58 in 0.99s]: IP: 178.33.220.142 / Error: unparseable / HTTP status: 200
- [2024-06-26 14:35:12 in 4.01s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-06-26 13:44:39 in 1.04s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-06-26 13:18:47 in 1.03s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-06-26 12:51:41 in 1.29s]: IP: 178.33.220.142 / OK / HTTP status: 200