Scheduled Maintenance

Last updated: 2026-02-16T19:50:49Z

Platform Services

Booking System

Online reservations & calendar sync

Maintenance

Payment Processing

Secure payment collection via Montonio & Stripe

Maintenance

Guest Portal

Guest check-in & communication

Maintenance

Email & SMS

Automated guest notifications

Maintenance

Smart Access

Smart locks & device control

Maintenance

Owner Dashboard

Property management portal

Maintenance

Available Regions

Dynamically discovered tenant deployments across Europe

🇪🇪

Estonia

Regional

Unknown
Domain vermare.ee
Deployments 0/3 healthy
Namespace vermare-ee
🇫🇮

Finland

Regional

Unknown
Domain vermare.fi
Deployments 0/3 healthy
Namespace vermare-fi
🇱🇻

Latvia

Regional

Unknown
Domain vermare.lv
Deployments 0/0 healthy
Namespace vermare-lv

Platform & Infrastructure

🚐

VanMare

vanmare

Unknown
Deployments 0/4 healthy
Namespace vanmare-system
🎮

Demo

demo

Operational
Deployments 3/3 healthy
Namespace vermare-demo
🛠️

Development

dev

Operational
Deployments 5/5 healthy
Namespace vermare-dev
🏢

Platform

platform

Unknown
Deployments 0/3 healthy
Namespace vermare-platform
🛠️

Platform Dev

dev

Operational
Deployments 4/4 healthy
Namespace vermare-platform-dev
⚙️

caddy-system

Infrastructure

Healthy
Deployments 1/1 healthy
⚙️

monitoring

Infrastructure

Healthy
Deployments 6/6 healthy
⚙️

vermare-system

Infrastructure

Healthy
Deployments 10/10 healthy

AI SRE — Väino

Automated Site Reliability
🧑‍💻

Väino

Monitoring 9 tenants. No anomalies detected.

On-duty 😌 Calm
0
Scans Today
0
Auto-Fixed
9
Escalated
9
Tenants Monitored

Recent Actions

2026-02-16T19:49 Keeping an eye on: vermare-dev/frontend-564f9798cf-2p6v5: Unhealthy — Readiness probe failed: Get "http://10.244.35.125:3000/": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
2026-02-16T19:49 Keeping an eye on: vermare-dev/status-api-757c4bbd98-fckld: Failed — Failed to pull image "vermare-status-api:latest": failed to pull and unpack image "docker.io/library/vermare-status-api:latest": failed to resolve reference "docker.io/library/vermare-status-api:lates
2026-02-16T19:48 I had an error: 'ascii' codec can't encode character '\U0001f6a8' in position 0: ordinal not in range(128). Recovering.
2026-02-16T19:48 Escalated: vermare-system: panic/fatal error detected: 2026-02-16 19:43:31 [ai_shared.journal] INFO [escalated] Escalated: vermare-system: panic/fatal error detected: 2026-02-16 19:38:20 [ai_shared.journal] INFO [escalated] Escalated: vermare-system: pani
2026-02-16T19:48 Keeping an eye on: vermare-system/mcp-kubernetes-cb8dd879-kr5j2: CPU throttling at 49%

Active Incidents

3

Pod backend-7f848966bc-pl9s6 memory usage is 96.3%

identified

Pod is using more than 90% of its memory limit.

Started: 2026-02-16T15:59

One or more targets are unreachable.

identified

100% of the frontend/frontend targets in vermare-survey namespace are down.

Namespace: vermare-survey Started: 2026-02-12T13:00

Job failed to complete.

identified

Job vermare-demo/demo-flush-29520180 failed to complete. Removing failed job after investigation should clear this alert.

Namespace: vermare-demo Started: 2026-02-16T03:16

30-Day Uptime

97.59% Last 30 days
30 days ago Today

Get Status Updates

Subscribe to receive notifications about service status and planned maintenance

Subscribe to Updates

Status API

Programmatic access to VerMare platform status data. All endpoints are public and read-only.

GET /api/v1/status

Complete status overview

GET /api/v1/services

Core service health

GET /api/v1/regions

Regional deployments

GET /api/v1/incidents

Active incidents

GET /api/v1/uptime

30-day uptime history

GET /api/v1/vaino

AI SRE agent status