Device ingestion and dashboard API (api.pidgeiot.com)
Operational for 68 min · 9 ms · HTTP 200 · 100% over 1 day
Sign-in, registration and session checks (auth.pidgeiot.com)
Operational for 68 min · 737 ms · HTTP 200 · 100% over 1 day
The web dashboard and marketing site (pidgeiot.com)
Operational for 68 min · 19 ms · HTTP 200 · 100% over 1 day
No incidents reported.
Each system above is checked every five minutes from Cloudflare's edge by requesting a public URL that real traffic already depends on. A check that fails is retried once before anything is reported as down, so a single dropped packet does not publish an outage.
Operational means the check succeeded. Degraded means it succeeded but took over two seconds, or it failed once and then succeeded. Down means two consecutive checks failed. Uptime figures count degraded time as available.
This page runs on its own Cloudflare Worker with its own storage, entirely separate from the platform it reports on, so it stays up when the product does not. It cannot see problems that its checks do not cover, which is what the incident reports above are for.
Machine-readable version: /status.json.
Email support@pidgeiot.com, or use the contact form for anything with details worth structuring. PidgeIoT is run by one engineer, so expect a reply within two business days rather than in minutes.
Include your account email, the flock or pigeon id involved, what you expected, what happened, and the time it happened in UTC. Never include a device token or any other credential.