Skip to content

The port is open. The service is not running.

Check first, sign up later

One check, no account. You see on which of the three levels your service responds.

Shop https://shop.example.net Simulation

One check per minute, in time-lapse. Bar height = level reached.

Port checkTCP :443
40 of 40 green
portslieHTTPS + content
Incident 13 minutes
  1. Database gone, error page with HTTP 200.
  2. Second bad check: alert to Discord.
  3. Level 3 reached: resolved.
    Discord · #server-status Outage: Shop Level 2 of 3 — responds, content implausible

    From production 1,870 checks in the last 24 hours 23 incidents in the last 30 days with the port open and a service that did not answer properly (level 1 or 2 of 3) Our own test targets not counted, at most 15 minutes old.

    • WebsiteContent and certificate
    • Error pagedespite HTTP 200
    • DNSA and AAAA
    • PingICMP
    • Minecraft JavaServer List Ping
    • Minecraft BedrockRakNet ping
    • FiveM/info.json
    • RedM/info.json
    • CS2A2S_INFO
    • RustA2S_INFO
    • Garry's ModA2S_INFO
    • EnshroudedA2S_INFO
    • TeamSpeakVoice-Init
    • SatisfactoryQuery API
    • PanelHTTP answer

    What it looks like when you are signed in

    All targets on one page, the last 24 hours per target, all incidents with duration and the exact message.

    Overview with five targets: four OK, one Minecraft server at level 2, above it a banner with the open incident.

    Screenshots of the real interface with sample data. The addresses come from ranges reserved for documentation.

    Your visitors see the status without you having to answer

    Every account gets a public status page: your name, your logo, your colour, plus history and disruptions. You choose which targets appear. It never shows addresses or ports. If you have your own domain, you can run it under status.deinprojekt.de (Small and Large plans). On your own website you place a small status badge.

    All about the status page
    Clickable example with made-up data. Theme, colour and “Disruption” at the top can be switched.

    Your services, one probe, your Discord

    portslie asks every service the way visitors or players reach it, at your plan's interval. If a target drops below level 3 twice in a row, exactly one message goes out, to Discord or by email. The all-clear comes as soon as it answers again.

    The three levels in detail

    For the evening something hangs

    What portslie can do today. All of it is built, none of it is an announcement.

    One alert per outage

    One message for the outage, one for the recovery. Quiet in between, even if the service is gone for an hour.

    Three levels instead of green or red

    Port, protocol, content. You see how far a service got.

    1. Port reachableopen
    2. Protocol respondsno answer
    3. Content plausiblenot reached
    How it works

    Asks the service itself

    The same query browsers or game clients send.

    HTTPS → 200 · certificate 61 days
    All check types

    Measured, not claimed

    For almost five days we checked a web server as if it were a Minecraft server (example.com:443). A port check would almost always have reported green.

    Checks
    1,293
    Port open
    1,288
    Valid answers
    0

    20–Sep 24, 2026, every 5 minutes · Raw data

    10 targets free. More when you need more.

    • Free 0 €permanent 10 targets · every 5 min
    • Small 4.90 €per month 15 targets · every 1 min
    • Large 12.90 €per month 60 targets · every 30 s

    All plans measure the same way, on all three levels. They differ in number of targets, interval and history.

    Compare plans

    Know before your visitors notice.

    10 targets are free. You see the first result after the first check.

    10 targets · checked every 5 minutes · no payment details