sneak/netwatch
1
0 Fork 0
Code Issues 5 Pull Requests 1 Actions 8 Packages Projects Releases Wiki Activity

The S3 Bahrain target never answers, so Reachable never reaches 26/26 #205

New Issue
Closed
opened 2026-11-11 21:16:19 +01:00 by clawbot · 1 comment
clawbot commented 2026-11-11 21:16:19 +01:00
Collaborator
Copy link
Copy source

The row S3 me-south-1 (Bahrain) times out on every check, for every user. Its host, s3.me-south-1.amazonaws.com, accepts no connection: curl -I https://s3.me-south-1.amazonaws.com/robots.txt times out, while the same request to each of the other S3 regions gets a 403 in under half a second. Press reports say the region has been out of service since March 2026.

Found by the acceptance test on #204.

Steps: build next, open the page, wait one minute.

What happens: the Bahrain row shows timeout on every check. Reachable stays at 25/26, in yellow, on a network where everything else answers.

What should happen: every WAN target answers when the network works, so a healthy network shows 26/26.

Decided: the Bahrain entry is replaced by S3 ap-south-1 (Mumbai), https://s3.ap-south-1.amazonaws.com/robots.txt, checked with HEAD like the other S3 entries. It is the closest long-running region outside the affected area, and it answers 403 directly, with no redirect. Reversing this means changing one entry in WAN_HOSTS.

Definition of done

  • WAN_HOSTS in web/src/main.js has S3 ap-south-1 (Mumbai) in place of the Bahrain entry, with method: "HEAD".
  • README.md, Targets, lists Mumbai in place of Bahrain.
  • test/unit/main.test.js names the new entry in place of the Bahrain one.

Model: opus-5-5

The row `S3 me-south-1 (Bahrain)` times out on every check, for every user. Its host, `s3.me-south-1.amazonaws.com`, accepts no connection: `curl -I https://s3.me-south-1.amazonaws.com/robots.txt` times out, while the same request to each of the other S3 regions gets a 403 in under half a second. Press reports say the region has been out of service since March 2026. Found by the acceptance test on https://git.eeqj.de/sneak/netwatch/issues/204. **Steps**: build `next`, open the page, wait one minute. **What happens**: the Bahrain row shows `timeout` on every check. `Reachable` stays at `25/26`, in yellow, on a network where everything else answers. **What should happen**: every WAN target answers when the network works, so a healthy network shows `26/26`. Decided: the Bahrain entry is replaced by `S3 ap-south-1 (Mumbai)`, `https://s3.ap-south-1.amazonaws.com/robots.txt`, checked with `HEAD` like the other S3 entries. It is the closest long-running region outside the affected area, and it answers 403 directly, with no redirect. Reversing this means changing one entry in `WAN_HOSTS`. ## Definition of done - [ ] `WAN_HOSTS` in `web/src/main.js` has `S3 ap-south-1 (Mumbai)` in place of the Bahrain entry, with `method: "HEAD"`. - [ ] `README.md`, Targets, lists Mumbai in place of Bahrain. - [ ] `test/unit/main.test.js` names the new entry in place of the Bahrain one. Model: opus-5-5
clawbot commented 2026-11-11 21:28:17 +01:00
Author
Collaborator
Copy link
Copy source

#216 (branch issue-205-s3-mumbai) replaces the Bahrain entry with S3 ap-south-1 (Mumbai), HEAD, in WAN_HOSTS, README.md and test/unit/main.test.js, in the same position.

Model: opus-5-5

https://git.eeqj.de/sneak/netwatch/pulls/216 (branch `issue-205-s3-mumbai`) replaces the Bahrain entry with `S3 ap-south-1 (Mumbai)`, `HEAD`, in `WAN_HOSTS`, `README.md` and `test/unit/main.test.js`, in the same position. Model: opus-5-5
Sign in to join this conversation.
No Branch/Tag Specified
Labels
Clear labels
critical
Extremely important: data loss, a security hole, production down, or basic use impossible
 merge-ready
needs-checks
needs-rebase
needs-review
needs-rework
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
clawbot sneak (Jeffrey Paul)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sneak/netwatch#205