OnlineOrNot Outage History
OnlineOrNot is up right nowPingoru has recorded 17 incidents for OnlineOrNot: 2 in the last 12 months and 0 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 531 (0%) |
Incidents, newest first
Critical November 18, 2025 Affected by Cloudflare incident 4h 50m Website
Started Nov 18, 2025, 12:19 PM UTC· resolved Nov 18, 2025, 05:09 PM UTC
- investigating Nov 18, 2025, 12:19 PM UTC
OnlineOrNot is currently being affected by https://www.cloudflarestatus.com/incidents/8gmgl950y3h7 It isn't possible to login to the dashboard, however uptime checks and heartbeat checks continue to run on AWS.
- resolved Nov 18, 2025, 05:09 PM UTC
This incident has been resolved.
Critical November 5, 2025 Status pages returning 500 5m Web app
Started Nov 05, 2025, 10:32 AM UTC· resolved Nov 05, 2025, 10:38 AM UTC
- investigating Nov 05, 2025, 10:32 AM UTC
We are currently investigating this issue.
- resolved Nov 05, 2025, 10:38 AM UTC
This incident has been resolved.
Major September 4, 2025 SSL certificate failed to re-issue for onlineornot.com –
Started Sep 04, 2025, 02:30 AM UTC· resolved Sep 04, 2025, 02:30 AM UTC
- resolved Sep 04, 2025, 05:22 AM UTC
Between Sep 4, 2025, 2:32:20 AM UTC and Sep 4, 2025, 5:17:30 AM UTC, OnlineOrNot's frontend was unavailable (hosted at https://onlineornot.com) due to an SSL certificate failing to renew on the platform-as-a-service (PaaS) we use as a host. We will be taking corrective measures to ensure this doesn't happen again.
Minor September 2, 2025 Browser Check false-positives 4m
Started Sep 02, 2025, 09:48 AM UTC· resolved Sep 02, 2025, 09:52 AM UTC
- resolved Sep 02, 2025, 09:55 AM UTC
Between 09:48 UTC and 09:52 UTC, a bad release of OnlineOrNot's Browser Checks resulted in false-positive alerts. The release was immediately detected and rolled back.
Minor August 21, 2025 Web app performance degraded 13m Website
Started Aug 21, 2025, 07:40 PM UTC· resolved Aug 21, 2025, 07:53 PM UTC
- investigating Aug 21, 2025, 07:40 PM UTC
Related to the incident earlier - https://status.onlineornot.com/incidents/8tf9dzsjrkhv
- monitoring Aug 21, 2025, 07:44 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Aug 21, 2025, 07:53 PM UTC
This incident has been resolved.
Minor August 21, 2025 Uptime checks and Heartbeat checks degraded 1h 18m Website, Uptime Checks, Heartbeat Checks
Started Aug 21, 2025, 06:20 PM UTC· resolved Aug 21, 2025, 07:39 PM UTC
- investigating Aug 21, 2025, 06:20 PM UTC
We are currently investigating this issue, it looks related to https://www.cloudflarestatus.com/incidents/d9n3g1vnxdd2.
- identified Aug 21, 2025, 06:52 PM UTC
The website is also affected.
- resolved Aug 21, 2025, 07:39 PM UTC
We've fallen back to a secondary provider, checks are running again. The web app's performance is still degraded, but will raise a separate incident for that.
Critical August 12, 2025 Issues with login detected 1h 8m Website
Started Aug 12, 2025, 09:01 AM UTC· resolved Aug 12, 2025, 10:09 AM UTC
- investigating Aug 12, 2025, 09:01 AM UTC
We are currently investigating this issue.
- investigating Aug 12, 2025, 10:09 AM UTC
We are continuing to investigate this issue.
- resolved Aug 12, 2025, 10:09 AM UTC
This incident has been resolved.
Minor March 17, 2025 Degraded performance across heartbeat and uptime checks 2d 3h Uptime Checks, Heartbeat Checks
Started Mar 17, 2025, 03:27 AM UTC· resolved Mar 19, 2025, 07:00 AM UTC
- investigating Mar 17, 2025, 03:27 AM UTC
OnlineOrNot has experienced waves of degraded performance across heartbeats and uptime checks in the last 24 hours, with the worst of it happening between: - 2025-03-16T10:30 UTC and 2025-03-16T19:05 UTC - 2025-03-17T01:50 UTC and 2025-03-17T13:25 UTC Our fallback systems have been turned on and are currently handling the load.
- identified Mar 17, 2025, 04:01 AM UTC
The underlying issue has been identified as an issue originating with Cloudflare's Hyperdrive service (https://www.cloudflarestatus.com/incidents/xcjxbfgs135k). OnlineOrNot will continue to run from its fallback systems until Hyperdrive is confirmed to be stable again.
- resolved Mar 19, 2025, 07:00 AM UTC
This incident has been resolved.
Notice January 16, 2025 Degraded performance for Uptime Checks 4h 32m
Started Jan 16, 2025, 05:00 PM UTC· resolved Jan 16, 2025, 09:32 PM UTC
- resolved Jan 17, 2025, 08:14 AM UTC
On 2025-01-16, between 18:05 UTC and 21:32 UTC, OnlineOrNot had degraded performance in its uptime checker. During this incident, uptime checks would take longer than usual to complete (often taking several minutes rather than the usual 30 seconds between checks). The root cause was a loss of connectivity between our Cloudflare Workers service, and the AWS database that stores metadata about uptime checks. There was a replica system ready to run in AWS, however due to a misconfiguration it could not start automatically. The misconfiguration has been fixed, and OnlineOrNot will run regular (monthly) drills to ensure the fallback system functions as expected.
Notice November 12, 2024 Status Pages and Public API were inaccessible 12m
Started Nov 12, 2024, 05:57 PM UTC· resolved Nov 12, 2024, 06:09 PM UTC
- resolved Nov 12, 2024, 06:54 PM UTC
OnlineOrNot's status pages, and the public API were unavailable between 17:57 and 18:09 UTC due to several nodes simultaneously failing. OnlineOrNot will be adding additional nodes to failover to ensure this does not happen again.