Network status

Network status.

Live uptime for five public checks covering this website, contact API reachability and the Guest WiFi demonstration routes. Separate private checks watch the services behind them. The board also shows how our monitoring approach works in practice.

-
Loading live data…
  • netintellect.co.uk
    -
  • API endpoint · reachability check
    -
  • Captive-portal API
    -
  • Captive-portal bridge
    -
  • Captive portal demo
    -

Updated every 10 minutes by a small Cloudflare Worker we run on the same edge that fronts the rest of the site.

How this page works

A Cloudflare Worker checks these endpoints every 10 minutes. Each uptime percentage is the proportion of recorded checks that succeeded over the last 30 days, or the available history if a check is newer. The overall figure is the average across the five public checks. Short interruptions between checks may go undetected. Results are stored in Cloudflare KV and read by this page; customer project licences and optional ongoing care are quoted separately.

What we monitor here

Five public checks cover the routes a prospect, client or venue would care about being reachable:

  • Marketing site. netintellect.co.uk, our public website served through Cloudflare Pages.
  • API endpoint. An OPTIONS request confirms that the contact Function is routed and answering. It does not submit a form or test Turnstile, email delivery or the complete send path.
  • Captive-portal API. The route from a customer-style domain through the VPS to the portal Worker.
  • Captive-portal bridge. The customer-domain and VPS web-server leg, checked separately so a disagreement helps locate a fault.
  • Captive portal demo. The demonstration Worker health check, reached through a Cloudflare service binding.

Separate private checks watch supporting service health and security conditions. Operational details and internal alerts stay off this public board. We can explain the monitoring design on a call.

Maintenance & auto-updates

Maintenance can interrupt a service. If a recorded check fails during maintenance, it counts as a failure in that service's uptime figure.

1. Nightly auto-updates (recurring)

Scheduled overnight updates can restart self-hosted services. A restart that falls entirely between two checks will not appear as downtime in this sampled record.

2. One-off planned work (announced)

Planned work affecting the public services will be listed here with the affected service, expected window and a summary of the change. If a check is paused, it produces no samples during that period; the percentage is based on the checks that were recorded, not an exact count of available minutes.

Upcoming windows: none currently scheduled.

Past incidents

This page does not yet publish a complete incident log. The board above shows current check results and sampled availability, which cannot establish that every service was uninterrupted between checks.

Monitoring and managed care

Define what needs watching before choosing the checks.

List the network, applications, backups and public services that matter. The proposal will show what is monitored, what maintenance covers and when a person steps in.

Discuss a care plan
  1. 01List what mattersNetwork, applications, backups and public services.
  2. 02Define the checksAlerts, maintenance and who responds.
  3. 03Review the care planOngoing work is scoped separately from the build.