Status
The checks are running late.
Checked every five minutes from outside Oomira’s infrastructure. Uptime is the share of those checks that succeeded.
Websiteoomira.com/
Not checked recently
Last checked 70 minutes ago (3 Oct 2026, 21:35 UTC): HTTP 200 in 354 ms. Median response over the last 24 hours: 382 ms.
- Last 24 hours
- 100%
- 197 checks, since 3 October 2026
- Last 7 days
- 100%
- 197 checks, since 3 October 2026
- Last 30 days
- 100%
- 197 checks, since 3 October 2026
- Last 90 days
- 100%
- 197 checks, since 3 October 2026
APIoomira.com/api/v1/pricing
Not checked recently
Last checked 70 minutes ago (3 Oct 2026, 21:35 UTC): HTTP 200 in 623 ms. Median response over the last 24 hours: 353 ms.
- Last 24 hours
- 100%
- 197 checks, since 3 October 2026
- Last 7 days
- 100%
- 197 checks, since 3 October 2026
- Last 30 days
- 100%
- 197 checks, since 3 October 2026
- Last 90 days
- 100%
- 197 checks, since 3 October 2026
Uptime by month
Calendar months in UTC. The current month is to date.
| Month | Website | API |
|---|---|---|
| October 2026 | 100%197 checks | 100%197 checks |
Incidents in the last 90 days
An incident is two or more failed checks in a row. A single failed check counts against uptime above but is not listed.
No incident since the checks began on 3 October 2026.
How it is checked
Every five minutes a runner on GitHub’s network, separate from the hosting, database and network providers that serve Oomira, requests the homepage (https://oomira.com/) and the public pricing API (https://oomira.com/api/v1/pricing, past any cached copy, so the check reaches the application and its database). A check passes on an HTTP 2xx response within 20 seconds. Each result is recorded, and two failed checks in a row alert the founder by email.
A scheduled check that starts late or does not run is counted neither as up nor as down; the number of checks behind each figure is shown beside it. Questions about availability: [email protected].