clearbluecapital.com — Clear Blue Capital Partners
Details
up since 2024-06-10 16:39 (22.7 days ago)
- Uptime: 99.63%
- Users: 0 (0 active this month, 0 active last six months)
- Posts: 0
- Peers: 0
- Version: hubzilla 8.0
- Registrations: Closed
[View Timeline] (← Broken) | [View Timeline Media]
Stats
No successful contact during the given timeframe.
Crawling Info
First contact: 2023-02-14 (16.6 months ago)
Last successful contact: 2024-07-03 (28.5 minutes ago)
Contact: 6164 successful, 2799 failed.
Average fetch time: 6.65s
Next attempt scheduled for 1.7 seconds ago.
Found through fri.aethercom.de (down)
IP address: 192.99.0.229 (and 4 others: tejanausland.com (down), iafpo.org (down), scottstolz.com (up), completehostingguide.com (up))
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-07-02 22:38:14 in 0.00s]: IP: 192.99.0.229 / Error: http / HTTP status: -1
- [2024-07-02 22:03:53 in 0.00s]: IP: 192.99.0.229 / Error: http / HTTP status: -1
- [2024-07-02 18:59:43 in 0.00s]: IP: 192.99.0.229 / Error: http / HTTP status: -1
- [2024-07-02 13:59:24 in 0.00s]: IP: 192.99.0.229 / Error: http / HTTP status: -1
- [2024-07-02 08:36:21 in 0.00s]: IP: 192.99.0.229 / Error: http / HTTP status: -1
- [2024-07-02 07:36:07 in 0.00s]: IP: 192.99.0.229 / Error: http / HTTP status: -1
- [2024-07-02 07:04:56 in 0.00s]: IP: 192.99.0.229 / Error: http / HTTP status: -1
- [2024-07-02 06:15:52 in 0.00s]: IP: 192.99.0.229 / Error: http / HTTP status: -1
- [2024-07-02 05:41:59 in 0.00s]: IP: 192.99.0.229 / Error: http / HTTP status: -1
- [2024-07-01 21:26:24 in 0.00s]: IP: 192.99.0.229 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-07-03 06:10:54 in 0.80s]: IP: 192.99.0.229 / Error: http / HTTP status: 404
- [2024-07-03 04:35:35 in 0.42s]: IP: 192.99.0.229 / Error: http / HTTP status: 404
- [2024-07-03 04:09:21 in 0.71s]: IP: 192.99.0.229 / Error: http / HTTP status: 404
- [2024-07-03 03:53:23 in 0.22s]: IP: 192.99.0.229 / Error: http / HTTP status: 404
- [2024-07-02 22:21:33 in 0.20s]: IP: 192.99.0.229 / Error: http / HTTP status: 404
- [2024-07-02 19:15:47 in 1.03s]: IP: 192.99.0.229 / Error: http / HTTP status: 404
- [2024-07-02 11:55:56 in 0.21s]: IP: 192.99.0.229 / Error: http / HTTP status: 404
- [2024-07-02 10:36:21 in 0.26s]: IP: 192.99.0.229 / Error: http / HTTP status: 404
- [2024-07-02 09:10:09 in 0.22s]: IP: 192.99.0.229 / Error: http / HTTP status: 404
- [2024-07-02 05:22:33 in 0.23s]: IP: 192.99.0.229 / Error: http / HTTP status: 404
- /api/v1/instance/peers ₍⇗₎
- [2024-07-03 02:28:28 in 0.62s]: IP: 192.99.0.229 / Error: http / HTTP status: 404
- [2024-07-02 18:12:47 in 0.23s]: IP: 192.99.0.229 / Error: http / HTTP status: 404
- [2024-07-02 10:11:35 in 0.23s]: IP: 192.99.0.229 / Error: http / HTTP status: 404
- [2024-07-01 19:51:49 in 0.79s]: IP: 192.99.0.229 / Error: http / HTTP status: 404
- [2024-07-01 11:02:14 in 0.34s]: IP: 192.99.0.229 / Error: http / HTTP status: 404
- [2024-06-30 22:35:39 in 1.30s]: IP: 192.99.0.229 / Error: http / HTTP status: 404
- [2024-06-30 12:03:50 in 1.61s]: IP: 192.99.0.229 / Error: http / HTTP status: 404
- /nodeinfo/2.0 ₍⇗₎
- [2024-07-03 09:23:21 in 4.93s]: IP: 192.99.0.229 / OK / HTTP status: 200
- [2024-07-03 09:04:11 in 0.87s]: IP: 192.99.0.229 / OK / HTTP status: 200
- [2024-07-03 08:40:35 in 1.62s]: IP: 192.99.0.229 / OK / HTTP status: 200
- [2024-07-03 08:14:03 in 2.07s]: IP: 192.99.0.229 / OK / HTTP status: 200
- [2024-07-03 07:44:14 in 5.36s]: IP: 192.99.0.229 / OK / HTTP status: 200
- [2024-07-03 07:24:32 in 1.62s]: IP: 192.99.0.229 / OK / HTTP status: 200
- [2024-07-03 07:03:14 in 1.53s]: IP: 192.99.0.229 / OK / HTTP status: 200
- [2024-07-03 06:40:32 in 0.89s]: IP: 192.99.0.229 / OK / HTTP status: 200
- [2024-07-03 06:10:54 in 3.78s]: IP: 192.99.0.229 / OK / HTTP status: 200
- [2024-07-03 05:46:39 in 2.11s]: IP: 192.99.0.229 / OK / HTTP status: 200