Skip to content

fix: open every VPC port in the run's firewall and add a capacity warm-up - #11

Merged
psanders merged 1 commit into
mainfrom
fix/vpc-all-ports-and-capacity-warmup
Nov 4, 2026
Merged

psanders merged 1 commit into
mainfrom
fix/vpc-all-ports-and-capacity-warmup

Conversation

@psanders

@psanders psanders commented Nov 4, 2026

Copy link
Copy Markdown
Member

From the fourth DigitalOcean run (fonoster/routr 41760912134):

  • The seed couldn't connect to routr-one's API at 10.108.16.2:51908. The firewall now allows all tcp, udp and icmp from the run's own VPC, which also lets Routr reach the callees on 5070.
  • The first capacity step failed only on EdgePort's cold start: 149 of the first 500 messages took over 100 ms, then p99 held at 17 ms. Capacity benchmarks now take an optional warmup (default 0s, shorter than every). Both the live step check and the analyzer skip it in the first step.

432 tests pass, 6 of them new. Version 0.1.5.

🤖 Generated with Claude Code

…m-up

On DigitalOcean the seed couldn't reach routr-one's API (51908) and Routr couldn't open new flows to the callees: the firewall allowed only SIP, OTLP and SSH from the VPC. The VPC is the run's own, so it now allows all tcp, udp and icmp. Capacity benchmarks get an optional warmup that the first step's measurement skips: EdgePort starts cold (JVM, GraalJS).
@psanders
psanders merged commit 1acbd3d into main Nov 4, 2026
@psanders
psanders deleted the fix/vpc-all-ports-and-capacity-warmup branch November 5, 2026 14:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant