Plantech ERP Status
Live health of the Plantech Kenya nursery ERP, storefront and customer portal.
Open ERP →

Core platform

ERP application (139.84.245.114)
Live ERP app server — responding and serving pages.
Operational
99.82% uptime 526 ms
ERP database
Live PostgreSQL probe via the app health endpoint.
Operational
DB connected app uptime 4h 15m
99.83% uptime 527 ms
Website & staff sign-in
Public site and ERP staff login at planseedgrow.com.
Operational
99.99% uptime 111 ms

Customer-facing

Storefront
Public seedling catalogue at /shop.
Operational
99.99% uptime 180 ms
Customer portal
Grower account sign-in at /account/login.
Operational
99.99% uptime 134 ms

Release notes & version log

2.3.1 August 30 2026
FeatureFix

Mobile, Seed Store and "sow" much more

  • MOBILE APP (ANDROID)
  • • Plantech ERP now installs as a home-screen app on Android: open the site in
  • Chrome, tap "Install Plantech on this phone". Full screen, Plantech-green
  • status bar, app shortcuts (Scouting, Scan batch, Seed Spot, Deliveries).
  • • Works offline: the app opens without coverage and anything saved in the
  • field syncs automatically when the connection returns.
  • GERMINATION SCOUTING (NEW, MOBILE)
  • • Scouts sample a few trays per order ~14 days after sowing; the mobile app
  • computes the success rate — one loss field per sampled tray, each with
  • its own photo.
  • • Photos are stamped with the order, tray, declared dead count and date;
  • the untouched high res original is kept alongside.
  • • The due list builds itself — no walking the greenhouse to find what to
  • check. Orders past their window flag as missing. Greenhouse and client
  • filters remember each scout's last choice.
  • • Early checks are allowed but marked, so a low early count is never read
  • as final germination. Rechecks (+1/+2/+3 weeks) stay out of the daily
  • queue until their day, then raise a revisit alarm.
  • • Crop issues (disease, pests, damping off…) can be reported with any
  • reading — an issue on a healthy rate shows as "issue", not "low".
  • LIVE SCOUTING (New Module)
  • • A live feed of scout reports as they come in — defaults to the last
  • 24 hours with range, status, scout, crop and issue filters plus search.
  • Any row opens the full report with photos and the weather at entry.
  • • Alert rules are configurable: below 85% flags and alerts Production;
  • below 80% sends an immediate heads-up to Sales, Production and
  • Management; issue reports alert Production. Every rule's threshold,
  • seed-origin scope, severity and departments can be edited.
  • • Local weather (temperature, humidity, wind, rain) is captured
  • automatically on every scout entry. (we used local meteo weather reported from a station at Karagite, might be a little different than on the farm)
  • • Weekly germination report: emails itself on a chosen day with the plain
  • Excel attached, or runs on demand. A printable digest adds a one-page
  • summary cover — stats, varieties to watch, issue patterns, best/worst
  • photos — with the individual reports from page 2, so you can print just
  • the summary. Admins also get per-scout performance: reporting pace,
  • over/under-reporting vs the team per crop, and reported rates checked
  • against the final out-turn of finished batches.
  • PRODUCTION PHASES
  • • Ready orders no longer offer phase buttons — the cycle closes at Ready.
  • • Sowing runs itself: it starts when seed is issued and completes at
  • Planting Confirmation using the confirmed count; the next phase starts
  • automatically and notifies its department. Partial sowings stay open.
  • Manual handovers (two-agronomist rule) are unchanged from Germination on.
  • SEED STORE
  • • Supplier is now mandatory when receiving Plantech-owned seed.
  • • Seed Balances (renamed) now includes Plantech stock alongside client
  • balances, each with a printable per-lot item ledger — every motion in
  • and out, with dates, quantities, who did it, and a running balance.
  • Ledger filters are type-to-find (built for a 10k+ client book).
  • • Expiry dates on lots, days-in-store tracking, and automatic alerts for
  • low stock (per variety per holder), approaching expiry, and overstay.
  • • FIFO issuing: lots list oldest-first; issuing past an older lot is
  • allowed but permanently recorded as a FIFO bypass.
  • • Abnormal deviation (beyond ±5%) shows red on Movements by PO; clicking
  • a row opens a summary with an undo option while sowing is unconfirmed.
  • • Seed audit (admin): 90 days of per-person patterns — deviations, seed
  • issued but never sown, FIFO bypasses, write-offs, undo habits,
  • reference-weight edits, off-hours motion — with a watchlist on top.
  • • Seed Spot (new): blind spot-check audits. Random lots at a random time;
  • the checker scans, weighs and photographs without ever seeing book
  • values, and every result reads the same. Deviations alarm Management
  • silently. Cadence, lot count and tolerance are admin settings.
  • LABELS & PRINTING
  • • Mobile receipt printers (Zebra ZQ511) supported over the print bridge,
  • with a step-by-step setup guide, receipt templates (Payment, Delivery,
  • Order) and demo 3" slips. Receipts print with a proper top margin.
  • • Office document printers (HP/Lexmark class) supported for page-size
  • forms on 8.5×11 over the same bridge, with reachability monitoring
  • (green/red status per printer).
  • • Label designer: fields can be centre/right aligned so real data stays
  • centred instead of overrunning; elements snap to a grid; barcodes can
  • show or hide the human-readable line; clicking a template opens the
  • designer directly.
  • REPORTS
  • • Germination Success report (matches the requested layout) with Excel
  • export, plus the printable weekly digest above. Print output uses
  • darker text for clean paper copies.
