Is Tilroy down?

Last checked 2m ago
Current status
Tilroy is up

No incidents right now.

Official status page: https://tilroy.statuspage.io · Polled every 5 minutes · 3 components tracked

Tilroy is operational right now. Last checked 2m ago; the most recent incident resolved 26d ago.

Real-time Tilroy status, recent outages, and incident history — pulled directly from Tilroy's official status page at https://tilroy.statuspage.io every 5 minutes. Pingoru tracks 3 Tilroy services and has captured 8 incidents in the last 90 days (97.78% uptime). Get email, Slack, Discord, or webhook alerts the moment Tilroy reports a new incident — free for 5 monitors, no credit card.

Users who monitor Tilroy also follow these eCommerce services: Shopify Stripe PayPal Blackbaud NetSuite Squarespace BigCommerce Cybersource Gorgias PayFast View all 6,000+ providers
Tilroy uptime 97.78% uptime · past 90 days
Mon Wed Fri
MarAprMayJun
Less More

Recent outages & incidents

Past 90 days
  1. Resolved
    Started May 18, 2026, 01:56 PM UTC · Resolved May 18, 2026, 01:53 PM UTC
    Timeline · 1 update
    • resolved · May 18, 2026, 01:56 PM UTC

      All offline sales are not yet processed , this will take until closing hours of the stores. The could result in wrong moneycounts this evening when closing the till. If you skip the moneycount today, tomorrow these will be fine. If you execute money count today, this will also be wrong tomorrow. Contact support for more information.

    Latest: All offline sales are not yet processed , this will take until closing hours of the stores. The could result in wrong moneycounts this evening when closing the till. If you skip th…

  2. Resolved 1h 4m
    Started May 18, 2026, 11:16 AM UTC · Resolved May 18, 2026, 12:21 PM UTC
    Point Of SaleData management and reporting
    Timeline · 7 updates
    • investigating · May 18, 2026, 11:16 AM UTC

      We are notified for slower Tilroy performance. This is under investigation.

    • investigating · May 18, 2026, 11:18 AM UTC

      Tilroy not available at the moment.

    • investigating · May 18, 2026, 11:44 AM UTC

      A problem was identified with one of the databases. The system is online again.

    • monitoring · May 18, 2026, 11:44 AM UTC

      A fix has been implemented and we are monitoring the results.

    • monitoring · May 18, 2026, 12:06 PM UTC

      We are continuing to monitor for any further issues.

    • resolved · May 18, 2026, 12:21 PM UTC

      This incident has been resolved.

    • postmortem · May 19, 2026, 05:42 AM UTC

      **Summary** On Monday 18 May 2026 around 13:00 \(local time\), our production database became unavailable for 26 minutes. The cluster recovered automatically and was fully back in service by 13:43. No data was lost. **Background** Our database runs as a three-node cluster: three identical copies of our data, kept in sync across three separate servers. One node is the primary - it accepts new data. The other two are secondaries - they continuously copy the primary. At least two of the three nodes must be online for the cluster to keep accepting data. If only one remains, the cluster intentionally stops, to prevent the servers from disagreeing on what the latest data is. What happened at around 13:05, the primary node started to slow down and stopped responding to the other two. Within seconds, the cluster automatically promoted one of the secondaries to be the new primary,a routine failover that should have been invisible to users. This time the failover did not complete cleanly. The new primary inherited a large backlog of unfinished work from the old primary and became overloaded while trying to clear it. At 13:14, the new primary hit a built-in safety mechanism : when a node is stuck and cannot complete its role change within 30 seconds, it shuts itself down so the rest of the cluster can move on. About 30 seconds later, at 13:15, the original primary, still trying to step down, hit the exact same safety mechanism and also shut itself down. With two of the three nodes down at the same time, the cluster fell below the two-node minimum and stopped accepting reads and writes. Recovery automatically restarted both failed nodes. They came back online around 13:40, a new primary was elected, and full service was restored at 13:43, with no manual intervention required. **Next steps** We are working together with our database supplier to identify the underlying root cause, it could be hardware related. A follow-up will be shared once those findings are confirmed

    Latest: **Summary** On Monday 18 May 2026 around 13:00 \(local time\), our production database became unavailable for 26 minutes. The cluster recovered automatically and was fully back in …

  3. Resolved 1h 18m
    Started May 11, 2026, 11:17 AM UTC · Resolved May 11, 2026, 12:35 PM UTC
    Point Of SaleE-commerceData management and reporting
    Timeline · 3 updates
    • investigating · May 11, 2026, 11:17 AM UTC

      We noticed slower Tilroy performance related to customers. This is under investigation.

    • monitoring · May 11, 2026, 11:45 AM UTC

      A fix has been implemented and we are monitoring the results.

    • resolved · May 11, 2026, 12:35 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  4. Resolved 34m
    Started Apr 09, 2026, 10:27 AM UTC · Resolved Apr 09, 2026, 11:01 AM UTC
    Point Of Sale
    Timeline · 2 updates
    • investigating · Apr 09, 2026, 10:27 AM UTC

      We are currently investigating this issue.

    • resolved · Apr 09, 2026, 11:01 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  5. Resolved 23m
    Started Apr 09, 2026, 09:27 AM UTC · Resolved Apr 09, 2026, 09:51 AM UTC
    Point Of SaleData management and reporting
    Timeline · 4 updates
    • investigating · Apr 09, 2026, 09:27 AM UTC

      We are receiving messages of slow performance or broken images. this is under investigation

    • identified · Apr 09, 2026, 09:39 AM UTC

      The issue has been identified and a fix is being implemented.

    • monitoring · Apr 09, 2026, 09:42 AM UTC

      This should be ok now

    • resolved · Apr 09, 2026, 09:51 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

See the full Tilroy outage history

3 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Tilroy outage history →

Or sign up free to get alerts when Tilroy breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 8 incidents View full outage history →