corporaterunaways.social — Corporate Runaways
Details
up since 2024-06-06 13:59 (29.4 days ago)
- Uptime: 99.81%
- Users: 11 (10 active this month, 10 active last six months)
- Posts: 61
- Posts per user: 5.55
- Peers: 1190
- Version: mastodon 4.2.7
- Registrations: Closed
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-06-22 20:02 — 2024-07-06 00:17
users: 11 (0.01/day)
min/max/avg/stddev: 7 / 11 / 10.15 / 0.91
posts: 60 (0.07/day)
min/max/avg/stddev: 39 / 61 / 58.12 / 4.81
peers: 1190 (3.24/day)
min/max/avg/stddev: 256 / 1190 / 1108.00 / 213.26
response_time: 1.675 (0.00/day)
min/max/avg/stddev: 0 / 25 / 4.34 / 4.86
Crawling Info
First contact: 2022-12-05 (19.0 months ago)
Last successful contact: 2024-07-06 (8.6 minutes ago)
Contact: 28387 successful, 674 failed.
Average fetch time: 4.34s
Next attempt scheduled for 12.8 minutes from now.
Found through updog.no (down)
IP address: 174.138.38.183
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-07-05 21:16:30 in 0.00s]: IP: 174.138.38.183 / Error: http / HTTP status: -1
- [2024-07-05 17:45:32 in 0.00s]: IP: 174.138.38.183 / Error: http / HTTP status: -1
- [2024-07-05 13:30:44 in 0.00s]: IP: 174.138.38.183 / Error: http / HTTP status: -1
- [2024-07-05 08:32:35 in 0.00s]: IP: 174.138.38.183 / Error: http / HTTP status: -1
- [2024-07-05 07:47:53 in 0.00s]: IP: 174.138.38.183 / Error: http / HTTP status: -1
- [2024-07-05 05:54:48 in 0.00s]: IP: 174.138.38.183 / Error: http / HTTP status: -1
- [2024-07-05 02:51:46 in 0.00s]: IP: 174.138.38.183 / Error: http / HTTP status: -1
- [2024-07-05 00:36:49 in 0.00s]: IP: 174.138.38.183 / Error: http / HTTP status: -1
- [2024-07-04 18:53:35 in 0.00s]: IP: 174.138.38.183 / Error: http / HTTP status: -1
- [2024-07-04 17:21:45 in 0.00s]: IP: 174.138.38.183 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-07-06 00:17:58 in 0.10s]: IP: 174.138.38.183 / OK / HTTP status: 200
- [2024-07-05 23:55:23 in 0.10s]: IP: 174.138.38.183 / OK / HTTP status: 200
- [2024-07-05 23:33:01 in 0.07s]: IP: 174.138.38.183 / OK / HTTP status: 200
- [2024-07-05 23:10:34 in 0.28s]: IP: 174.138.38.183 / OK / HTTP status: 200
- [2024-07-05 22:48:06 in 0.35s]: IP: 174.138.38.183 / OK / HTTP status: 200
- [2024-07-05 22:25:08 in 0.87s]: IP: 174.138.38.183 / OK / HTTP status: 200
- [2024-07-05 22:02:18 in 0.09s]: IP: 174.138.38.183 / OK / HTTP status: 200
- [2024-07-05 21:39:14 in 0.49s]: IP: 174.138.38.183 / OK / HTTP status: 200
- [2024-07-05 20:53:14 in 0.09s]: IP: 174.138.38.183 / OK / HTTP status: 200
- [2024-07-05 20:29:54 in 0.12s]: IP: 174.138.38.183 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-07-05 18:57:24 in 0.10s]: IP: 174.138.38.183 / OK / HTTP status: 200
- [2024-07-05 10:49:18 in 0.09s]: IP: 174.138.38.183 / OK / HTTP status: 200
- [2024-07-04 23:28:41 in 0.27s]: IP: 174.138.38.183 / OK / HTTP status: 200
- [2024-07-04 13:28:01 in 0.08s]: IP: 174.138.38.183 / OK / HTTP status: 200
- [2024-07-04 05:19:03 in 0.63s]: IP: 174.138.38.183 / OK / HTTP status: 200
- [2024-07-03 19:53:25 in 0.08s]: IP: 174.138.38.183 / OK / HTTP status: 200
- [2024-07-03 11:02:26 in 0.09s]: IP: 174.138.38.183 / OK / HTTP status: 200
- [2024-07-03 01:37:16 in 0.09s]: IP: 174.138.38.183 / OK / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2024-07-06 00:17:58 in 0.48s]: IP: 174.138.38.183 / OK / HTTP status: 200
- [2024-07-05 23:55:23 in 0.27s]: IP: 174.138.38.183 / OK / HTTP status: 200
- [2024-07-05 23:33:01 in 0.37s]: IP: 174.138.38.183 / OK / HTTP status: 200
- [2024-07-05 23:10:34 in 1.52s]: IP: 174.138.38.183 / OK / HTTP status: 200
- [2024-07-05 22:48:06 in 2.10s]: IP: 174.138.38.183 / OK / HTTP status: 200
- [2024-07-05 22:25:08 in 3.30s]: IP: 174.138.38.183 / OK / HTTP status: 200
- [2024-07-05 22:02:18 in 0.38s]: IP: 174.138.38.183 / OK / HTTP status: 200
- [2024-07-05 21:39:14 in 1.81s]: IP: 174.138.38.183 / OK / HTTP status: 200
- [2024-07-05 20:53:14 in 0.45s]: IP: 174.138.38.183 / OK / HTTP status: 200
- [2024-07-05 20:29:54 in 0.33s]: IP: 174.138.38.183 / OK / HTTP status: 200