2.1.2 August 8 2026
Feature Fix

Mother Stock — full rework Part 1

  • Batch-first inventory — mother plants are tracked as planted batches: Client, Crop, Variety, Planting week, Pots, Plants/pot, Total plants, Pot type, Location, Age in weeks, Variety PC and Batch PC. Click any row for the batch card and full cuttings log.
  • Pots on tables — a batch's pots can sit on one table or spread across several, with pots moved between tables at any time.
  • Space in m² — each pot type carries a footprint in m² and each table an area; the Table space board shows area, occupied, free and fill % per table. Four pot types are pre-loaded (4L pot, 5L pot, 6L bag, 17L pot) with placeholder footprints — adjust in Catalog → Containers.
  • Real productivity (PC) — cuttings per plant per week is computed from the actual harvest log, averaged over recorded weeks only so unrecorded weeks never drag the number down; every figure shows its coverage, e.g. "2.25 (2/8 wks)". Variety PC covers the client's variety across all batches; Batch PC scores a single planting.
  • Cuttings harvested form — searchable client list (mother-stock clients only) → crop → variety → week-tracked date → quantity, with both recording styles: per batch (when counted separately) or per client-variety (when batches weren't split). Purpose now includes Maintenance for cuttings harvested and trashed — the week still counts as recorded.
  • Cold room stock control — harvested cuttings stock in as batches with a printable QR sticker, and stock out in partial quantities with a destination and running balance; taking more than the balance is refused. Manual stock-in supported; every batch keeps its full in/out history.
  • Mobile — the harvest form and a new Cold room screen (scan the sticker → stock out) work from the phone, offline-capable like the rest of the mobile app.
  • Order intake per contract — mother-stock orders capture pot type (with "➕ New pot type…" right in the menu), number of pots, plants per pot, cost per pot per month, service start and end dates, and renewable-yearly. Registration requires confirming how propagation is billed — included in the pot price or charged separately with its one-time fee — and the printed hosting agreement reflects all of it.
  • Billing — the monthly hosting invoice uses the contract rate when one is set (price list otherwise), still pro-rated by day for pot changes; a separate propagation fee is billed once on the first invoice and never again. A renewal alert fires 30 days before the service end date.
  • Product card — mother-stock fields on every variety: MaxP/C, weeks to reach it, MS lifespan and MS comments; batches past their lifespan are flagged. "Service" is now available as a product line for pricing mother-stock activities.
2.1.1 August 7 2026
Feature

Further updates to the seed store logic and a few fixes here and there

  • Client Orders & Production
  • Paste-from-Excel uses the full order template: Variety Code | Tray code | Requested Qty | Sow Max | Unit | Seeds per cell | Seed Origin | Comments | Production location (cuttings)
  • Daily Sow Program report: per-day sowing list with requested / planned / sown, statuses Sown / Partial / Not sown / Re-planned, date & client-type filters
  • Partial sowings can close at the sown quantity and re-plan the remainder as a linked child planning order — parent and child both visible, nothing lost
  • Orders still at zero sown after their scheduled date are flagged red for follow-up
  • Order amendments: pick the exact fields to change, give a reason, manager approves, changes apply automatically with a full record
  • "Delivery needs confirmation" flag on orders — Logistics is alerted, gets a queue with client phone numbers, and settles each as delivery, pickup, or confirmed
  • Crop codes now follow a series: SE-TOM0002 / CU-MUM0001 (line prefix + family code + number), assigned automatically at registration — also fixes the crops paste error
  • "Name" column renamed to "Crop" on Crops & Varieties
  • Growing phases configured per variety on the product card, with one-click standard sets (Sowing→Growing / Sticking→Growing) and durations
  • Custom one-off phases with their own duration can be added at production-order level
  • Sowing/sticking more than 1 day after seed issue raises a "sowing overdue" alert
  • App-wide
  • All dates and times display in Kenya time (Africa/Nairobi), everywhere — including the wallboard clock
  • Night mode: 🌙 toggle in the bottom-right corner, remembered per browser
  • Product and seed-lot cards lock the page behind them (no background scrolling)
  • Administration
  • Click a user's row to edit them (old bottom button strip removed)
  • Deleting a user archives them: sign-in blocked, hidden from lists, all history kept, reversible
  • Data migration page: Excel templates + paste-import for Customers, Locations, Products, Growing Phases
  • Seed Store
  • Receiving is a motion with a type: Input (receive seeds) or Output (reduce/retire stock with a mandatory reason)
  • Package fields at receiving: number of packages + empty package weight → net weight computed automatically
  • Seeds quantity computed from net weight via the reference weight W1000; a hand-counted figure overrides it
  • Lot number mandatory at receiving ("NA" accepted); duplicate lot numbers allowed across clients
  • Client-specific seed locations — client seed defaults to the client's own shelf; lots managed and picked by location + variety
  • Tiny seeds can be received and issued by seed count alone (no reference weight)
  • Movements shown one line per PO: Date | PO No. | Customer | Seed | Seed Location | Lot No. | Reference Weight | Issue Weight | Return Weight | Seeds Used | Trays Sown | Deviation
  • Deviation recorded per PO: seeds used ÷ theoretical (trays sown × cells × seeds/cell)
  • Batch issuing: one weighed issue splits across several POs of the same variety, proportionally by planned trays
  • No PO splitting needed — a second lot issued to the same PO simply adds another movement line
  • Release/unrelease: one-click undo of an issue (seeds back on the lot, batch removed, PO back in the queue) until sowing is confirmed
  • Raw movement ledger still available behind a toggle for auditing
2.1.0 August 6 2026
Feature Fix

First official update! It's a big one!

  • Tables & Search (system-wide)
  • Tables no longer move while you filter. Column widths are locked after the page loads, so typing in a filter only hides rows — the table itself stays perfectly still.
  • Combine filters inside one column. Filter boxes understand a|b (either), a & b (both), and !a (exclude) — for example, status confirmed|planted, or quantity >100 & <500. Dropdown filters (status, unit, currency) are now checkbox lists so you can tick several values at once.
  • Filters accept percentages the way you type them. Searching a success rate as 80, 80%, or .8 all find the same rows — no more guessing how the number is stored.
  • Every table has its own search box. One field that matches against all visible columns at once, plus a ↻ Refresh button that re-pulls data without reloading the page.
  • Pagination for large tables. Tables page through records (with a rows-per-page choice) instead of piling thousands of rows onto one page. Excel exports still include the full filtered set.
  • Global search in the top bar. One search across clients, orders, products, production orders, seed lots, invoices, payments, purchase orders and delivery notes — results link straight to the record, and each person only sees results from modules they have access to.
  • Bulk editing in list views. Editable tables have row checkboxes with "set field on all selected" and "delete selected," with confirmation and a success/failure tally. All existing permissions still apply.
  • Dashboard, Reports & Notifications
  • Top sellers. The dashboard highlights the most-sold item this month (e.g. "🏆 Most sold item this month: Tomato Anna F1 — 88,400 plugs") with top-3 breakdowns per production line, and Reports gained an "Order items (top sellers)" dataset for slicing by month, line, or client.
  • Notifications grouped by section. The bell now folds alerts into Sales, Production, Delivery, Finance, Inventory, and so on — each with a count, click-to-expand, and a per-section "Clear all," instead of one long list.
  • CRM
  • Corporate vs non-corporate codes. New corporate clients get CO____ codes and non-corporate clients CL____, so the code alone tells them apart. Existing clients keep their current codes (payment matching depends on them).
  • "My Customers" workspace. A personal page for each sales rep: their clients with last interaction, next scheduled follow-up, open tasks, and open orders — all visible without opening a single customer card. Includes an overdue/today/this-week schedule with one-click done, quick "log / schedule" on any client, and a switcher to view a colleague's book for cross-reference.
  • Client Orders — Registration
  • Sow Max. For client-owned seed, tick "Max" to sow everything the client has in the seed store. Quantities display the word Max everywhere — including on printed labels.
  • Success-rate supply planning. Each line shows the quantity ordered and the quantity to sow. By default: orders placed in trays are sown as-is (no success-rate top-up), plants/plugs orders are grossed up to cover expected losses, and client-owned seed is excluded — with a per-line checkbox to override any of these, including the client-seed rule.
  • Editable sow quantity. The "to sow" figure is a field you can type over when a client directs exactly what to sow — planning then follows the directive instead of the formula.
  • Mixed trial trays. Lines can be marked 🧪 mixed tray when several small trial varieties share one physical tray. Marker only — quantity calculations are unchanged.
  • Faster entry. Client and farm/delivery-point fields are type-ahead searches. Delivery point can also be changed later on the order, right up until dispatch.
  • Units to invoice. Price lists now offer tray, plant, and cell (one cell = one plug) as invoicing units.
  • Client Orders — Lifecycle
  • Estimated completion date. The orders table shows each order's expected end date — from real production ETAs once planned, otherwise from crop lead days.
  • Repeating orders. Orders can repeat weekly, monthly, or yearly. The system creates the next occurrence as an editable draft two weeks ahead (with a notification), since these orders usually change — nothing is ever confirmed automatically. A management panel on the orders page lets you pause, reschedule, or stop a schedule.
  • Partial sowing reasons. Recording a partial planting now requires a short reason, which appears 💬 next to the status on the confirmation queue and the order — so follow-up is obvious.
  • Closing partially fulfilled orders. When a client accepts a reduced quantity, "Close short as fulfilled" ends the order cleanly instead of leaving it stuck. It always goes through manager approval, and the system records who requested it, who approved it, and why. (Admin note: route the order.close-short and order.unlink approval actions to your Marketing/Supply-Chain manager roles under Administration → Approvals.)
  • Shared collection date. Multi-crop orders can commit to one collection day. Planning suggests sow dates counted backward from that day (longest lead time sows first), and the whole order is flagged the moment any item's delay becomes known — not on sowing day. A flagged order offers two resolutions: push the whole collection date back, or unlink the delayed item into its own order (approval-gated, with the approver shown which item caused the delay and the proposed new dates).
2.0.2 24 July 2026
FeatureFix

Another round of fixes and QOL improvements

  • M-Pesa: prepayments now auto-match to the customer (by order ref or phone) and show as credit on their account
  • Finance confirms each prepayment against an order or invoice from the allocation queue — nothing applies automatically
  • Customer portal and CRM now display "credit on account" for unapplied prepayments
  • M-Pesa C2B connection verified end-to-end in sandbox (live webhook on prod.planseedgrow.com)
  • Excel exports always include column headers, even with no rows
  • Orders can't be released to production without prices — missing prices are flagged and alert the sales team
  • Zero-value invoices, transport charges, and tray write-offs are now blocked with clearer guidance
  • Clearer forms everywhere: empty dropdowns now explain what's missing and where to set it up
  • Production batch actions explain the seed-store to planting chain instead of showing blank
  • Dashboard pipeline chart no longer stretches bars when few stages have orders
2.0.1 24 July 2026
Fix

Few bug fixes

  • Fixed issues with missing pricing and null values being passed to orders
  • Added email functions from test domain. Password resets and other items can be emailed to customers
  • Fixed issue where DN would issue a 0 invoice on upriced order
  • Added mock mpesa connector to live Mpesa sandbox. Further testing required.
2.0.0 July 22
Release

V2 Production Deployment

  • Sever updated to a production level chasis. DB migrated and seeded data removed aside from required.
1.0.0 12 Jul 2026
Release

Initial release

  • First production release of the Plantech Kenya nursery ERP, built to spec across all 47 assumptions.
  • Master-data CRUD, production planning, orders, logistics, finance and stores.
  • Mobile app for field agents, drivers, greenhouse and harvest teams with an offline action queue.
  • Mock eTIMS, M-Pesa, weighbridge and OCR integrations.

Incident history

Major outage ERP database unreachable 20 Sept 2026 · resolved in 51s
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: timeout after 10000ms.
Major outage ERP database unreachable 18 Sept 2026 · resolved in 51s
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: timeout after 10000ms.
Major outage ERP application (139.84.245.114) unreachable 18 Sept 2026 · resolved in 51s
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: timeout after 10000ms.
Major outage ERP database unreachable 16 Sept 2026 · resolved in 1m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected 200).
Major outage ERP application (139.84.245.114) unreachable 16 Sept 2026 · resolved in 1m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected one of 200/301/302/307/308).
Major outage ERP application (139.84.245.114) unreachable 12 Sept 2026 · resolved in 55s
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: timeout after 10000ms.
Major outage ERP database unreachable 11 Sept 2026 · resolved in 1m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected 200).
Major outage ERP application (139.84.245.114) unreachable 11 Sept 2026 · resolved in 1m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected one of 200/301/302/307/308).
Show 70 older incidents
Major outage ERP database unreachable 10 Sept 2026 · resolved in 13m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Failures recurred: HTTP 502 (expected 200).
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected 200).
Major outage ERP application (139.84.245.114) unreachable 10 Sept 2026 · resolved in 13m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Failures recurred: HTTP 502 (expected one of 200/301/302/307/308).
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected one of 200/301/302/307/308).
Major outage ERP database unreachable 09 Sept 2026 · resolved in 1m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected 200).
Major outage ERP application (139.84.245.114) unreachable 09 Sept 2026 · resolved in 1m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected one of 200/301/302/307/308).
Major outage ERP database unreachable 08 Sept 2026 · resolved in 41m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Failures recurred: HTTP 502 (expected 200).
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Failures recurred: HTTP 502 (expected 200).
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected 200).
Major outage ERP application (139.84.245.114) unreachable 08 Sept 2026 · resolved in 41m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Failures recurred: HTTP 502 (expected one of 200/301/302/307/308).
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Failures recurred: HTTP 502 (expected one of 200/301/302/307/308).
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected one of 200/301/302/307/308).
Major outage ERP database unreachable 01 Sept 2026 · resolved in 1m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected 200).
Major outage ERP application (139.84.245.114) unreachable 01 Sept 2026 · resolved in 1m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected one of 200/301/302/307/308).
Major outage ERP database unreachable 01 Sept 2026 · resolved in 1m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected 200).
Major outage ERP application (139.84.245.114) unreachable 01 Sept 2026 · resolved in 1m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected one of 200/301/302/307/308).
Major outage ERP database unreachable 31 Aug 2026 · resolved in 1m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected 200).
Major outage ERP application (139.84.245.114) unreachable 31 Aug 2026 · resolved in 1m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected one of 200/301/302/307/308).
Major outage ERP database unreachable 29 Aug 2026 · resolved in 1m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected 200).
Major outage ERP application (139.84.245.114) unreachable 29 Aug 2026 · resolved in 1m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected one of 200/301/302/307/308).
Major outage ERP database unreachable 28 Aug 2026 · resolved in 1m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected 200).
Major outage ERP application (139.84.245.114) unreachable 28 Aug 2026 · resolved in 1m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected one of 200/301/302/307/308).
Major outage ERP database unreachable 28 Aug 2026 · resolved in 30m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Failures recurred: HTTP 502 (expected 200).
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected 200).
Major outage ERP application (139.84.245.114) unreachable 28 Aug 2026 · resolved in 30m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Failures recurred: HTTP 502 (expected one of 200/301/302/307/308).
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected one of 200/301/302/307/308).
Major outage ERP database unreachable 28 Aug 2026 · resolved in 1m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected 200).
Major outage ERP application (139.84.245.114) unreachable 28 Aug 2026 · resolved in 1m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected one of 200/301/302/307/308).
Major outage ERP database unreachable 25 Aug 2026 · resolved in 1m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: timeout after 10000ms.
Major outage ERP application (139.84.245.114) unreachable 25 Aug 2026 · resolved in 1m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: timeout after 10000ms.
Major outage ERP database unreachable 23 Aug 2026 · resolved in 1m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected 200).
Major outage ERP application (139.84.245.114) unreachable 23 Aug 2026 · resolved in 1m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected one of 200/301/302/307/308).
Major outage ERP database unreachable 23 Aug 2026 · resolved in 1m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected 200).
Major outage ERP application (139.84.245.114) unreachable 23 Aug 2026 · resolved in 1m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected one of 200/301/302/307/308).
Major outage ERP database unreachable 19 Aug 2026 · resolved in 8m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: timeout after 10000ms.
Major outage ERP application (139.84.245.114) unreachable 19 Aug 2026 · resolved in 8m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: timeout after 10000ms.
Major outage ERP database unreachable 15 Aug 2026 · resolved in 1m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected 200).
Major outage ERP application (139.84.245.114) unreachable 15 Aug 2026 · resolved in 1m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected one of 200/301/302/307/308).
Major outage ERP database unreachable 15 Aug 2026 · resolved in 4m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: timeout after 10000ms.
Major outage ERP application (139.84.245.114) unreachable 15 Aug 2026 · resolved in 4m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: timeout after 10000ms.
Major outage ERP database unreachable 15 Aug 2026 · resolved in 51s
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: timeout after 10000ms.
Major outage ERP application (139.84.245.114) unreachable 15 Aug 2026 · resolved in 51s
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: timeout after 10000ms.
Major outage ERP database unreachable 13 Aug 2026 · resolved in 1m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected 200).
Major outage ERP application (139.84.245.114) unreachable 13 Aug 2026 · resolved in 1m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected one of 200/301/302/307/308).
Major outage ERP database unreachable 11 Aug 2026 · resolved in 1m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected 200).
Major outage ERP application (139.84.245.114) unreachable 11 Aug 2026 · resolved in 1m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected one of 200/301/302/307/308).
Major outage ERP database unreachable 11 Aug 2026 · resolved in 1m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected 200).
Major outage ERP application (139.84.245.114) unreachable 11 Aug 2026 · resolved in 1m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected one of 200/301/302/307/308).
Major outage ERP database unreachable 11 Aug 2026 · resolved in 1m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected 200).
Major outage ERP application (139.84.245.114) unreachable 11 Aug 2026 · resolved in 1m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected one of 200/301/302/307/308).
Major outage ERP database unreachable 09 Aug 2026 · resolved in 1m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected 200).
Major outage ERP application (139.84.245.114) unreachable 09 Aug 2026 · resolved in 1m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected one of 200/301/302/307/308).
Major outage ERP database unreachable 09 Aug 2026 · resolved in 52s
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: timeout after 10000ms.
Major outage ERP application (139.84.245.114) unreachable 09 Aug 2026 · resolved in 52s
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: timeout after 10000ms.
Major outage ERP database unreachable 08 Aug 2026 · resolved in 58s
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected 200).
Major outage ERP application (139.84.245.114) unreachable 08 Aug 2026 · resolved in 58s
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected one of 200/301/302/307/308).
Major outage ERP database unreachable 08 Aug 2026 · resolved in 4m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Failures recurred: timeout after 10000ms.
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: timeout after 10000ms.
Major outage ERP application (139.84.245.114) unreachable 08 Aug 2026 · resolved in 4m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Failures recurred: timeout after 10000ms.
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: timeout after 10000ms.
Major outage ERP database unreachable 08 Aug 2026 · resolved in 3m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: timeout after 10000ms.
Major outage ERP application (139.84.245.114) unreachable 08 Aug 2026 · resolved in 3m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: timeout after 10000ms.
Major outage ERP database unreachable 07 Aug 2026 · resolved in 1m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected 200).
Major outage ERP application (139.84.245.114) unreachable 07 Aug 2026 · resolved in 1m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected one of 200/301/302/307/308).
Major outage ERP database unreachable 06 Aug 2026 · resolved in 1m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected 200).
Major outage ERP application (139.84.245.114) unreachable 06 Aug 2026 · resolved in 1m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: HTTP 502 (expected one of 200/301/302/307/308).
Major outage ERP database unreachable 06 Aug 2026 · resolved in 51s
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: timeout after 10000ms.
Major outage ERP database unreachable 06 Aug 2026 · resolved in 51s
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: timeout after 10000ms.
Minor issue Customer portal unreachable 03 Aug 2026 · resolved in 5m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: timeout after 10000ms.
Minor issue Storefront unreachable 03 Aug 2026 · resolved in 5m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: timeout after 10000ms.
Major outage Website & staff sign-in unreachable 03 Aug 2026 · resolved in 5m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: timeout after 10000ms.
Major outage ERP database unreachable 03 Aug 2026 · resolved in 5m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: timeout after 10000ms.
Major outage ERP application (139.84.245.114) unreachable 03 Aug 2026 · resolved in 5m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: ENETUNREACH.
Major outage ERP database unreachable 31 Jul 2026 · resolved in 4m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: timeout after 10000ms.
Major outage ERP application (139.84.245.114) unreachable 31 Jul 2026 · resolved in 4m
  • resolved Automated checks are passing again. Service has recovered.
  • investigating Automated monitoring detected repeated failures: timeout after 10000ms.
