Availability checks
Basic uptime and endpoint reachability checks across regional hosts.
Private infrastructure lab
Monitoring, static delivery and regional endpoint checks.
I-RMW is a small engineering workspace for availability checks, TLS observations, static content delivery tests and operational notes around lightweight web infrastructure.
Overview
Small, predictable and observable infrastructure.
The project keeps simple public pages for infrastructure notes and endpoint status checks. Each endpoint follows the same visual system and exposes only static content.
TLS observations
Certificate lifecycle notes, HTTPS behavior and edge configuration records.
Static delivery
Small static assets used to validate caching, routing and response behavior.
Regional endpoints
Endpoint map
Regional pages use the same layout and status language. They are kept intentionally lightweight and suitable for simple external checks.
ru1.i-rmw.ru
Primary regional endpoint.
Public page planned
ru2.i-rmw.ru
Secondary regional endpoint.
Static page available
de1.i-rmw.ru
Central Europe endpoint.
Static page available
fi1.i-rmw.ru
Northern Europe endpoint.
Fallback page planned
se1.i-rmw.ru
Nordic endpoint.
Fallback page planned
Operational notes
Recent infrastructure notes
Static endpoint pages
A shared visual template is being used for public root and regional endpoint pages. The pages are static and do not require an application backend.
TLS configuration review
Endpoint certificates are tracked separately to simplify renewal, verification and rollback during configuration updates.
Monitoring baseline
Basic external checks include HTTP status, TLS availability, static asset reachability and expected response size.
Current status
Root endpoint is ready for static checks.
This page is served as static content. No dynamic application runtime is required for the public root endpoint.
HTTPS endpoint: active
Static assets: available
Public root page: operational
Regional pages: staged rollout