TCP Port Monitoring. Every service covered, no protocol required.
Databases, caches, message queues: Uptimeify runs a TCP check against any hostname and port your clients operate, polled from European nodes, and tells you about the outage before it becomes a ticket.
Made and Hosted in the
European Union
GDPR-Compliant Hosting
in Germany
GEO-Redundant Replica
across the EU
One monitor for any port. From database cluster to custom build.
Redis on 6379, Postgres on 5432, a custom build on 9000: half of your clients' infrastructure speaks neither HTTP nor one of the classic mail and transfer protocols. The TCP port monitor opens a real connection to any hostname and port combination you configure, closing the gaps no dedicated monitor covers.
- Any hostname and port: so you cover
redis.deinkunde.com:6379the same way as a custom service on an exotic port. - Intervals from 1 minute: so you check critical services tightly and quieter systems at a calmer pace.
- Port-only mode everywhere: so SSH, SMTP, FTP, and IMAP/POP monitors can drop to a plain port check when a full protocol login isn't needed yet.
A full TCP connect (SYN, SYN-ACK, ACK) opens on the configured port, no half-open scanning.
Timeout per connection attempt is configurable, check intervals run from 1 minute.
Open doesn't mean healthy. The banner tells you.
An open port only proves that something answered, not that the right service is running. Uptimeify optionally reads the banner the service returns after connect and matches it against your expectation. You'll know when whatever is listening on db.deinkunde.com:5432 is no longer Postgres.
- Optional banner match: so you confirm the expected service is responding, not just that the port is open.
- Separate failure states: so you distinguish refused connections from timeouts and narrow down the cause faster.
- Clean incident history: so your report proves when the service dropped and when it recovered, not just that it was gone.
After a successful connect, the check reads the first server response and matches it against your expected string.
No match means failure, even on an open port, a foreign process on the right port doesn't pass as up.
Without a configured banner, the check stays a pure connect test.
Confirmed by multiple EU nodes. Alerts only on real outages.
A single failed connect is not an outage. Every failure is confirmed from multiple European locations before an incident opens. You get alerted on real downtime, not network blips, and your client hears it from you, not the other way around.
- Multi-location consensus: so a single routing hiccup doesn't wake you at 3 a.m.
- Regional probes: so you scope checks to specific EU regions and map firewall rules cleanly.
- 29 alert channels with escalation: so the right person reacts before your client notices anything.
Polling runs from 7 locations in 6 countries, Falkenstein, Nuremberg, Zurich, Prague, Helsinki, Milan, Warsaw.
An incident opens only after confirmation from multiple locations, never from a single failed connect.
Checks can be scoped to individual regions, and worker IPs are published at uptimeify.io/ips.txt, straight into your firewall allowlist.
Success Kit
We don't just monitor. We help you sell.
Every Uptimeify subscription includes access to our Success Kit, a collection of battle-tested resources to turn your monitoring into a profit center.
Service Level Agreement templates to define professional boundaries with your clients.
Find the sweet spot for your care plans. Calculate margins based on check frequency and support hours.
Powerpoint Templates that explain 24/7 monitoring to non-technical clients. Close more retainers.
Use automated reports to proactively communicate value, so clients never ask what they're paying for.
Ready to turn monitoring into a profit center?
Claim your Success Kit and start scaling today.
Frequently Asked Questions
Any service reachable over TCP, databases like Postgres, MySQL, or MongoDB, caches like Redis, message brokers, legacy applications, or custom builds. You configure a hostname and port, for example db.deinkunde.com:5432, Uptimeify opens the connection and reports the moment the port stops answering. That covers the services no dedicated protocol monitor exists for.
A ping (ICMP) verifies that the host is reachable on the network. The TCP check goes one layer deeper, it confirms that a service on a specific port accepts the connection. A server can happily answer pings while the database on port 5432 has been down for an hour. Only the TCP check surfaces that difference, and both together give you the full picture.
Every failed check is confirmed from multiple EU locations before an incident opens and alerts fire. Polling runs from 7 locations across 6 European countries. A single network blip between one node and your server never triggers an alert, so every notification that reaches you is a real one.
Yes. Status pages run on your own domain, PDF reports carry your logo, and your clients get access through isolated sub-accounts. Your client sees your monitoring service, not ours, so the work you do builds your brand.
Yes. Uptimeify runs on a European-only stack, hosted in Germany, geo-redundantly replicated across the EU, without US sub-processors with access to your monitoring data. That minimizes third-country transfer risk and gives you a clear answer when a client asks where their data lives.
Ready to see every port your clients run?
One monitor for every TCP service in your portfolio, branded as your service, polled from the EU. Get started in minutes and close the last blind spot in your stack.