Minor issue Label search returning no matches 21 Jul 2026 · resolved in 45m
  • resolved Search set to case-insensitive after the PostgreSQL migration. Label lookups return expected results.
  • identified Post-migration, text search became case-sensitive so mixed-case label queries returned nothing.
Minor issue Some form submissions returning an error 21 Jul 2026 · resolved in 35m
  • resolved API now defaults an empty body for non-JSON requests. Affected submissions succeed; found during the new-server bring-up.
  • investigating Certain POST requests without a JSON content-type returned a server error.
Major outage Reports page failing for Sales users 15 Jul 2026 · resolved in 2h 35m
  • resolved Resolved. Role-scoped report queries no longer exceed the database parameter limit; verified across all demo roles.
  • monitoring Fix deployed — large order sets are now filtered in application code. Watching for recurrence.
  • identified A very large query for a sales rep with ~1,800 orders exceeded the SQLite parameter limit, returning a 500.
  • investigating Sales users report the Reports page returns an error.
Minor issue Duplicate operational alerts flooding the alerts list 14 Jul 2026 · resolved in 2h 20m
  • resolved Alert generators now dedupe against existing open alerts. Backlog cleaned (2,745 → 353). No data affected.
  • identified Overgrowth, tray-overdue and service-due checks re-raised alerts on every page load.
  • investigating Operators report the alerts panel filling with repeated entries.
Minor issue Sign-out not working on production 13 Jul 2026 · resolved in 45m
  • resolved Fix deployed. Redirects now build from the public host behind the proxy; staff and customer sign-out confirmed working.
  • identified Logout redirect pointed at an internal address behind nginx. Patching the redirect helper.
  • investigating Reports that Sign out on the live site did not return users to the login screen.