Hidden Rabbit

Traffic topology at a glance

Operate nodes, chains, subscriptions, and access delivery without falling back to legacy runtime vocabulary.

Open nodes trackReview chain topologyAudit access delivery

Operating posture

  • Nodes, chains, subscriptions, and access stay product-owned in Hidden Rabbit.
  • Shared shell contracts remain in rabbit-platform; routing vocabulary does not.
  • The first API boundary should describe panel data explicitly before runtime integration deepens.
Cascade statusOnline

AMS1-OD → AMS2-OD is deployed in reverse mode and healthy.

Active nodes2

Portal and bridge are healthy; Frankfurt stays ready for the next hybrid slice.

Delivery surfaces2

Operator-facing access publication remains product-owned inside Hidden Rabbit.

Route postureHidden Rabbit

AMS1-OD → AMS2-OD on tunnel 10086

Delivery readiness1 surfaces ready

1 subscription tracks are still rolling toward stable access delivery.

Operator backlog2 live users across the opening slice

1 standby nodes and 1 review queues still need operator attention.

Nodes

Node fleet

Portal, bridge, and standby nodes that shape the first Hidden Rabbit route map.

AMS1-OD

Portal relay in Amsterdam

online
Public endpoint
194.50.94.149:8443
Listener port
8443
Hop range
20000-50000
Live users
1
FRA1-OD

Standalone relay in Frankfurt

watch
Public endpoint
fra1-od.hiddenrabbit.net.ru:443
Listener port
443
Hop range
20000-50000
Live users
0
AMS2-OD

Bridge relay in Amsterdam

online
Public endpoint
89.125.17.81:443
Listener port
443
Hop range
20000-50000
Live users
1
Telegram deliveryHidden Rabbit

Bot-issued link

ready
Operator fallbackHidden Rabbit

Encrypted archive

review