Internal status page software for IT teams and employees
UptimePilot gives an IT team a password protected status page for the systems employees depend on: VPN, email, single sign-on, the intranet, the ticket portal and the payroll app. The page updates from live monitors, your team posts incident updates in a few clicks, and employees stop opening tickets to ask whether something is down. Password protected pages start on the Business plan at $124 a month billed yearly.
Why IT teams lose hours to "is it down" tickets
When the VPN drops or the mail relay stalls, the first twenty minutes are rarely spent fixing it. They go to answering the same question in chat, by email and at the service desk: is it just me. Every duplicate ticket pulls an engineer away from the cause, and the tickets arrive faster the bigger the company gets.
An internal status page moves that answer to one address everybody knows. Employees check it before they write, the service desk links to it in the auto reply, and the incident owner posts one update instead of forty.
Most teams try to solve this with a pinned chat message or a shared document. It works until the outage hits the chat tool itself, or until nobody remembers to edit the document. A page fed by monitors changes state on its own, so the first signal does not depend on someone noticing.
What belongs on an internal status page
Group components the way employees describe their problems, not the way your infrastructure is laid out.
| Component | How UptimePilot watches it | What employees see |
|---|---|---|
| VPN gateway | TCP port check on the public gateway address, confirmed from two regions | Remote access operational or degraded |
| Email and calendar | HTTPS check on the webmail login page plus a keyword check | Email operational or outage |
| Single sign-on | HTTPS check on the identity provider login page with an expected keyword | Sign-in operational or outage |
| Intranet and wiki | HTTPS check with a keyword that only a working page contains | Intranet operational or outage |
| Ticket portal and HR apps | HTTPS and keyword checks on each portal | One line per app |
| Nightly jobs, backups and syncs | Heartbeat monitor that the job pings when it finishes | Late or missed runs flagged before the morning |
| Certificates and domains | SSL and domain expiry monitors | Warnings 30 days ahead, before a sign-in page breaks |
One honest limit. UptimePilot checks run from outside your network, the way a remote employee connects. A service that is only reachable from the office LAN cannot be probed directly. For those, use a heartbeat that a script inside the network pings on a schedule, or monitor the public gateway that sits in front of the service.
-
01
Create the page and put a password on it
Add a status page, name it the way employees will search for it, and turn on password protection. Only people who have the password can read it, and only team members with the right role can publish. Put it on a short address such as status.yourcompany.com with a custom domain, which Team plans and higher include.
-
02
Link monitors to components
Each component follows its monitors. If the VPN gateway fails both regions, the component turns red without anyone touching the page. During planned work, a maintenance window pauses alerts and shows the work as scheduled maintenance instead of an outage.
-
03
Tell people where to look
Link the page in the service desk auto reply, the intranet header, the onboarding email and the pinned chat message. Alerts reach the on-call engineer by email, SMS, Slack, Microsoft Teams or webhook, with escalation when nobody acknowledges, so the page and the person fixing the issue stay in step.
-
04
Post updates in plain words
Name the impact as employees feel it: cannot sign in, shared drive is read only, calendar invites are delayed. Say what you know, give a time for the next update, and close the incident when service is back. The history stays on the page as a record, which is also the evidence for your monthly availability report.
Internal status page options for IT teams
The right choice depends on whether you need to monitor your own systems, aggregate vendor status, or run a full service management suite.
| UptimePilot | Status aggregators | ITSM suites with status pages | |
|---|---|---|---|
| Watches your own systems | Yes, with uptime, keyword, port, SSL, domain and heartbeat checks | Mainly reads vendor status pages such as Microsoft or Google | Usually depends on connected monitoring tools |
| Page updates from live checks | Yes | From vendor feeds | Varies by product |
| Password protected page | Business and Enterprise | Paid tiers | Included in the suite |
| Best for | IT teams that own the systems and want the page and the monitoring together | Teams that mostly depend on SaaS vendors and want to know when they fail | Large IT departments that already run an ITSM platform |
| Pricing model | Per plan, members included | Per plan or per service | Per agent seat |
If your employees mostly lose time to outages at Microsoft, Google or Slack, an aggregator that reads those vendors' status pages is the better fit, and it can sit alongside UptimePilot for the systems you run yourself.
Who buys an internal status page
- IT managers at companies with 50 to 2,000 employees who field the same outage tickets repeatedly.
- Managed service providers that give each client a private page for its own staff, covered on MSP uptime monitoring.
- Platform and DevOps teams that want engineering to see build, staging and deployment status in one place.
- Agencies that need a client only page behind a password, described on white label status pages.
What an internal status page costs
Pricing is per team with members included. Every limit is on uptime monitoring pricing.
- Team, $99 a month or $49 a month billed yearly: 200 monitors, 5 status pages with custom domains, 10 members, public pages.
- Business, $249 a month or $124 a month billed yearly: 1,000 monitors, 20 password protected status pages, 25 members, REST API. The plan for private internal pages.
- Enterprise, $599 a month or $299 a month billed yearly: 3,000 monitors, 50 status pages, 100 members, SSO (SAML) for your team and an audit log.
A typical IT team with a VPN, mail, sign-in, an intranet and ten internal apps needs fewer than 60 monitors, so Business leaves room for client or department pages on top. For the public side of the same tool, see the status page app.
01
What is an internal status page?
An internal status page shows employees whether company systems such as the VPN, email, sign-in and intranet are working. It is private, usually behind a password or single sign-on, and it carries incident updates from the IT team so staff can check it before filing a ticket.
02
Who needs an internal status page?
IT teams that field repeated "is it down" tickets need one most. It also suits managed service providers, platform teams and any company where an outage of a shared system stops many people at once. If employees already ask in chat whether something is broken, you need the page.
03
Can I password protect a status page in UptimePilot?
Yes. Password protected status pages are included on Business, with 20 pages, and on Enterprise, with 50 pages. Team plans include public pages with custom domains. Only team members with the right role can publish incidents.
04
How do I monitor internal services that are not on the public internet?
UptimePilot checks run from outside your network. For services reachable only inside it, have a script or scheduler ping a heartbeat URL on a schedule and alert when it goes missing, or monitor the public gateway, such as the VPN or reverse proxy, that sits in front of the service.
05
How is an internal status page different from a customer status page?
The tooling is the same, the audience and the wording differ. A customer page is public and describes product impact. An internal page is protected and covers employee tools. Many teams run both from one UptimePilot account with shared monitors.
Stop answering "is the VPN down" in chat
Add your monitors, publish a password protected page and give employees one address to check first.