EU-hosted monitoring for availability data
Uptime monitoring looks trivial until it becomes part of a vendor review. Endpoints, hostnames, regions and incident history reveal a lot about how your systems run. MOJAQ keeps monitoring hosted in Helsinki, with international processing paths disclosed and a DPA working template published, so availability monitoring stays aligned with the same EU-first expectations you apply to application and customer data.
HTTP and port checks, three clear states
Use HTTP checks for sites, APIs and health endpoints; use port checks where network reachability matters. Each check reports up, down or degraded, so a slow or partial failure is not treated the same as a full outage. That distinction keeps your alerting meaningful and your on-call calmer.
Incident timelines that help you debug
A red badge is not enough; you need timing. MOJAQ records an incident timeline so you can see when a problem started, how it changed and when it recovered, then line it up against a deploy, a dependency issue or a traffic spike. Because monitoring sits beside your error tracking and deploy markers in the same platform, correlating downtime with the cause takes seconds, not a scavenger hunt across tools.
Questions
What can I monitor?
HTTP(S) endpoints, TCP ports and heartbeats (your cron job pings a URL; if the ping stops, you get alerted), with up, down and degraded states plus an incident timeline.
Where is my data stored?
In Helsinki, Finland, in the EU, with international processing paths disclosed and a DPA working template published.
What does it cost?
Free during the private beta. We do not promise a fixed free duration.