atlbbs.com — AtlBBS
Details
up since 2024-04-10 20:21 (36.5 days ago)
- Uptime: 100.00%
- Users: 2 (2 active this month, 2 active last six months)
- Posts: 10
- Posts per user: 5.00
- Peers: 189
- Version: mastodon 4.2.8
- Registrations: Approval Required
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-05-03 16:41 — 2024-05-17 08:08
users: 2 (0.00/day)
min/max/avg/stddev: 2 / 2 / 2.00 / 0.00
⋯ ⋯posts: 10 (0.15/day)
min/max/avg/stddev: 8 / 10 / 9.04 / 0.44
peers: 189 (4.10/day)
min/max/avg/stddev: 132 / 189 / 167.65 / 15.69
response_time: 2.806 (-3.02/day)
min/max/avg/stddev: 0 / 62 / 9.55 / 14.05
Crawling Info
First contact: 2024-04-10 (36.5 days ago)
Last successful contact: 2024-05-17 (23.8 minutes ago)
Contact: 1869 successful, 94 failed.
Average fetch time: 9.55s
Next attempt scheduled for 10.8 minutes from now.
Found through infosec.exchange (up)
IP address: 94.23.75.107 (and 984 others, including: suganthan.social (down), thehyperwave.social (down), hype.city (down), wbknl.xyz (down), vocalounge.cafe (blacklisted), pacsa.us (up), itsnot.online (down), shog.social (down), strangers.social (down), 23th.day (down))
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-05-17 06:12:26 in 0.00s]: IP: 94.23.75.107 / Error: http / HTTP status: -1
- [2024-05-17 05:32:37 in 0.00s]: IP: 94.23.75.107 / Error: http / HTTP status: -1
- [2024-05-16 20:34:46 in 0.00s]: IP: 94.23.75.107 / Error: http / HTTP status: -1
- [2024-05-16 19:47:01 in 0.00s]: IP: 94.23.75.107 / Error: http / HTTP status: -1
- [2024-05-16 16:48:18 in 0.00s]: IP: 94.23.75.107 / Error: http / HTTP status: -1
- [2024-05-16 16:06:12 in 0.00s]: IP: 94.23.75.107 / Error: http / HTTP status: -1
- [2024-05-16 03:07:06 in 0.00s]: IP: 94.23.75.107 / Error: http / HTTP status: -1
- [2024-05-16 00:12:27 in 0.00s]: IP: 94.23.75.107 / Error: http / HTTP status: -1
- [2024-05-15 23:33:52 in 0.00s]: IP: 94.23.75.107 / Error: http / HTTP status: -1
- [2024-05-15 18:52:54 in 0.00s]: IP: 94.23.75.107 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-05-17 08:08:19 in 0.18s]: IP: 94.23.75.107 / OK / HTTP status: 200
- [2024-05-17 07:31:09 in 0.19s]: IP: 94.23.75.107 / OK / HTTP status: 200
- [2024-05-17 06:52:18 in 0.19s]: IP: 94.23.75.107 / OK / HTTP status: 200
- [2024-05-17 04:52:27 in 0.22s]: IP: 94.23.75.107 / OK / HTTP status: 200
- [2024-05-17 04:14:23 in 0.49s]: IP: 94.23.75.107 / OK / HTTP status: 200
- [2024-05-17 02:58:21 in 0.22s]: IP: 94.23.75.107 / OK / HTTP status: 200
- [2024-05-17 02:21:52 in 0.17s]: IP: 94.23.75.107 / OK / HTTP status: 200
- [2024-05-17 01:43:52 in 0.20s]: IP: 94.23.75.107 / OK / HTTP status: 200
- [2024-05-17 01:04:16 in 0.19s]: IP: 94.23.75.107 / OK / HTTP status: 200
- [2024-05-17 00:26:41 in 0.46s]: IP: 94.23.75.107 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-05-16 15:18:26 in 0.17s]: IP: 94.23.75.107 / OK / HTTP status: 200
- [2024-05-16 00:50:41 in 0.17s]: IP: 94.23.75.107 / OK / HTTP status: 200
- [2024-05-14 12:21:27 in 0.19s]: IP: 94.23.75.107 / OK / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2024-05-17 08:08:19 in 0.98s]: IP: 94.23.75.107 / OK / HTTP status: 200
- [2024-05-17 07:31:09 in 1.00s]: IP: 94.23.75.107 / OK / HTTP status: 200
- [2024-05-17 06:52:18 in 1.81s]: IP: 94.23.75.107 / OK / HTTP status: 200
- [2024-05-17 04:52:27 in 1.05s]: IP: 94.23.75.107 / OK / HTTP status: 200
- [2024-05-17 04:14:23 in 3.32s]: IP: 94.23.75.107 / OK / HTTP status: 200
- [2024-05-17 03:36:17 in 0.63s]: IP: 94.23.75.107 / Error: unparseable / HTTP status: 200
- [2024-05-17 02:58:21 in 1.02s]: IP: 94.23.75.107 / OK / HTTP status: 200
- [2024-05-17 02:21:52 in 1.09s]: IP: 94.23.75.107 / OK / HTTP status: 200
- [2024-05-17 01:43:52 in 0.99s]: IP: 94.23.75.107 / OK / HTTP status: 200
- [2024-05-17 01:04:16 in 1.01s]: IP: 94.23.75.107 / OK / HTTP status: 200