status.july.jp — Now/here
The Current Situation in July
Details
up since 2026-03-09 18:46 (36.0 days ago)
- Uptime: 100.00%
- Users: 1
- Posts: 4
- Posts per user: 4.00
- Peers: 4
- Version: gotosocial 0.21.2+git-343fed2
- Source code: https://codeberg.org/superseriousbusiness/gotosocial
- Registrations: Closed
[View Timeline] (← Broken) | [View Timeline Media]
Stats
No successful contact during the given timeframe.
Crawling Info
First contact: 2026-03-09 (36.0 days ago)
Last successful contact: 2026-04-14 (83.6 minutes ago)
Contact: 942 successful, 56 failed.
Average fetch time: 5.16s
Next attempt scheduled for 38.8 minutes ago.
Found through misskey.xstudiotw.net (up)
IP address: 172.67.168.212 (and july.jp.)
- Country: US
- Net Org: OrgName: Cloudflare, Inc.
- CIDR: 172.64.0.0/13
Staff
ak@status.july.jp
[No bio.]
[No bio.]
Responses
- /api/v1/instance ₍⇗₎
- [2026-04-14 17:28:49 in 0.15s]: IP: 172.67.168.212 / OK / HTTP status: 200
- [2026-04-14 15:44:32 in 0.12s]: IP: 172.67.168.212 / OK / HTTP status: 200
- [2026-04-14 13:47:28 in 0.48s]: IP: 104.21.38.240 / OK / HTTP status: 200
- [2026-04-14 11:54:41 in 0.75s]: IP: 104.21.38.240 / OK / HTTP status: 200
- [2026-04-14 10:14:26 in 0.67s]: IP: 104.21.38.240 / OK / HTTP status: 200
- [2026-04-14 08:29:34 in 0.14s]: IP: 104.21.38.240 / OK / HTTP status: 200
- [2026-04-14 06:23:14 in 0.12s]: IP: 172.67.168.212 / OK / HTTP status: 200
- [2026-04-14 04:07:02 in 0.47s]: IP: 172.67.168.212 / OK / HTTP status: 200
- [2026-04-14 02:55:45 in 0.12s]: IP: 104.21.38.240 / OK / HTTP status: 200
- [2026-04-14 01:41:28 in 0.12s]: IP: 104.21.38.240 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2026-04-14 13:47:28 in 0.45s]: IP: 104.21.38.240 / Error: http / HTTP status: 401
- [2026-04-13 11:48:42 in 0.11s]: IP: 172.67.168.212 / Error: http / HTTP status: 401
- [2026-04-13 01:11:25 in 0.12s]: IP: 172.67.168.212 / Error: http / HTTP status: 401
- [2026-04-12 10:35:16 in 0.12s]: IP: 104.21.38.240 / Error: http / HTTP status: 401
- [2026-04-11 19:07:09 in 0.72s]: IP: 172.67.168.212 / Error: http / HTTP status: 401
- [2026-04-11 07:23:33 in 0.68s]: IP: 104.21.38.240 / Error: http / HTTP status: 401
- [2026-04-10 17:17:02 in 0.14s]: IP: 104.21.38.240 / Error: http / HTTP status: 401
- [2026-04-08 21:52:05 in 0.69s]: IP: 104.21.38.240 / Error: http / HTTP status: 401
- [2026-04-08 02:35:16 in 0.13s]: IP: 172.67.168.212 / Error: http / HTTP status: 401
- /nodeinfo/2.1 ₍⇗₎
- [2026-04-14 17:28:49 in 0.84s]: IP: 172.67.168.212 / OK / HTTP status: 200
- [2026-04-14 15:44:32 in 0.52s]: IP: 172.67.168.212 / OK / HTTP status: 200
- [2026-04-14 13:47:28 in 2.24s]: IP: 104.21.38.240 / OK / HTTP status: 200
- [2026-04-14 11:54:41 in 3.09s]: IP: 104.21.38.240 / OK / HTTP status: 200
- [2026-04-14 10:14:26 in 3.08s]: IP: 104.21.38.240 / OK / HTTP status: 200
- [2026-04-14 08:29:34 in 0.54s]: IP: 104.21.38.240 / OK / HTTP status: 200
- [2026-04-14 06:23:14 in 0.50s]: IP: 172.67.168.212 / OK / HTTP status: 200
- [2026-04-14 04:07:02 in 2.36s]: IP: 172.67.168.212 / OK / HTTP status: 200
- [2026-04-14 02:55:45 in 0.71s]: IP: 104.21.38.240 / OK / HTTP status: 200
- [2026-04-14 01:41:28 in 0.61s]: IP: 104.21.38.240 / OK / HTTP status: 200
Federation Info
Peers: 4
Federation restrictions
Unsalted hashes of "status.july.jp"
- MD5: 321311b90faad2c7136c5c1fbb823e65
- SHA1: b7634772acba8b631f9079a6826b2f55bd5c3907
- SHA256: 0bbd7909f49596b8211c3f9d306419a3ce2eaefeae7a58443c3f5d30b9fdba66